(Target Name) testing plan @ 6.1template

Posted October 16th, 2007 by larryl

Date: Oct.22th 2007 - Nov. 15th 2007

Functional testing

Requirement Priority (only High\Low) Test objective Understand of the requirement (0%-100%) Detailed enough? (0%-100%) Feedback from author? Test cases
  • (Example row) Docking Libarary Zone Behaviors
 High Test all the features in SD_CONTENT which can manipulate SD_CONTENT's zone. 100% :) I'm larry so I know the docking library very well. 100% We test ALL the features in SD_CONTENT, so the cover 100%. Yes, Larry say that's good.
    • (Example sub row) Floating zone
Test all SD_CONTENT zone manipulate features when a zone is floating. Larry reviewed the test cases. He think the this procedure make sense.
  • tcs#80 Moving and resizing a floating zone.
  • tcs#110 Change title/tooltips/description/detail of a floating zone.
  • tcs#122 Change pixmap of a floating zone.
  • tcs#124 Show/hide and close a floating zone.
  • tcs#149 Show tab stub text
      • (Example sub row)Tab zone
...... ...... ......
  • (Example row)Tool Bar Behaviors
 High Test all features in SD_TOOL_BAR_CONTENT. 50% I know the features are control the behaviors of a docking tool bar. But I don't understand how to insert tool bar buttons. 50% Only tested docking tool bar when certain kind of tool bar buttons exist. Larry not reviewed.
  • tcs#186 Show/hide/close a toolbar.
  • tcs#188 Change title of a tool bar.
  • tcs#190 Creating new titlebar after closing an undocked one.
  • tcs#192 Double click on title of a floating toolbar
  • Please extend row here

Nonfunctional testing (Performance, security, compatibility, and usability)

Requirement Priority (only High\Low) Test objective Understand of the requirement (0%-100%) Detailed enough? (0%-100%) Feedback from author? Test cases
  • Please extend row here

Statues: (Used for tacking the testing process) dd/mm/yy updated:

Test Procedure Execution Status (%) Defect Trend Analysis Number of failed high priority TCSs Number of failed low priority TCSs Number of failed TCSs per day Total TCSs

Note

  • Requirement: New feature to be tested
  • Priority: only High\Low
  • Test objective: Briefly describe the purpose of the procedure
  • Understand of the requirement (0%-100%): understand the intricacies of the application's functionality and domain well?
  • Detailed enough? (0%-100%): Are test procedures detailed enough, covering the depth, and combinations and variations of data and functional paths, necessary to catch the higher priority defects? Do tests include invalid data as well as valid data?
  • Feedback from author: ask for test-procedure reviews, inspections, and walkthroughs

Test cases

No test cases for this test plan available.