VodQA3_ATDD_KetanSoni

Acceptance Test Driven Development (ATDD) in practice ,[object Object]

Typical flow in industry BAs specify requirements Devs develop functionality QAs identify test scenarios BAs verifies functionality Business sign off QAs -Testing + automate scenarios

From “Functional Test” perspective what all problems / concerns do you guys see in this flow? From Devs perspective ,[object Object],[object Object],From QA s perspective ,[object Object],[object Object],[object Object],From Team perspective ,[object Object]

How to overcome problems? “ Begin with the end in mind.” — Stephen R. Covey One way that worked for us: Acceptance Test Driven Development (ATDD) is a practice in which the whole team collaboratively discusses acceptance criteria, with examples, and then distills them into a set of concrete acceptance tests before development begins.

[object Object],Login functionality… As a user When I enter login credentials Then I should get authenticated

[object Object],Executable test scenarios in human readable format… Scenario 1 : Verify valid login credentials… Given I am on login page When I login as username “test” and password “testing” Then I should get authenticated Scenario 2 : Verify logout functionality… Given I am a logged in user When I click on “logout” link Then I should be logged out BA Verify

[object Object],Application code to make the above statements pass… //Create login page // Implement the back-end for login functionality… Scenario 1 : Verify login functionality… Given I am on login page When I login as username “test” and password “testing” Then I should get authenticated… Test Scenario … Scenario 1 : Verify login functionality… Given I am on login page When I login as username “test” and password “testing” Then I should get authenticated 1) Developers run this test scenario and expect it to fail 2) To make the above executable statements pass, developer write the application and implement the login functionality… 3) Developers run the test scenario mentioned in step 1 and expect it to pass…

[object Object],Scenario : Verify login and logout functionality… Given I am on login page When I login as username “test” and password “testing” Then I should get authenticated When I click on “logout” link Then I should logout + Consolidation of test scenarios… MANUAL TESTING

Typical ATDD flow… 1 QAs + BAs write scenarios 1 Developers implement scenarios 1 QAs - Manual Testing and consolidation of scenarios

[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],Benefits of ATDD…

VodQA3_ATDD_KetanSoni

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (20)

Similar to VodQA3_ATDD_KetanSoni

Similar to VodQA3_ATDD_KetanSoni (20)

More from vodQA

More from vodQA (20)

Recently uploaded

Recently uploaded (20)

VodQA3_ATDD_KetanSoni