P15 Acceptance - Test Execution

More documents

Recommendations

Info

Before <strong>Test</strong>ing Have all requirements been reviewed and approved including changes? Have test criteria for requirements/use cases been developed? Has the test plan been developed, reviewed and approved including acceptance criteria? Are test cases written, traceability matrix complete? Have they been reviewed and approved? Are resources available and appropriately trained? Has the test environment been established including test data? Have supporting test tools been established for recording and reporting test results? 18 © 2007 The University of Texas at Austin
Documenting <strong>Test</strong> Case Results Evaluate test results Pass – the test results match the expected results Fail – the test results do not match the expected results When a test fails: Be sure it’s the software and not the test design at fault Review the data inputs are correct Rerun the test, if necessary Document results by recording When the test took place Pass/Fail 19 © 2007 The University of Texas at Austin
Page 1 and 2: Test Execution Developing Test Cas
Page 3 and 4: Dynamic Testing Quality cannot be
Page 5 and 6: Developer Tests White box testing
Page 7 and 8: System Test Cases Are designed to
Page 9 and 10: Combined System/Acceptance Testing
Page 11 and 12: Acceptance Test Cases Designed to
Page 13 and 14: What does a test case look like? T
Page 15 and 16: Test Case Example Steps: 1)Enter a
Page 17: a s t i s e ld Traceability Matrix
Page 21 and 22: Problem Reporting System Identify
Page 23 and 24: Prioritizing Fixes and Changes Hig
Page 25 and 26: Guide for Test Reporting Structure
Page 27 and 28: Debugging Process initiated when a
Page 29 and 30: Don’t Don t Forget Regression Tes
Page 31 and 32: Good Enough Testing Knowing when to
Page 33: Next… Next Software Acceptance…

P15 Acceptance - Test Execution

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?