CERTIFIED TESTER ACCEPTANCE TESTING (CT-ACT)
- Description
- Reviews
CERTIFIED TESTER ACCEPTANCE TESTING (CT-ACT)
COURSE DESCRIPTION
The ISTQB® Acceptance Testing (CT-AcT) certification focuses on the concepts, methods, and practices of collaboration between product owners/business analysts and testers in acceptance testing. It covers user acceptance testing (UAT), contractual and regulatory acceptance testing, as well as alpha and beta testing.
COURSE OBJECTIVES
IT professionals who have passed the “Acceptance Testing” syllabus exam should be able to accomplish the following Business Objectives.
For business analysts and product owners:
• Contribute to an organization’s acceptance testing activities by participating in the acceptance test design phase and supporting the alignment of the product with the business requirements;
• Contribute to an organization’s acceptance testing activities by participating in the acceptance test design phase and supporting the alignment of the product with the business requirements;
• Contribute to the quality of the acceptance testing process, including validation and verification of produced artifacts.
For testers:
• Contribute to the definition of acceptance criteria during the requirements definition phase;
• Collaborate efficiently with business analysts and other stakeholders during all acceptance testing activities:
• Understand the business objectives, communicate with business units, and share common objectives for acceptance testing.
PREREQUISITES
To gain this certification, candidates must hold the Certified Tester Foundation Level certificate.
WHO CAN BENEFIT
The Acceptance Testing certification is aimed at anyone involved in software acceptance testing activities. This includes people in roles such as product owners, business analysts, testers, test analysts, test engineers, test consultants, test managers, user acceptance testers, and software developers.
COURSE OUTLINE
1. Introductions and Foundations
1.1. Fundamental Relationships
1.1.1. Business Goals, Business Needs, and Requirements
1.1.2. Requirements/ User Stories, Acceptance Criteria and Acceptance Tests
1.1.3. The Importance of the Quality of the Requirements
1.2. Business Analysis and Acceptance Testing
1.2.1. Relationship between Business Analysis and Testing Activities
1.2.2. Collaboration between Business Analysts and Testers in Acceptance Testing
1.2.3. How Acceptance Testing Can Drive the Development Process: ATDD and BDD
2. Acceptance Criteria, Acceptance Tests and Experience-Based Practices
2.1. Writing Acceptance Criteria
2.2. Designing Acceptance Tests
2.2.1. Test Techniques for Acceptance Testing
2.2.2. Using the Gherkin Language to Write Test Cases
2.3. Experience-based Approaches for Acceptance Testing
2.3.1. Exploratory Testing
2.3.2. Beta Testing
3. Business Process and Business Rules Modeling
3.1. Modeling Business Processes and Rules
3.2. Deriving Acceptance Tests from Business Process/Rule Models
3.3. Business Process Modeling for Acceptance Testing
3.3.1. Good Practices for Business Process Modeling for Acceptance Testing
3.3.2. Using Business Process Models for ATDD
4. Acceptance Testing for Non-functional Requirements
4.1. Non-functional Characteristics and Quality in se
4.1.1. Non-functionalQuality Characteristics and Sub-characteristics
4.1.2. Quality in Use
4.2. Usability and User Experience
4.2.1. UX Requirements Analysis
4.2.2. Usability Testing
4.3. Performance Efficiency
4.3.1.High-level Performance Acceptance Tests
4.3.2. Acceptance Criteria for Performance Acceptance Tests
4.4. Security
5. Collaborative Acceptance Testing
5.1. Collaboration
5.2. Activities
5.2.1.Defect Analysis
5.2.2.Reporting
5.2.3.QA Activities for Acceptance Testing
5.3. Tool Support
Please contact us for schedules and for booking a private class.
Popular Courses
Archive
Working hours
Monday | 9:00 am - 6.00 pm |
Tuesday | 9:00 am - 6.00 pm |
Wednesday | 9:00 am - 6.00 pm |
Thursday | 9:00 am - 6.00 pm |
Friday | 9:00 am - 6.00 pm |
Saturday | Closed |
Sunday | Closed |