Autotests as Part of Spec: How an Analyst Passes Requirements and Acceptance Criteria to Development

In a classic development process, an analyst defines requirements, but even the most polished specification does not protect against bugs and misinterpretation. Text can be interpreted in different ways, and feedback arrives too late — together with the implemented feature. This leads to painful rework and missed deadlines.

But what if an analyst could deliver to the development team not only requirements, but also formal, executable criteria of their correctness — ready-to-use autotests?

In this talk, I will show how our team introduced this practice and what results it brought. I'll cover what a tool set we use to work with tests. During the talk, you will develop an autotest for a typical scenario using a ready-made algorithm, which you will be able to apply in your own projects.