In current agile times, the industry demands from us that we release production-ready software more often, typically every two to four weeks. To do this, you will not only need to guarantee that the new features work but also that existing functionality still works. If you're relying on humans to verify this by hand, you will face two problems. First, humans invariably make mistakes when doing repetitive tasks so bugs will go uncaught. Second, after a few weeks the application will become simply too large to completely regression test every iteration. As a result of this, the feedback loop will become larger and larger. Soon, your project will grind to a halt while you spend entire iterations doing bugfixes on functionality built weeks ago that isn't fresh in anyones mind. Luckily you can avoid these pitfalls by making sure that all recurring tests done by the team are automated (Three strikes and you automate). This way, you can get feedback early and often and you will be able to fix bugs while everything is still fresh in your mind. Xebia has a lot of experience in this area; we're going to share it in practical hands-on examples in this workshop. .

Topics in this 2-day workshop are:

• automation tools
• acceptance suites