Digital Transformation is now the holy grail of IT organizations. However, most companies are still struggling with setting up a proper Continuous Delivery process, which shall help the transition into shorter release cycles and faster, more frequent deployments to production.

Teams may already be familiar with Continuous Integration, Continuous Delivery and Continuous Deployment (the 3Cs) and the differences between them. However, to make these 3Cs possible, we need a fourth C, namely Continuous Testing (a.k.a Test Automation.) Continuous Testing is the fast feedback mechanism that assists the 3Cs and is one of the most difficult challenges for digital transition.

In this talk, I'm aiming to cover the top continuous testing pitfalls and how companies are solving these problems. This talk is based on practical examples that include key pitfalls around:

• Test Data management
• Choosing the right tool/framework
• Deciding on what to automate?
• Is In-Sprint Automation possible?
• Is automation part of Definition of Done?
• Effective collaboration
• Test Environments
• Flaky tests

It's time the testers took control! And use some of the modern tools that help address those problems. This talk will cover tech stack like Selenium, Appium, PlayWright, Taiko, Docker, Kubernetes, Grafana/Kibana, TestContainers.

A few months ago Appium migrated to W3C protocol, added AI, and integration for custom plugins for element search, that anybody can implement. Apple released Xcode 10 with abilities run XCUITest in Parallel. Google released EarlGrey with support for accessibility in iOS12 and then there is Flutter with its driver package for integration testing.

As you see, there has been a lot of recent developments and additions in the mobile testing world. This talk aims at covering them and also review its current state and suggest some key pointers when selecting a tool and review their usage and weaknesses