Project Plan
- Sprint
- Feature
- BugFix
- Sprint
Test Plan
- BDD
- who is creating/consuming the BDD?
- if BDD syntax is not an input to a Sprint,
- unit testing removes this interpretation layer
- test case verbiage -> BDD verbiage
- BDD verbiage -> logic
- test case verbiage -> BDD verbiage
- allowing instead:
- test case verbiage -> logic
- Define quality Test Steps in the Test Case Specification
- Can still have self-describing automation, but not bound to bdd framework
- TestNG also allows for tagging
- unit testing removes this interpretation layer
- perhaps force BDD logic upstream
- QA involved when defining the feature
- feature & test scenarios created at same time
- TestNG driven tests
- macros
- macros
- Process
- Feature -> Test Cases
- Test Cases -> BDD
- BDD -> Automation
- Unit Testing
- Feature -> Test Cases
- Test Cases -> Automation
Test Case Manager
Test Case to Automation Mapping
Results Requirements
Test Product Development Process
- Log in to post comments
