System Test Plan {STP}
Printed From: One Stop Testing
Category: Software Testing @ OneStopTesting
Forum Name: Test Plans @ OneStopTesting
Forum Discription: Discuss, Learn and Prepare better and better Test Plans for yourself.
URL: http://forum.onestoptesting.com/forum_posts.asp?TID=2863
Printed Date: 04Jun2024 at 9:21am
Topic: System Test Plan {STP}
Posted By: tanushree
Subject: System Test Plan {STP}
Date Posted: 15Oct2007 at 4:13am
System Test Plan {STP}
The
system test plan is the overall plan carrying out the system test level
activities. In the system test, apart from testing the functional
aspects of the system, there are some special testing activities
carried out, such as stress testing etc. The following are the sections
normally present in system test plan
What is to be tested?
This
section defines the scope of system testing, very specific to the
project. Normally, the system testing is based on the requirements. All
requirements are to be verified in the scope of system testing. This
covers the functionality of the product. Apart from this what special
testing is performed are also stated here.
Functional Groups and the Sequence
The
requirements can be grouped in terms of the functionality. Based on
this, there may be priorities also among the functional groups. For
example, in a banking application, anything related to customer
accounts can be grouped into one area, anything related to inter-branch
transactions may be grouped into one area etc. Same way for the product
being tested, these areas are to be mentioned here and the suggested
sequences of testing of these areas, based on the priorities are to be
described.
Special Testing Methods
This
covers the different special tests like load/volume testing, stress
testing, interoperability testing etc. These testing are to be done
based on the nature of the product and it is not mandatory that every
one of these special tests must be performed for every product.
Apart from the above sections, the following sections are addressed, very specific to system testing.
• System Testing Tools
• Priority of functional groups
• Naming convention for test cases
• Status reporting mechanism
• Regression test approach
• ETVX criteria
• Build/Refresh criteria
|
|