Discover new horizons in test automation! If routine is already starting to undermine your passion for automation development, then we know how to break this monotonous pattern. Based on our experience in developing projects, we invite you to dive into the world of fuzzing and improve your testing process. 

We will tell you the main steps and patterns for implementing fuzzing testing, talk about collecting experience, and show how to avoid possible mistakes and pitfalls when using it. You'll gain valuable, practical tips on how to optimize your testing process using fuzzing. 

In our talk, we will tell two points of view — a specialist with 10 years of experience who has long been immersed in the topic of automation, and a specialist who is taking his first steps in this field.

Storytelling about how autotests were born and died in one product. What problems they solved and how their concept changed. About successes and mistakes.  About how we wrote a lot of code, and then rewrote it twice. We set up a database for data and didn't think through the architecture. About how we tinkered with the pipeline and still overcomplicated it. In general, about what many of you have encountered and, perhaps, may still encounter.

In this talk, the speaker addresses a common issue observed among functional testers, where a lack of understanding of development tools leads to inefficient testing practices. As a result, valuable time is wasted, and critical bugs may be overlooked due to a false sense of test coverage.

The main objective of the presentation is to introduce attendees to a selection of popular development tools, focusing on their potential for reuse and integration into the testing process to boost efficiency. By highlighting the advantages and best practices associated with these tools, the speaker aims to equip functional testers with the necessary knowledge and skills to optimize their testing efforts.

Big company and chaos were eating into our projects, but we were able to stop it.

How? With the support of corporate tools and approaches developed by us.

We will talk about them in our report.

We will tell you how to save yourself in the entropy of implementing, developing and supporting automated tests, as well as lower the threshold for entering test automation.

What to do if there is a need to automate testing of end-to-end processes, but there is no skill. As a rule, in large teams, you can always find someone who already has such experience and is ready to share it. What to do if there is no such person in the team, but there is a desire and even a need? 

Today I will share with you the answers (from my experience) to the most pressing questions: 

• Where to begin?
• How to choose an approach to this kind of automation?
• Wet or not?

 And also to many others.

The asynchronous approach has long been the norm for developers but is rarely seen among testers because it is considered more complex.

In reality, the current level of development of tools allows you to write asynchronous code for autotests with little effort, which can later be easily reused for load testing, taking into account the peculiarities of business logic while saving resources and development time.