Component Testing (DRAFT) 6.0
If you notice any issues with this page, please
report them.
This part of the Testing how-to guide covers component testing of AngularDart apps using the following packages:
- package:test
- Dart’s standard testing package, which is similar to most
unit testing frameworks, including Jasmine for
JavaScript. If you’ve used a modern testing framework before,
then writing tests using
package:testwill have a familiar feel. Testing basics is covered in Writing component tests: Basics. For in-depth coverage of the package capabilities, see thepackage:testdocumentation. - package:angular_test
- A complementary package that provides a means of interacting with Angular components created as test fixtures.
- package:mockito
- A library for creating
mock objects.
Not all component tests require mock objects, but in later sections, you’ll learn
the fundamentals of using
package:mockitoas needed. For further details, see the package documentation.
Scope
The angular_test package is suitable for testing either a single component, or a small group of related components. This package is not meant to test an entire app. For that, you need to write end-to-end tests.
Topics
This guide covers the following component testing topics:
- Component testing
- Running component tests
- Writing component tests
- Basics: pubspec config, test API fundamentals
- Page objects: field annotation, initialization, and more
- Simulating user action: click, type, clear
- Services: local, external, mock, real
@Input()and@Output()- Routing components
- Appendices - coming soon