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.
Comments