BELARUS

BIO

With more than 10 years in IT I had a chance to work in different areas, such as development, testing and management. I had a chance to work with PHP, Java, Python and .Net platform with different application from microservices to monolithic and monstrous desktop UI applications.
With such a rich background I decided to focus on things that help to deliver high-quality software, starting from inception and all the way to operation.
Currently I am holding a position of Test Automation Tech Lead, but I prefer to consider myself a full-stack engineer. My passions are quality and efficiency. Agile fan and XP practitioner.

 

Topic: Quest for an adequate autotest coverage

There’re lots of “best practices” for test automation, like Test Pyramid, Page Object Model, Layered frameworks but still test automation initiatives fail to deliver expected results. In a talk we will go through the test automation pitfalls, areas where “Best practices” do not help and easy and, for some, unexpected way to make test automation initiative successful.

Takeaway:

-Simple algorithm to make sufficient (adequate) test coverage for top-to-bottom (from unit to UI) and bottom-to-top (from UI to unit) test automation – real life example of automating pretty much the same functionality in a layered application using both approaches.

-Understanding (on practice example) the effect that application architecture makes on test automation and a way to increase test automation efficiency – layered architecture vs hexagonal architecture. Dependencies and test automation. All in all my message is that there’s no distinct test automation discipline, and test automation works best when it is considered natural part of architecture design and development.

Topic outline:

Slides (1-15 minutes)
Coding and Q/A – all other time.

 

« Go Back