0.5 Content and goals

Select a link to go directly to the lesson or topic relating to the listed goal:

• Section 1: Agile Software Development
  
  • Remember the basic concept of Agile software development based on the Agile Manifesto.
    
    
  • Understand the advantages of the whole-team approach and the benefits of early and frequent feedback.
    
    
  • Recall Agile software development approaches.
    
    
  • Be able to write testable user stories in collaboration with developers and business representatives.
    
    
  • Understand how retrospectives can be used as a mechanism for process improvement in Agile projects.
    
    
  • Understand the use and purpose of continuous integration.
    
    
  • Know the differences between release planning and iteration planning, and how a tester adds value in each of these activities
    

• Section 2: Fundamental Agile testing principles, practices, and processes
  
  • Describe the differences between testing activities in traditional and Agile projects.
    
    
  • Describe how development and testing activities are integrated in Agile projects.
    
    
  • Describe the role of independent testing in Agile projects.
    
    
  • Describe the tools and techniques used to communicate the status of testing in an Agile project, including test progress and product quality.
    
    
  • Describe the process of evolving tests across multiple iterations and explain why test automation is important to manage regression risk.
    
    
  • Understand the skills (people, domain, and testing) of a tester in an Agile team.
    
    
  • Understand the role of a tester in an Agile team.
    

• Section 3: Agile testing methods, techniques, and tools
  
  • Recall the concepts of test-driven development, acceptance test-driven development, and behaviour-driven development.
    
    
  • Recall the concepts of the test pyramid.
    
    
  • Summarise the testing quadrants and their relationships to testing levels and testing types.
    
    
  • Be able to work as a tester in a Scrum team.
    
    
  • Be able to assess quality risks in an Agile project.
    
    
  • Be able to estimate testing effort based on iteration content and quality risks.
    
    
  • Be able to interpret relevant information to support testing activities.
    
    
  • Be able to explain to business stakeholders how to define acceptance criteria that are testable.
    
    
  • Be able to write acceptance test-driven development test cases for a given a user story.
    
    
  • Be able to write test cases using black-box test design techniques, for functional and non-functional behaviour, based on given user stories.
    
    
  • Be able to perform exploratory testing to support the testing of an Agile project.
    
    
  • Recall the different types of tool available to testers according to their relevance in Agile projects.