How to properly (not) use testers
https://habr.com/ru/company/jugru/blog/661623/
Recently I came across a text article from the creator of Allure Report, I watched this report in the record.
Main Points:
- Autotests are written in native languages ββin the same repository.
- Tests run on build.
- Automation is higher than documentation: we do not need manual descriptions, they quickly become outdated.
- Cross-functional teams: people know how to write code and fix the framework, development is interested in testing, and so on.
- Shared infrastructure: testers are also responsible for the test environment.
Yes, in general, itβs cool if there is such a team and everything works like clockwork.
Most likely, the main problem will be writing native tests in one repository, as well as running autotests for each PR (MR). This is not done at the snap of a finger, it requires the efforts of the whole team.
If you are using Allure Report / Allure TestOps, then in fact you already get live documentation. There are no particular problems with this.
Team development is, in principle, one of the important areas, here you need to instill good practices from the very beginning, undergo training, just learn from colleagues or other people.
β And a question to everyone, have you heard about this approach at all? Or maybe you are already trying to get closer to the ideal team?π
Original post in Telegram - https://t.me/qa_relia/50