TM
Behaviour Driven Testing
with
Copyright © 2009 NMQA Ltd.
TM
The Traditional Test methodology:
Copyright © 2009 NMQA Ltd.
TM
The Common Test methodology:
Copyright © 2009 NMQA Ltd.
TM
The Behaviour Driven Testing methodology:
Copyright © 2009 NMQA Ltd.
TM
The Behaviour Driven Testing methodology:
• Helps with STORY DEFINITION to avoid ILL DEFINED requirements
• Focuses on identifying BUSINESS VALUE and not ABSTRACT IDEAS
• Focuses on CUSTOMER USE over the TECHNICAL IMPLEMENTATION
• Focuses on FINDING BUGS and not on CONFIRMING COMPLETNESS
Focus on value to the user
Copyright © 2009 NMQA Ltd.
TM
Strengthened relationships through BDT:
Stakeholder / User
Business Analyst
Stories / Requirements / Needs
Business Analyst
Tester
Refined (Test) Scenarios / Automated Tests
Tester
Developer

Code Deploy / Test Execution / Accepted system
Copyright © 2009 NMQA Ltd.
TM
The flow of the BDT methodology:
BUSINESS ANALYST identifies the FEATURES the
CUSTOMER/USER wants
FEATURES are captured in Vienna as REQUIREMENTS
TEST SCENARIOS are written in Vienna as Test Cases
Developer writes code that make TEST CASES PASS
Copyright © 2009 NMQA Ltd.
TM
The flow of the BDT methodology:
TEST CASES get AUTOMATED by the testers
Code is DEPLOYED and Testers perform a Vienna Test Run
BUGS get fixed, automated tests run as REGRESSION TESTS
When done Customer / User ACCEPTS the software
(Acceptance & Quality Criteria met)
Copyright © 2009 NMQA Ltd.
TM

SEMI AUTOMATED / MANUAL TEST EXECUTION
Behaviour Driven Testing
Exploratory Testing
• Learn, plan and execute at once
• Look for bugs, missing features and opportunities for improvement
Combination/Interaction Testing
• Focus on interactions between features
Scenario Testing
• Use combined real-world scenarios that exercise multiple stories
Business Cycle Testing
• Execute scenarios based on end of day/month/qtr/year business tasks
Non-Functional / Para-Functional Testing
• Performance, Security, Accessibility, Compatibility
http://www.io.com/%7Ewazmo/papers/agile_testing_challenges.pdf
Copyright © 2009 NMQA Ltd.
TM
Behaviour Driven Testing and Vienna
• Manage FEATURES as FUNCTIONAL REQUIREMENTS
• Manage SCENARIOS as TEST CASES
• Use all other modules as standard to manage testing
Copyright © 2009 NMQA Ltd.
TM
Behaviour Driven Testing and Vienna
• Requirements written in NATURAL LANGUAGE
• Easy for all project participants to work with and contribute to
• Creates Requirements Documentation linked with other artefacts
Copyright © 2009 NMQA Ltd.
TM
Behaviour Driven Testing and Vienna
• Test Cases provide Context, Purpose and Expected Outcome
• This format makes it easy for ‘non-testers’ to add tests
• Developers can implement the Test Cases so they pass
Copyright © 2009 NMQA Ltd.
TM
The BDT Test methodology:
Copyright © 2009 NMQA Ltd.
TM
Vienna – Running a Selenium-Ruby Automated Test
Copyright © 2009 NMQA Ltd.
TM
The BDT Test methodology:
Copyright © 2009 NMQA Ltd.
Vienna Test Management
Thank you for your time
Any Questions?
TM