End-to-end tests appear everywhere: test-driven development, story-test-driven development, acceptance testing, functional testing, and system testing. They’re also slow, brittle, and expensive. In this expert-level workshop, we will discuss why end-to-end testing is used, examine where and why it breaks down, and generate more effective solutions. We will spark ideas for participants to explore further on their own.

We will not be debating the premise (that end-to-end tests are problematic). This is an expert-level workshop and attendees will be expected to participate fully.

Why do testers on some agile teams find iterations productive and enjoyable, while other teams struggle to “keep up” with testing and get stories to “done done” within the iteration? Succeeding with agile testing is more than just automating tests or sitting with the developers. To create working software quickly, your whole team must be able to build a shared understanding of a feature - and do this rapidly, accurately, over and over again, every feature, every iteration. This hands-on tutorial teaches you how to use the agile technique of acceptance criteria to build shared understanding.

This talk discusses techniques that can be used to apply Agile practices to atypical technologies, and presents case studies on how to apply Agile practices to projects built with technologies including Teradata (Database), and MicroStrategy (BI).

A Continuous Integration system is often considered one of the key elements involved in supporting an agile software development and testing environment. As a traditional software tester transitioning to agile environment, it became clear that we would needed several changes to make the transition to agile testing possible. This experience report discusses a continuous integration implementation I led last year. The initial motivations, technical specifics of the implementation, perceived benefits to the team, and retrospective results are all discussed.