ISTQB Foundation Agile Tester | Inclusief CTFL-AT examen
Deze cursus in het kort
- Locaties door heel Nederland
- Professionele docenten
- Inclusief certificaat
- 9.4 op Springest.nl
- Ook bij u op locatie
Agile testing is a relatively new approach to software testing. The principles of Agile software development, as described in the Agile Manifesto, are followed. A tester on an Agile project has a different way of working than on a traditional project.
Omschrijving
The ISTQB certification for Foundation Level Extension – Agile Tester is designed for professionals who are working within Agile environments. The certification is also meant for professionals who are planning to start implementing Agile methods in the near future, or are working within companies that plan to do so, The certification provides an advantage for those who would like to know the required Agile activities, roles, methods, and methodologies specific to their role.
Course outcomes
Certified agile testers should be able to demonstrate their skills in the following areas:
- the fundamentals of Agile software development;
- the different agile approaches;
- the Differences between testing in traditional and Agile approaches;
- testing in Agile projects;
- roles and skills of a tester in Agile projects;
- Agile testing techniques and methods;
- assess product quality risks within an Agile project;
- estimate testing effort based on iteration content and quality risks;
- tools in Agile projects.
Exam
Similar to the Foundation Level Certification exam, the Agile Tester Certification exam will comprise of 40 multiple choice questions, with a pass mark of 65% to be completed within 60 minutes. Participants that take the exam not in their spoken language, will receive additional 25% time, for a total of 75 minutes. The exam fees are included.
- Module: Foundation Level Agile Tester
- Number of questions: 40
- Exam length (minutes): 60
Inhoud
Chapter 1: Agile Software Development
- The tester should remember the basic concept of Agile software development based on the Agile Manifesto
- The tester should understand the advantages of the whole-team approach and the benefits of early and frequent feedback
- The tester should recall Agile software development approaches
- The tester should be able to write testable user stories in collaboration with developers and business representatives
- The tester should understand how retrospectives can be used as a mechanism for process improvement in Agile projects
- The tester should understand the use and purpose of continuous integration
- The tester should know the differences between iteration and release planning, and how a tester adds value in each of these activities.
Chapter 2: Fundamental Agile Testing Principles, Practices, and Processes
- The tester should be able to describe the differences between testing activities in Agile projects and non-Agile projects
- The tester should be able to describe how development and testing activities are integrated in Agile projects
- The tester should be able to describe the role of independent testing in Agile projects
- The tester should be able to describe the tools and techniques used to communicate the status of testing in an Agile project, including test progress and product quality
- The tester should be able to describe the process of evolving tests across multiple iterations and explain why test automation is important to manage regression risk in Agile projects
- The tester should understand the skills (people, domain, and testing) of a tester in an Agile team
- The tester should be able to understand the role of a tester within an Agile team
Chapter 3: Agile Testing Methods, Techniques, and Tools
- The tester should be able to recall the concepts of test-driven development, acceptance testdriven development, and behavior-driven development
- The tester should be able to recall the concepts of the test pyramid
- The tester should be able to summarize the testing quadrants and their relationships with testing levels and testing types
- For a given Agile project, the tester should be able to work as a tester in a Scrum team
- The tester should be able to assess quality risks within an Agile project
- The tester should be able to estimate testing effort based on iteration content and quality risks
- The tester should be able to interpret relevant information to support testing activities
- The tester should be able to explain to business stakeholders how to define testable acceptance criteria
- Given a user story, the tester should be able to write acceptance test-driven development test cases
- For both functional and non-functional behavior, the tester should be able to write test cases using black box test design techniques based on given user stories
- The tester should be able to perform exploratory testing to support the testing of an Agile project
- The tester should be able to recall different tools available to testers according to their purpose and to activities in Agile projects
Plaats en data (10)