When communicating with colleagues and friends involved in software testing, very often I hear questions like "How to take the first steps in test automation?".

For many of us, this question remains without a confident answer. As a result, we can see a growing fear of taking the first but perhaps the most important steps to testing automation and drastically saving resources and time. 

In my talk, I want to share the most important and simple steps for introducing test automation into your daily work. We will talk about: How to start writing autotests within a week after the appearance of such an idea; How to sell the idea of ​​the usefulness of automation to management; How to write tests from day one that will not only make your life easier but will also be highly maintainable in the future!

The talk will be especially interesting for QA engineers for whom manual regression seems to be an unacceptable waste of time.

Nowadays, auto-tests have become not just a trend, but a mandatory tool in most of the IT-companies around the world. One of the most common objects to be covered with auto-tests is API. 

This talk is about one of the approaches used by Arenadata Software Company to write “truly” automated tests for basic API properties and functions of one of Arenadata applications. We will describe its main advantages: versatility, scalability and the ratio of the amount of required code to the number of final automated tests for applications with an extensive API. We will discuss the possible difficulties in implementing this approach and share the results of applying this approach when implementing an automated testing framework for one of our applications.