Tools Certifications Specialized Certifications Test Data Certification

Learning Objectives of CP-AAT Click here to visit CPAAT website

"Knowledge with experience is power; certification is just a by-product"

What is CP-AAT?

CP-AAT stands for “Certified Professional – Automation Agile Testing” certification prepared and honored by “Agile Testing Alliance” & “University Teknologi Malaysia (UTM)”.

CP-MAT is the prerequisite for this next level of certification called CP-AAT. Alternatively you should be having at least 3 years of relevant experience in Testing and at least one year in an Agile project.

The course is applicable for all roles and not just “testers”. Knowledge, experience & certification is consciously designed to focus on “agile testing” and not just on “agile testers”.

How is it useful?

    CP-AAT prepares you for utilizing automation effectively in an agile project. It helps you realize the tester’s role in planning and strategizing for Test Automation in an agile project. It gives you insight into the cost-benefit analysis, the opportunities and risks and the Agile team approaches to let the test-first strategy drive the quality goals of the projects. The course covers BDD and ATDD in a hands-on fashion using pairing techniques of XP. It also covers the real-life challenges that a tester would face while applying the strategies. All the concepts are driven using the case studies and actual test automation tasks involved in any live agile projects. The course introduces you to the automation tools such as Cucumber, JUnit, FitNesse and Selenium.


Am I Eligible?

    Anyone having more than 2 years experience in agile or testing is eligible for CP-AAT. If you have already done CP-MAT then you automatically qualify for this course provided you have 1 year experience.


    CP-AAT is designed specifically for corporates and working professionals alike. If you are a corporate you can opt for either 5 half days course or 3 days course followed by an examination. If you are a working professional opt for 3 days course followed by an examination.

Learning Objectives of CP-AAT


    1. Agile Recap

    1.1. Agile Manifesto

    1.2. Agile Principles

    1.3. Agile in Practice (Video)

    1.4. Agile Mindset

    1.5. Scrum – Testing in iterations

    1.6. Testing challenges in Agile

    1.7. Test Automation


    2. Need for Automation

    2.1. Challenges in Test Automation

    2.2. Regression Testing

    • Regression Strategy in Agile
    • Factors Affecting Regression
    • Automation of the regression suite

    2.3. Automation Strategy

    • Cost-Benefits Analysis
    • Preparation for Automation
    • Opportunities and Risks
    • Test Automation Frameworks
    • Tools evaluation and Pilot

    2.4. Agile Teams

    Cross-functional Testers and Whole Team Approach

    • Energized work
    • Informative workspace
    • Root-cause analysis
    • Coding Standards
    • Iteration demo and reporting
    • Retrospective

    Independent/Specialist Testing Group

    • Right people, right thing
    • Test Hardening
    • Pairing
    • "Done" Done

    2.5. Test-First approach

    • BDD
    • ATDD
    • TDD

    2.6. Behavior and Requirements

    • Behavior of the System
    • Test Case specification
    • User Stories and Scenarios

    2.7. User Stories

    • Attributes of good user stories
    • How to write user stories
    • Is every task a user story?
    • Who writes them?

    2.8. Group Exercise

    • Create features for the given Requirements and User Stories

    2.9. Attributes of a Good feature document


    3. Introduction to Cucumber

    • Behavior in Feature document
    • Step definition
    • Human Language Support
    • Cucumber for Java – Cucumber JVM
    • Testing Possibilities
    • Getting BDD wrong

    3.1. Installation and configuration for Cucumber

    • Installing Eclipse
    • Creating Maven project
    • Maven dependencies
    • Manual setup (non-maven) – required libraries

    3.2. Implementing BDD using Cucumber

    • Preparing Features File having test scenarios
    • Writing a step definition
    • Writing Runner Class
    • Given, When, Then, And, But annotations and usage in features class
    • Passing parameters in Step Functions
    • Using regular expression in steps

    3.3. Test-first concept in Cucumber

    • JUnit Test generation in Cucumber
    • Pretty, Tags and Glue
    • Cucumber HTML Reports
    • Using Assertions to report failure
    • Running simple feature/Step scenario
    • Building a simple test case
    • Running all/limited tests

    3.4. Agile Practical - Sprint 1

    • Cucumber in action
    • Features and Steps definition for Requirements
    • Running the Requirements as Test
    • Retrospective


    4. ATDD and BDD

    • The Test-First AAT Onion
    • Adding Acceptance Test layer to BDD
    • Jumpstarting FitNesse
    • Wikibased, Tabulated Tests
    • FIT and SLiM protocols
    • Fixtures and Refactoring

    4.1. The ATDD Cycle

    • Capturing requirements for ATDD
    • Acceptance Criteria
    • Definition of Done

    4.2. Installing and Configuring FitNesse

    • Capturing requirements for ATDD
    • FitNesse in action
    • ATDD using FitNesse for the given User Story

    4.3. Agile Practical - Sprint 2

    • FitNesse in action
    • ATDD using FitNesse for the given User Story
    • Retrospective

    4.4. Running Fixtures

    • Add logic and assertions to your test
    • Exercise

    4.5. Writing Fixtures using Selenium

    • Drive web based application using Selenium
    • Exercise


    5. Selenium WebDriver

    5.1. WebDriver primer to write the script for Glue code and Fixtures

    5.2. Eclipse

    • Configuring Eclipse for FitNesse and Selenium
    • Running Tests as Fixtures

    5.3. Agile Practical - Sprint 3

    • Importing Selenium Tests as fixtures
    • ATDD using FitNesse and Selenium for the given User Story
    • Retrospective


    6. Practical Agile Testing

    Case Study

    • Practice all BDD and ATDD fundamentals throughout the course on a case study of a dummy project.