Testing strategy (draft)

Testing approaches

Next procedures are planned to be included into the Design system product testing:

1. Manual testing: Screenshots' comparing (resolutions and browsers to be agreed);

2. Automated testing: Visual regression testing (for released components);

3. Unit tests;

4. Accessibility checking (automatic, via Storybook);

All the tests mentioned above will be based on Browsers & Devices support agreed strategies. CI/CD process set up is also planned to be included into the approach for developed components' testing.

Assumptions

The list of initial assumptions for testing is below:

1. Use automatic validation, whenever possible, even if implemented at a basic or incomplete level.

2. During component development, the most important tests are those which check that the Application Programming Interface (API) is operating correctly, that the element’s accessibility rules are observed and whether there are any graphic regressions.

3. To create acceptance criteria we can use 4 questions as a start:

• Does the new component solve a problem that can’t be solved with existing patterns?

• Does it meet user and business needs across multiple areas?

• Does it match customers’ needs?

• Does it meet the accessibility standards?