Transparency of QA work

Developers have access to checks, they can preview the feature at the development stage: obvious bugs will not get into the build.

Ability to quickly and conveniently modify checks

Creativity in checks is needed at the same level as consistency. It should be possible to easily modify tests if the technical specification has changed and the logic of the feature has changed.

It is also important to periodically change and expand the set of checks if a feature has been tested for a long time according to the same scenario. Let's not forget about the paradox of the pesticide: every method for preventing or finding an error leaves a part of the errors against which it is no longer effective. If you often pass the same tests, over time they will no longer find errors.

These criteria prompted us to organize one common structure in order to write in the same way in the truest sense. But, what is important, it is the same only within the framework of the general structure: the freedom of “creativity” remains within each test.