The document discusses test requirements, which define what needs to be tested to validate a system's functionality and behavior. Test requirements are derived from sources like business requirements, use cases, and previous testing deliverables. They form the basis for establishing a testing effort and determining test coverage. The document provides examples of writing test requirements and organizing them in a hierarchy to aid in generating test cases and measuring test completion.

1. Test Requirements: The Basis of Testing David Capocci, CQA, CSTE Sr. QA Systems Analyst SAFECO Corporation [email_address]

11. Drilling down: Where test requirements fit into the picture Business Requirement Test Requirement Test Scenarios/ Cases Test Procedure/ Script Fitting TR’s into the testing picture Generates 1 M Generates 1 M Executes/Runs 1 M

12. Drilling Down Business Requirement Test Requirement Test Scenarios/ Cases Test Procedure/ Script Fitting TR’s into the testing picture First, Let’s look at this relationship: What’s within our testing process Then we’ll look at this relationship: Gernerating TR’s from what feeds into our testing process

15. Test Scenarios/Cases for - “Validate that a withdrawal of a multiple of $20, between $20-$300 can be done” What’s within our testing process

18. The Workbench Concept Generating TR’s Our workbench is called “Generating Test Requirements” DO DO Check Standards Tools Rework Entrance Criteria Exit Criteria Product Input Product Output

28. Remember this?…Drilling down Fitting TR’s into the testing picture

29. Decomposing: Drilling down within a Test Requirement Business Requirement Test Requirement Test Scenarios/ Cases Test Procedure/ Script Fitting TR’s into the testing picture Keep the function-based perspective in mind! Business Function Tasks within the Function Data Entry Types for transactions Transactions to perform a task Field Validation

30. Test Requirement Decomposition Decomposing TR’s

31. Test Requirement Decomposition Business Function Tasks within the Function Data Entry Types for transactions Transactions to perform a task Field Validation High level Functional Areas: usually from “ Functional Spec” type docs, or BA work Lower level Functional Areas: usually from “ Technical Spec” type docs regarding internal logic, or PA work Decomposing TR’s