We work with different types of testing, depending on what the client needs.
When there is no software documentation and the engineer must learn about the product through work, the exploratory testing method is suitable. This strategy necessitates less formalistic preparation, asit does not adhere to the script and encourages thinking outside the box.
We also do requirements testing – our work starts even before the actual programming. We make sure all the documentation is clear and interpretable only in one proper way. It is also a good way to make sure the nomenclature and UX principles used across the system are consistent, if multiple products are under development.
We mostly focus on functional and regression testing, which do not require coding skills but rather a good overall understanding of business. The scope of such tests is selected by risk evaluation and time available – such tests are good to automate, as they often refer to features that are not planned to change in the nearest future.