The Crosswalk Project test suite includes test cases that validate the behavior of the project. The tests are open source. The souce code can be obtained from Crosswalk Test Suite repository.
There are several components in the Crosswalk Project. For example:
- Web API -- APIs used by web applications running on the Crosswalk Project runtime
- Embedding API -- the Java API for embedding the Crosswalk Project in an Android application.
The corresponding test suites for these components are well orginazed with the following parts:
- Web API tests
- Embedding API tests
- Web Runtime and feature tests
- Crosswalk based Cordova tests
Tools, documentation, and some other tests (e.g. stability tests and BAT tests) are also included in the test suite. Please refer to test suite wiki for more details.
The Test Suite provides a series of development guides for test case developers and contributors. The guides cover test suite source layout, coding style, test case naming convention, folder naming convention, test case classification, and how to add test cases into test suites for components like Web API, Embedding API, Cordova and Web Runtime. You may also need to understand the test case priority and test coverage before developing the test cases.
The Test Suite not only covers the master branch but also the beta branch since usually case bugs are affected on both of them and sometimes we need to add hotfixes on the beta branch. The Test Suite branch schedule aligns with branch dates of Crosswalk Project which follows Crosswalk release methodology.
Web Testing Service
The easiest way to run the test suites is using the Web Testing Service. It is a web-based test runner that indicates how well browsers or web runtimes support web standards and related specifications on different platforms. The Web Test Client based on the Crosswalk Project is also available on Google Play. Please refer to the Web Testing Service wiki for more details.
Contribute test cases
No test is too small or too simple if it helps to validate a feature or behavior. Everyone is encouraged to contribute to test development. Please refer to detailed contribution steps in contribute tests page.