Frequently, the testers perform checking of the ready-made product on the basis of the created project documentation. They are familiar with the specifics of system operation, know the peculiarities of working area, and etc.
If it is an agile development, then it is a different story. The role of QA specialist becomes quite different. He should know not only how to check a certain part of functionality but also what will be and should be the outcomes of this checking. At that, all business goals and tasks should be met as well.
There are several types of agile methodologies. But despite the fact that, a tester plays a kind of a key link between the developers and end users. The QA specialists “build a bridge” between what is required, how this may be executed, and how this may be ensured before the deployment process.
What are the myths of Agile Testing?
- Unit testing will be enough for qualitative checking.
- Regression tests may be created with the help of the module tests reuse.
- The testers and automation tools are not required for agile testing.
- Actually, automated testing becomes impossible.
- Due to the unit tests, there is no need to conduct manual testing.
- The developers possess the skills, enough for qualitative checking.
- User acceptance testing loses its importance.
- The TDD principle may be used for all projects.