Tests are too slow, results are unreliable, maintenance takes too much time!
Have you ever heard those complaints before?
Test automation can bring tremendous value to the project if implemented properly. Otherwise, it can quickly become a huge pain to maintain for the whole team.
Fortunately, there are well-known ways to avoid common mistakes when working with automation and you’ll see how to do it.
If you want to improve your automation game and avoid these complaints in the future – join us!
We will cover:
Why focusing on “progressive” tests is more valuable than covering regression
Proper test isolation: test data, test containers, and mocked external dependencies (Wiremock)
How to deal with flaky tests and why you should always keep the test pipeline green
Why you should invest in better logging instead of relying on debugging
How to speed up your tests and why you should parallelize test execution from the very beginning
Why it is crucial to involve developers in your automation project and use the same programming language for both development and tests
.NET Automation Tech Lead at Ciklum
Vlad has 7 years of professional experience, working both as a .NET developer and a QA Automation engineer.
He created and maintained automation frameworks in multiple programming languages, mainly in C# and sometimes Python.
Now he is a Tech Lead in the .NET automation unit.
Sign up if you're:
Test Automation Engineer of any level/language
A test automation engineer-wannabe
Project manager interested in getting the most value out of your automation project
Since 2002, we’ve engineered technology that redefines industries and shapes the way we live
clients reached IPO stage
seasoned like-minded experts globally
client domains: healthcare, fintech, travel, sportswear, entertainment, security
You can find more opportunities here: