creating test case content how to successfully integrate acceptance criteria
TRANSCRIPT
Introduction
• What We’ll Be Talking About– A Little Review– Functional Specifications and Acceptance
Criteria– Creating Test Cases– Searching for Test Cases– A Note on Parent Issues– A Note on Tasks– Getting Good Coverage in Your Test Cases– Getting Good Coverage in Your Test Scripts
Review
• Review of JIRA Issues Types– Story• Functional Specification (FSPEC)• Acceptance Criteria (AC)
– Task– Bug/Defect– Test Case
Review
Issue Type Location Purpose
User Story OLE Project Main Issue Type
Task OLE Project “To Do” for Coders
Bug/Defect OLE Project “To Do” for Broken Functions
Test Case OLETS Project
One Item from AC
Review
• Review of JIRA Relationships– Parent• Story to Test Case• One-Way Link
– Tests/Tested By• Task to Test Case• Bug/Defect to Test Case• Two-Way Link
Review
Issue Type Location Purpose Relationship to Test Cases
User Story OLE Project Main Issue Type
Parent
Task OLE Project “To Do” for Coders
Tested By
Bug/Defect OLE Project Fix for Broken Functions
Tested By
Test Case OLETS Project
One Item from AC
Functional Specifications and Acceptance Criteria
• Review–What is a Functional Specification?• A Functional Specification is a document
that elaborates upon a user-derived story.– Workflow– Detailed Output Needs
Functional Specifications and Acceptance Criteria
• Review–What is a Functional Specification?• Functional Specifications have an organic
structure.
Functional Specifications and Acceptance Criteria
• Review–What are Acceptance Criteria?• Acceptance Criteria are statements of what
will be tested to ensure functionality.• Acceptance Criteria are a crystallization of
a Functional Specification’s essence.
Functional Specifications and Acceptance Criteria
• Acceptance Criteria Coverage of Functional Specifications
Functional Specifications and Acceptance Criteria
• Acceptance Criteria and Test Cases– Description– Story Fulfillment
Creating Test Cases
• Double-Check the Acceptance Criteria
• Creating the Test Case–Use the Acceptance Criteria as your
checklist.
Creating Test Cases
• Creating the Test Case– Summary Field• Contracted Acceptance Criteria Statements
Creating Test Cases
• Creating the Test Case– Description• Full Acceptance Criteria Statement• Steps
Searching for Test Cases
• Connect to the OLE Test Scenarios (OLETS) JIRA Project– https://jira.kuali.org/browse/OLETS
• Log In
Searching for Test Cases
• Refresh the Search
• Search for Issues You Created– Reporter• Current User
A Note on Parent Issues
• Functional Specification• Coding Complete– For Stories– For Bug/Defects– Link to Milestone Release
Documentation• https://wiki.kuali.org/display/OLE/
OLE+Release+Documentation+-+for+Milestone+0.8
A Note on Parent Issues
• All Tasks Are in “Testing” Status– “Issue Links” Section– “Relies On” Subsection
A Note on Tasks
• Correspondence between Tasks and Test Cases– Tasks are organic, created in response
to a need.– Test Cases are planned, pre-defined by
Acceptance Criteria.
A Note on Tasks
• If a piece of AC seems to be missing, it may not be ready for implementation at this time.– Check with the QA Team
Good Test Case Coverage
• Fulfilling All Parts of an AC Statement– Evaluate each clause individually.• “User is able to select multiple pre-order
documents [‘requisitions’] and review the calculated price total of all selected pre-order documents.” (OLE-27, Order Holding Queue)– “User is able to select multiple pre-order
documents” on the Order Holding Queue interface.
– “User is able to calculate the total price of all selected pre-order documents” in the Order Holding Queue.
Good Test Case Coverage
• Fulfilling All Parts of an AC Statement– Breaking Down AC into Actual Steps• Try It Out
– Latest Driver’s Manual: https://wiki.kuali.org/display/OLE/OLE+0.6+Milestone+User+Documentation
• Take Notes• Be Clear, But Be Brief
– “Brevity is a great charm of eloquence.” – Cicero
Good Test Script Coverage
• Ensure All Statements Are Covered– Don’t Forget the AC Checklist– Break It Up• Into Two Scripts• Into Sections Within the Script