Your SlideShare is downloading. ×
0
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
IEEE Standard 829 Software Testing
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

IEEE Standard 829 Software Testing

2,441

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,441
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
109
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. IEEE Standard 829 Software Testing CEN 5016 © Dr. David A. Workman School of EE and CS University of Central Florida March 26, 2003
  • 2. IEEE Std (829) for Software Testing PROJECT DOC ITEM DOC TEST ITEM TEST PLAN TEST DESIGN SPEC TEST DESIGN SPEC TEST DESIGN SPEC TEST CASE SPEC TEST PROCEDURE SPEC TEST ITEM TRANSMITTAL REPORT TEST EXECUTION TEST EXECUTION TEST SUMMARY REPORT TEST INCIDENT REPORT TEST LOG TEST LOG TEST INCIDENT REPORT
  • 3. IEEE Std (829) for Software Testing <ul><li>Test Plan </li></ul><ul><ul><li>To prescribe the scope, approach, resources, and schedule of testing activities. To identify items to be tested , the features to be tested , the testing tasks to be performed, the personnel responsible for each task , and the risks associated with the plan. </li></ul></ul><ul><li>Test Design Spec (details of plan – specifics) </li></ul><ul><ul><li>To specify refinements of the test approach and to identify the features to be tested by this design and its associated test cases. </li></ul></ul><ul><li>Test Case Spec </li></ul><ul><ul><li>To define a test case identified by a test design specification. </li></ul></ul><ul><li>Test Procedure Spec </li></ul><ul><ul><li>To specify the steps for executing a set of test cases or, more generally, the steps used to analyze a software item in order to evaluate a set of features. </li></ul></ul><ul><li>Test Item Transmittal Report </li></ul><ul><li>Test Log </li></ul><ul><li>Test Incident Report </li></ul><ul><li>Test Summary Report </li></ul>
  • 4. IEEE Std (829) for Software Testing <ul><li>Test Plan </li></ul><ul><li>Test Design Spec </li></ul><ul><li>Test Case Spec </li></ul><ul><li>Test Procedure Spec </li></ul><ul><li>Test Transmittal Report </li></ul><ul><ul><li>To identify the test items being transmitted for testing. It includes the person responsible for each item, its physical location, and its status. Any variations from the current item requirements and designs are noted in this report. </li></ul></ul><ul><li>Test Log </li></ul><ul><ul><li>To provide a chronological record of relevant details about the execution of tests. </li></ul></ul><ul><li>Test Incident Report </li></ul><ul><ul><li>To document any event that occurs during the testing process that requires investigation. </li></ul></ul><ul><li>Test Summary Report </li></ul><ul><ul><li>To summarize the results of the designated testing activities and to provide evaluations based on these results. </li></ul></ul>
  • 5. Test Plan <ul><li>Outline </li></ul><ul><ul><li>a) Test plan identifier; </li></ul></ul><ul><ul><li>b) Introduction; </li></ul></ul><ul><ul><li>c) Test items; </li></ul></ul><ul><ul><li>d) Features to be tested; </li></ul></ul><ul><ul><li>e) Features not to be tested; </li></ul></ul><ul><ul><li>f) Approach; </li></ul></ul><ul><ul><li>g) Item pass/fail criteria; </li></ul></ul><ul><ul><li>h) Suspension criteria and resumption requirements; </li></ul></ul><ul><ul><li>i) Test deliverables; </li></ul></ul><ul><ul><li>j) Testing tasks; </li></ul></ul><ul><ul><li>k) Environmental needs; </li></ul></ul><ul><ul><li>l) Responsibilities; </li></ul></ul><ul><ul><li>m) Staffing and training needs; </li></ul></ul><ul><ul><li>n) Schedule; </li></ul></ul><ul><ul><li>o) Risks and contingencies; </li></ul></ul><ul><ul><li>p) Approvals. </li></ul></ul>
  • 6. Test Design Spec <ul><li>Outline </li></ul><ul><ul><li>a) Test design specification identifier; </li></ul></ul><ul><ul><li>b) Features to be tested; </li></ul></ul><ul><ul><li>c) Approach refinements ( refinements or deviations from the Test Plan ) </li></ul></ul><ul><ul><li>d) Test identification (identify the Test Case Specs for this Test Design) </li></ul></ul><ul><ul><li>e) Feature pass/fail criteria. </li></ul></ul>
  • 7. Test Case Spec <ul><li>Outline </li></ul><ul><ul><li>a) Test case specification identifier; </li></ul></ul><ul><ul><li>b) Test items; </li></ul></ul><ul><ul><li>c) Input specifications; </li></ul></ul><ul><ul><li>d) Output specifications; </li></ul></ul><ul><ul><li>e) Environmental needs; </li></ul></ul><ul><ul><li>f) Special procedural requirements; </li></ul></ul><ul><ul><li>g) Inter-case dependencies. </li></ul></ul>
  • 8. Test Incident Report <ul><li>Outline </li></ul><ul><ul><li>a) Test incident report identifier; </li></ul></ul><ul><ul><li>b) Summary; </li></ul></ul><ul><ul><li>c) Incident description: </li></ul></ul><ul><ul><ul><li>a) Inputs; </li></ul></ul></ul><ul><ul><ul><li>b) Expected results; </li></ul></ul></ul><ul><ul><ul><li>c) Actual results; </li></ul></ul></ul><ul><ul><ul><li>d) Anomalies; </li></ul></ul></ul><ul><ul><ul><li>e) Date and time; </li></ul></ul></ul><ul><ul><ul><li>f) Procedure step; </li></ul></ul></ul><ul><ul><ul><li>g) Environment; </li></ul></ul></ul><ul><ul><ul><li>h) Attempts to repeat; </li></ul></ul></ul><ul><ul><ul><li>i) Testers; </li></ul></ul></ul><ul><ul><ul><li>j) Observers. </li></ul></ul></ul><ul><ul><li>d) Impact: </li></ul></ul><ul><ul><ul><li>If known, indicate what impact this incident will have on test plans, test design specifications, test procedure specifications, or test case specifications. </li></ul></ul></ul>
  • 9. Test Summary Report <ul><li>Outline </li></ul><ul><ul><li>a) Test summary report identifier; </li></ul></ul><ul><ul><li>b) Summary: </li></ul></ul><ul><ul><ul><li>Summarize the evaluation of the test items. Identify the items tested, indicating their version/revision level. </li></ul></ul></ul><ul><ul><ul><li>Indicate the environment in which the testing activities took place. </li></ul></ul></ul><ul><ul><ul><li>For each test item, supply references to the following documents if they exist: test plan, test design specifications, test procedure specifications, test item transmittal reports, test logs, and test incident reports. </li></ul></ul></ul><ul><ul><li>c) Variances; </li></ul></ul><ul><ul><li>d) Comprehensive assessment; </li></ul></ul><ul><ul><li>e) Summary of results: </li></ul></ul><ul><ul><ul><li>Summarize the results of testing. Identify all resolved incidents and summarize their resolutions. Identify all unresolved incidents. </li></ul></ul></ul><ul><ul><li>f) Evaluation: </li></ul></ul><ul><ul><ul><li>Provide an overall evaluation of each test item including its limitations. This evaluation shall be based upon the test results and the item level pass/fail criteria. An estimate of failure risk may be included. </li></ul></ul></ul><ul><ul><li>g) Summary of activities; </li></ul></ul><ul><ul><li>h) Approvals. </li></ul></ul>
  • 10. Team Testing Requirements <ul><li>Each team lead will prepare a Test Plan that summarizes the formal testing effort for some (small set of) component(s) assigned to each of the other team members. </li></ul><ul><li>Each team member (other than the lead) shall prepare a Test Design Spec and Test Case Specs for the part of the system identified in the Test Plan that was assigned to that individual. It is not necessary to prepare formal documentation for all planned or performed testing activities, just a part that is critical to success of the overall testing effort. </li></ul><ul><li>Each team lead will prepare a Test Summary Report to describe the results of all formally conducted testing activities. </li></ul>Consult the Program Manager when deciding what system components should be formally tested.

×