e1bf3d33f8
Now, using `ng.probe(element)` in the browser console returns
a DebugElement when in dev mode.
`ComponentFixture#debugElement` also returns a new DebugElement.
Breaking Change:
This is a breaking change for unit tests. The API for the DebugElement
has changed. Now, there is a DebugElement or DebugNode for every node
in the DOM, not only nodes with an ElementRef. `componentViewChildren` is
removed, and `childNodes` is a list of ElementNodes corresponding to every
child in the DOM. `query` no longer takes a scope parameter, since
the entire rendered DOM is included in the `childNodes`.
Before:
```
componentFixture.debugElement.componentViewChildren[0];
```
After
```
// Depending on the DOM structure of your component, the
// index may have changed or the first component child
// may be a sub-child.
componentFixture.debugElement.children[0];
```
Before:
```
debugElement.query(By.css('div'), Scope.all());
```
After:
```
debugElement.query(By.css('div'));
```
Before:
```
componentFixture.debugElement.elementRef;
```
After:
```
componentFixture.elementRef;
```
|
||
|---|---|---|
| .. | ||
| impl | ||
| README.md | ||
| async_route_spec.ts | ||
| auxiliary_route_spec.ts | ||
| bootstrap_spec.ts | ||
| lifecycle_hook_spec.ts | ||
| navigation_spec.ts | ||
| redirect_route_spec.ts | ||
| router_link_spec.ts | ||
| sync_route_spec.ts | ||
| util.ts | ||
README.md
Router integration tests
These tests only mock out Location, and otherwise use all the real parts of routing to ensure that
various routing scenarios work as expected.
The Component Router in Angular 2 exposes only a handful of different options, but because they can be combined and nested in so many ways, it's difficult to rigorously test all the cases.
The address this problem, we introduce describeRouter, describeWith, and describeWithout.