Ensures the product meets the end-user’s expectations and demonstrates the intended use. A streamlined process means fewer errors and delays. This framework decreases confusion, simplifies the release process, and increases efficiency GIVEN a product’s specified behaviors WHEN the product meets the end-user’s expectation AND demonstrates the intended use THEN the product has been validated

1. Behavioral Driven
Validation (BDV)
Ensures the product meets the end-user’s expectations and
demonstrates the intended use.
Price Charlot

2. BDV + Streamlined
Framework
A streamlined process means fewer errors and delays
Price Charlot
 One universal format for user story, use case / DEF (defect,
enhancement, or feature) / test-case, and automation.
 Clear path from user story to use case / DEF / test-case and to
automation
 This framework decreases confusion, simplifies the release process,
and increases efficiency

3. Streamlined Framework
Price Charlot
 LINK: provides the IDs to bind all framework components
 CONSTRUCT: words to use to frame user and system interactions
 USER STORY: feature information gathered from users
 USE CASE / DEF / TEST-CASE: all possible ways the user and system can interact

4. Streamlined Framework Example
Price Charlot
LINK
 TITLE: Redirect HTTP request
 USER_STORY_ID: 1
 USE_CASE_ID: 1
 DEF_ID: 1
 TEST_CASE_ID: 1
 AUTOMATION_ID: 1
USER STORY
 ACTOR: AS_A( system administrator )
 ACTION: I_WANT_TO( redirect all HTTP logins to securely login via HTTPS )
USE CASE / DEF / TEST-CASE
 GIVEN: TRANSPORT( Firefox )
 AND: ISSUE( UI incorrectly allows HTTP access )
 WHEN: GOTO( http://site/login ) URL
 AND: SEND( ENTER ) key
 THEN: FIND( https://site/login ) in the browser URL location bar
 AND: FIND( Username ) field
 AND: FIND( Password ) field
AUTOMATION
 DICTIONARY{ TITLE: “Redirect HTTP request”, USER_STORY_ID: “1”, USE_CASE_ID: “1”, DEF_ID: “1”,
TEST_CASE_ID: “1”, AUTOMATION_ID: “1”, TRANSPROT: “Firefox”, ISSUE: “UI incorrectly allows HTTP access”, GOTO:
“http://site/login”, SEND: “ENTER”, FIND: “https://site/login”, FIND: “Username”, FIND: “Password” }

5.  Price Charlot
Path from DEF to test-case and to
automation
 Test-case created from DEF
 Automation created from test-case

6.  Price Charlot
DEF to new test-case(s)
One to one / One to many
 One DEF may result in one / many test-case(s)
 Many test-cases must be linked to each other
 The test-case(s) must be linked to the one DEF

7.  Price Charlot
DEF to existing test-case(s)
One to one / One to many
 One DEF may have a link to one / many test-case(s) .
 In this case, nothing needs to be done
 One DEF may not have an established link to one / many test-case(s) .
 In this case, a link(s) must be created.

8.  Price Charlot
DEF to existing + new test-case(s)
One to many
 One DEF may not entirely be covered by one / many linked test-case(s)
 In this case, a new test-case(s) must be created
 All the test-case(s) must be linked to the one DEF
 The new and the existing test-case(s) must be linked to each other

9.  Price Charlot
Existing + new DEFs to test-case
Many to one
 Many DEFs may result in one test-case
 The DEF(s) must be linked to the one test-case

10.  Price Charlot
Existing + new DEFs to existing + new
test-cases
Many to many
 Many DEFs may result in many test-cases
 The test-cases must be linked to each related test-case
 The DEFs must be linked to each resulting test-case

11.  Price Charlot
Test-case to existing or new automation
One to one / One to none
 One test-case may result in one automation dictionary
 The test-case must be linked to the automation
 Relationship between test-case and automation is always one to one
 A test-case may not be automatable.
 In this case, the LINK “AUTOMATION_ID:” is set to “-1”

12. Automation Framework Example
Price Charlot
AUTOMATION
 DICTIONARY{ TITLE: “Redirect HTTP request”, USER_STORY_ID: “1”, USE_CASE_ID: “1”, DEF_ID: “1”,
TEST_CASE_ID: “1”, AUTOMATION_ID: “1”, TRANSPROT: “Firefox”, ISSUE: “UI incorrectly allows HTTP
access”, GOTO: “http://site/login”, SEND: “ENTER”, FIND: “https://site/login”, FIND: “Username”, FIND:
“Password” }

13.  Price Charlot
Premises and Conclusions
 GIVEN a product’s specified behaviors
 WHEN the product meets the end-user’s expectation
 AND demonstrates the intended use
 THEN the product has been validated