Agile Development and Continuous Delivery are rapidly becoming the de facto standard for software development. The key business driver behind these initiatives: delivering new functionality to your customers faster. This is easy to state in theory but much harder to achieve in practice: the level of quality of your services must be maintained! If your system goes down once a week every week, your customers are unlikely to be happy.
Are you tired of spending endless hours maintaining your automated test cases? Do you dread looking at test automation reports because of the tedious tweaks you know you’ll need to make from the latest updates from dev? Has your team lost its faith in test automation?
The ultimate goal of a DevOps approach is to deliver high-quality features to your customers at the pace they need. High performing DevOps shops point to continuous testing and test automation as key contributors to their success.
As automation knocks on the door once again, for many there is a continued fear, when will I be automated away? While manual testing will continue for the foreseeable future, it never hurts to get introduced to the concepts of what might come next as a manual tester! The world of software development and software testing continues to change, and as it does, testing and development come to meet in the contested territory of DevOps.
Since AI driven test generation was first introduced in 2017, much has been learned. Millions of test steps were generated and executed, finding thousands of bugs. We will dig into how the technology works, where it works and doesn’t.
The world of testing is always evolving – software development life-cycles, delivery models and team culture. We see this evolution affecting the way teams are constructed, what skill-sets are required, and the ownership of quality within the organization.
