Loading Course Schedule...
PT10253
Training Summary
This is a two day overview course which introduces students to the ideas, practices and methodology of Acceptance Test Driven Development (ATDD).The first day explores the collaborative practices used in the ATDD cycle of Discuss - Distill - Develop -Demo from initial requirements and specification by example through writing executable acceptance tests in Gherkin. Emphasis is on the integration of ATDD with other best practices such as continuous testing, software craftsmanship, Agile software delivery, test driven development, Agile testing and others while remaining focused on ATDD within the Capital One IT context. The application of ATDD in the areas of new application development, support programming in existing systems and API or micro-services are covered. The second day focuses on implementing automated acceptance tests using Cucumber, Java, TestNG, Maven and other tools and frameworks used at Capital One. Students work through illustrative examples of converting Gherkin features into test automation code emphasizing the best practices in writing, testing, deploying maintaining the automation code. Automation of tests in web based applications and RESTful APIs are examined in detail.
Prerequisites
None required for the first day, but the second assumes the ability to understand and write Java code at a basic level as well as familiarity with TestNG or a similar automated test environment like JUnit. The ability to use Eclipse as a Java IDE at a basic level is also assumed.
Duration
2 Days/Lecture & Lab
Audience
This course is for anyone who needs to understand what ATDD is, how it is implemented at Capital One. It is directed towards those who have little or no exposure to ATDD and are working with it or will be working with it in some role at Capital One. This class is suitable for testers, developers, Scrum Masters, business analysts and product owners.
Course Topics
Root causes of failures and inefficiencies in software development and delivery.::How ATDD is used to correct or prevent those errors that are the root causes of failure.::The ATDD process Discuss-Distill-Develop-Demo and how it integrates with Agile development.::Discuss Activities delivery of specifications by example and acceptance criteria.::Distill Activities development of lean and robust acceptance tests.::Writing acceptance tests in Gherkin declarative versus imperative.::Gherkin best practices using Scenario Outlines, domain specific language, Scenario and feature file organization.::Testing the tests ensuring the Gherkin acceptance tests are robust and effective.::How Cucumber automates step definitions.::Implementing step definitions in Java.::Using TestNG to run Cucumber Tests::Selective execution of tests using tags.::Implementing Step definitions for generic application interfaces.::Implementing Step definitions for web applications.::Using the Page Object pattern in web testing.::Implementing step definitions for RESTful APIs.::Using ATDD to support and integrate with Test Driven Development.::Using Cucumber in Eclipse and batch environments.