| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Overrides/Supersedes
This decision was migrated from the Tech Leads Decision Log as part of a consolidation process. The original decision record can be found here.
RFC
N/A
Stakeholders
Contributors
Aliaksei Chumakou Mikita Siadykh
...
- Follow honeycomb approach (UI part is marked with bold lines on picture)
- 70-80% unit/integration tests coverage - it's possible to use one testing tool for that so it shouldn't be a problem to count coverage for both test types;
- Per commit unit tests execution
- POs/QAs define set of e2e scenarios (for existing features they could be gathered from testrail, but for new features PO can define scenarios in the tickets itself, so e2e tests could be counted in ticket's estimation)
- e2e tests are executed frequently (after merge to master, 1 per day, etc ?)
- e2e tests don’t block environments
- e2e tests reporting (e.g. reportportal.io)
Action items
- to review initial document Anton Emelianov (Deactivated)
- to check what needs to be changed regarding requirements/goals of new approach for ui testing Mikita Siadykh
...