Duration: 1 Day
Course Overview
This module concentrates on the ways in which testing is conducted differently in agile teams when compared to traditional processes. Traditionally testing would be carried out by separate QA departments, often with deliberate separation from the design and development teams. Products were handed over for QA once significant functionality has been built, so that the QA team can focus on proving whether the functionality demanded in the requirements were implemented correctly.
Agile testing embeds test experts into the agile teams, who work alongside the designers and developers to jointly realise well-implemented and functionally correct requirements in the software product. To achieve this efficiently, rapidly and reliably, the techniques and technologies used in testing are different from the traditional tools and methods.
The module introduces all these changes, together with reviewing the benefits achieved by the newer approach, and the pitfalls of doing it badly or half-heartedly.
The style of learning used in this module is lecture, small-group activities, and some demonstrations of software tools.
How can I attend my course?
Course Content
Introduction
• Traditional SDLC processes – waterfall and V-model
• Agile principles and values
• Iterative, incremental product development
• Rapid feedback
• Collaborative, cross-functional, cohesive teams
• Agile testing – values and principles
Core practices
• Collaborative development and test
• Moving testing to the left
• Test-Driven Development
• Test automation
• Continuous Integration and Continuous Delivery
• Continuous Improvement through retrospection
Case study
• Discussion of a case study development project
• Designing the team structure
• Choosing the testing approach
• Planning testing for an agile sprint