History

Julie Ralph 5a59e44765 chore(test): migrate Dart tests to package:test Instead of running with karma and the karma-dart shim, run dart tests directly using the new package:test runner. This migrates away from package:unittest. Fixes a couple tests, mostly associated with depending on absolute URLs or editing the test providers after an injector had already been created. Remove karma-dart and associated files. Change gupfiles to run tests via `pub run test` instead.		2016-03-04 02:27:44 +00:00
..
impl	chore(test): migrate Dart tests to package:test	2016-03-04 02:27:44 +00:00
README.md	refactor(router): improve recognition and generation pipeline	2015-11-30 17:06:03 +00:00
async_route_spec.ts	chore(test): migrate Dart tests to package:test	2016-03-04 02:27:44 +00:00
auxiliary_route_spec.ts	chore(test): migrate Dart tests to package:test	2016-03-04 02:27:44 +00:00
bootstrap_spec.ts	chore(test): migrate Dart tests to package:test	2016-03-04 02:27:44 +00:00
lifecycle_hook_spec.ts	feat(router): add regex matchers	2016-03-02 16:08:19 -08:00
navigation_spec.ts	feat(router): add regex matchers	2016-03-02 16:08:19 -08:00
redirect_route_spec.ts	feat(router): add regex matchers	2016-03-02 16:08:19 -08:00
router_link_spec.ts	feat(router): add regex matchers	2016-03-02 16:08:19 -08:00
sync_route_spec.ts	chore(test): migrate Dart tests to package:test	2016-03-04 02:27:44 +00:00
util.ts	feat(router): add regex matchers	2016-03-02 16:08:19 -08:00

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.