Acceptance Criteria, Test Scripts & Testing

Testing Approach

1. Specification team or SME Team nomination of a team member to be the testing coordinator for the stories
2. Acceptance criteria needs to be very clear 
3. QA/SA anticipate producing an independent document back to the team and/or testing coordinator for sign off
4. After acceptance criteria generated and during the coding effort, QA Manager/Testing team will work with the spec team testing coordinator (or designate) to develop step by step detailed test scripts
5. Once coding is complete, QA Manager will work with the testing coordinator to actually test the code based on the scripts
   1. We expect at least one tester will make a recording of the test script with Selenium IDE (a test script recorder)
   2. Training and directions for storing the recording will be provided by QA Manager.

Acceptance Criteria

Sample from Loading Records:

• 
  

• 
  

Sample: Acceptance Criteria

Acceptance criteria (otherwise known as "fit criteria" or "test completion criteria") define the boundaries of a user story, and are used to confirm when a story is completed and working as intended. AC should quantify the behavior, the performance or some other demonstrable quality of the final end product (coded function).

Including acceptance criteria is required as part of User Stories & Requirements so that:

• Users think through how a feature or piece of functionality will work from the user’s perspective
• We remove ambiguity from requirements
• AC form the basis for user tests & test scripts that will confirm that a feature or piece of functionality is working and complete.

Acceptance criteria may test the entire user story, or if multiple user stories are combined into one spec, then multiple acceptance criteria may need to be written.

Examples:

• User Story:As a Data Creator, I create purchase orders for a resource linked to a bib and/or item record (create PO).
• Acceptance Criteria:
  • A user must be able to allocate multiple fund codes across line items and within each line item being ordered.
  • An Item record is created for every PO line item.
  • I must be able to place orders to vendors in USD or foreign currency.

• User Story:As a Selector, I need a holding area for items for potential future actions (Order Holding Queue).
• Acceptance Criteria:
  • A selector must be able to search Requisitions, and then select requisitions to calculate totals across multiple requisitions selected.
  • A selector, with proper permissions, should be able to "take" or "assign" requisitions to Selectors.

Test Scripts

Test Scripts will require additional "testing" designated SMEs from Spec teams or functional areas to work with the QA Manager to develop Test Scripts based on the Acceptance Criteria developed in User Requirements.

Additional KFS-related Test Script Resources:

• KFS Functional Testing (reference only)
• Resources/Templates: KFS-Jira Test Scenarios for PURAP.
• Maintenance Docs run-throughs: KFS Maintenance Docs
• Vendor run-throughs: KFS Vendor test docs
• KFS PURAP e-doc tests:(to formulate search, biz rules)
• See: KFS 4.1 Driver's Manual (scenarios)
• Users/Routing Template: KFS PURAP Roles-Permissions

User Acceptance Testing

(coming soon)

, May 2011

SME Team Spec Testers