A software project test plan is a document that describes the objectives, scope, approach, of a software testing effort. The completed document will help people outside the test group understand the 'why' and 'how' of product validation.
Showing posts with label test plan. Show all posts
Showing posts with label test plan. Show all posts
Saturday, August 20, 2011
Thursday, April 16, 2009
What is staffing and training needs in a test plan?
Staffing and Training
This section of the test plan describes the number of people required and what skills they need to possess.
Labels:
automated test,
Staff function,
staffing,
test plan,
training
What are testing tasks in test plan?
Testig Tasks
this part of testing plan identifies the set of tasks necessary to prepare for and perform testing.
Labels:
identify task,
set of tasks,
test plan,
Testing,
Testing Tasks
What is test deliverables in test plan?
Test Deliverables
This is a listing of all the documents, tools and other components that to be developed and maintained in support of the testing effort.
Labels:
components,
deliverables,
documents,
Planning,
Sqa plan,
support,
test,
test deliverable,
test plan,
Testing effort,
tools
What is suspension criteria and resumption requirements in test plan?
suspension criteria and resumption requirements
The purpose of this section of the test plan is to identify any conditions that warrant a temporary suspension of testing and the criteria for resumption.What is 'approach' in test plan?
Approach in Test Plan
This section can be divided into a number of sub sections- Methodology
- Configuration management
- Metrics collection
- Tools and Automation
Labels:
approach,
automation,
configuration management,
methodology,
metric,
metric collection,
test approach,
test plan,
tools
What is 'item pass/ fail creteria' in test plan?
Item Pass /Fail criteria
This section of the test plan describes the pass/fail criteria for each of the items described in Test items.Sample Pass/Fail criteria for System testing
- 90% of the test cases must pass
- All test cases dealing with critical functionality must pass
- All medium and high severity defects must be fixed
- Test coverage must be at least 90%
Labels:
Creteria,
critical,
Functionality,
high severity,
Item,
Item Fail,
Item pass,
medium,
pass,
System testing,
test case,
test coverage,
test plan
What are the 'features not to be tested' in test plan?
features Not to be Tested
This section of the test plan is used to record any features that will not be tested and why.
Labels:
features not be tested,
First time testing,
record,
section,
Software,
test plan,
Tested
What are test items in test plan?
Test Items
This section of the test plan describes what is to be tested within the scope of this test plan.What are the 'features to be tested' in test plan?
Features to be tested in Test Plan
This section of the test plan includes a listing of what will be tested from the user or customer point of view as opposed to test items, which are a measure of what to test from the viewpoint of supplier.What is in introdcution of test plan?
Introduction
There are two main things to include in introduction section of test plan- Scope of the project
- Scope of the plan
What are test different test planning at differebt stages of STLC?
Stages of test planning
Requirements -> Master/ Acceptance Test Plan
Design ->System Test Plan
Code -> Integration Test Plan
Implementation -> Unit Test Plan
Thursday, April 9, 2009
What is the standard for software testing documentation?
IEEE Std 829-1998 Standard for Software Test Documentation
Contents
1.Test Plan
2.Test Design Specification
3.Test Case Specification
4.Test Procedure Specification
5.Test Log
6.Test Incident Report
7.Test Summary Report
Friday, March 27, 2009
When reviews are needed? or What are the reasons for reviews?
Reviews are necessary due to following reasons:
- Reviews are useful not only for finding and eliminating defects, but also for gaining consensus among the project team, securing approval from stakeholders, and aiding in professional development for team members.
- Reviews help teams find defects soon after they are injected making them cost less to fix than they would cost if they were found in test.
- All work products in a software project should be either reviewed or tested.
Labels:
defect reports,
flawed test cases,
review worth,
SFS,
SRS,
test plan,
Tested
Subscribe to:
Posts (Atom)