Software Testing (Cases)
Software Testing (Cases)
TEST PLAN
Test plan is a detailed document which describes software testing areas and
activity.
It outlines test strategy objectives test schedule required resources test
Estimation and test deliverables.
Test plan is a base of every software testing.
Test plan is the project plan required to perform testing of an application or a
system.
Test plan is prepared by the test lead 60% test manager 20% and by the test
engineer 20%
TEST PLANNING ACTIVITIES
To determine the scope and the risk that need to be tested and that are not to
be tested.
documenting test strategy
Making sure that the testing activities have been included
Deciding entry and exit criteria.
Evaluating the test estimate
planning when and how to test and deciding how the test results will be
evaluated and defining test exit criteria.
ensuring that the test documentation generates repeatable test assets
ADVANTAGES OF TEST
PLANNING
Better coverage
Generate more bugs
We only need to define test points during the testing phase
The entire test plan can be reused if regression testing is done later on.
PREPARING A TEST PLAN HOW TO
WRITE A TEST PLAN
Step 1. Purpose of the document it gives the short description about the objective
behind preparation of the document Ex document explaining various activities
performed as a part of testing
Step 2. Overview of an application in this step brief description about the application
to be tested is mentioned
Step 3. Testing scope 1.In scope 2.out of scope 3. item not tested
In this step it gives an explanation about the functions modules in scope and out of
scope for testing along with this.it also gives information about any item which is not
tested due to any restriction.
TEST REPORTING
Step 4. Metrics: In this section it gives information about Metrics these metrics will
help to understand the test execution results status of test cases and defects etc
Ex number of test cases plan versus executed and number of test cases passed or
failed
Step 5. Types of testing performed 1. Smoke testing 2. System integration testing 3.
Regression testing
Step 6. Information of test environment and tools detail of test environment in which
the testing is carried out is given
Information about server database and application URL
Step 7. Lessons learned: This section describes the crucial issues occurred and faced
also gives detailed solution
Step 8. Recommendation suggestions about different activities can be mentioned here
Step 9. Best practices save time good and efficient.
TEST REPORTING
Step 9. Best practices save time good and efficient.
Step 10. Exit criteria
A) all planned test cases are executed.
B)All critical defects are closed etc
Step 11. conclusion/ sign of
TEST REPORTING
Types of test report:
1. Test incident report
A test incident report is communication that happens through the testing cycle as
and when defects are encountered a test incident report is nothing but an entry
made in the defect repository each defect has a unique ID and this is used to
identify the incident defects are highlighted in the test summary report
2. Test summary report
A summary of the activities carried out during that cycle
Defect that were uncovered during that cycle based on their severity and impact
Progress from the previous cycle to the current cycle in terms of defect fixed
Outstanding defects that are yet to be fixed in this cycle.
Any variations observed in effort or schedule