Сапурина Лилия Юрьевна
В автоматизации с 2014 года. Занимаюсь разработкой систем автоматизации с нуля и их внедрением в команду, разработкой процесса автоматизации. Ежегодно делюсь своим опытом на конференциях в секциях, посвященных тестированию (CEE - SECR, SQA Days, TestCon)
Tips and tricks: test syntax simplifying and multi-environment testing
A year ago, I talked about calculating risks and switching to a new test automation tool. This time, I would like to talk about technical details of the tool implementation, which allows flexible testing at the component and integration levels by all team members.
I will tell you about dynamic configurations that allow write universal tests for many environments and show an example of implementation of Spring-like syntax that allowed to simplify the technique of writing tests using Java + Selenide, as well as make this process understandable and familiar for developers.
From scratch. Is it worth using a new framework for automation?
Having worked in three companies as QA automation engineer and communicating with colleagues from other teams and companies, I always meet people who are facing a dilemma - is it worth switching to a new automation framework, because the old framework is difficult to use, expand or support? What is more expensive - to spend resources on refactoring and training employees to the old framework or to use a new one? When will the new framework bring the first results?
In this talk, we will try to consider the main points that should be taken into account in the decision-making process, calculate risks and possible solutions.