2.
Testing Documentation
2.1 Test
Plan
The Test
Plan document on the other hand, is derived from the Product Description,
Software
Requirement
Specification SRS, or Use Case Documents.
The Test Plan document is usually prepared by the Test Lead or Test Manager and the focus of the
The Test Plan document is usually prepared by the Test Lead or Test Manager and the focus of the
document
is to describe what to test, how to test, when to test and who will do what
test.
When a
testing phase starts and the Test Manager is “controlling” the activities, the
test plan should be
updated
to reflect any deviation from the original plan.
After all, Planning and Control are continuous
activities in the formal test process.
§ Test Plan id
§ Introduction
§ Test items
§ Features to be tested & not to be tested
§ Test techniques
§ Features pass or fail criteria
§ Test environment (Entry criteria, Exit criteria)
§ Test deliverables
§ Staff and training needs
§ Responsibilities
§ Schedule
This is a
standard approach to prepare test plan and test strategy documents, but things
can vary Company-to-company
2.2 Testing Strategy
A Test
Strategy document is a high level document and normally developed by project
manager. This document defines “Testing Approach” to achieve testing
objectives. The Test Strategy is normally derived from the Business Requirement
Specification document.
Usually
in the case for small projects “Test Approach” or “Strategy” inside the Test
Plan. However, for
larger
projects, there is one Test Strategy document and different number of Test
Plans for each phase
or level
of testing.
Components
of the Test Strategy document
§ Scope and Objectives
§ Business issues
§ Roles and responsibilities
§ Communication and status reporting
§ Test deliverability
§ Industry standards to follow
§ Test automation and tools
§ Testing measurements and metrics
§ Risks
§ Defect reporting and tracking
§ Change and configuration management
§ Training plan
2.3
Test Scenario
A set of test cases that ensure that the
business process flows are
tested from end to end. They may be
Independent tests or a series of tests
that follow each other, each dependent on the output of the previous one.
2.4
Test Suit
Test
suit is a
collection of test cases that are
intended to be used to test a software program to show that it
has some specified set of behaviors. A
test suite often contains detailed instructions or goals for each
collection of test cases and information
on the system configuration to be used during testing. A group
of test cases may also contain
prerequisite states or steps, and descriptions of the following tests.
2.5
Test Case
A test case is
a set of conditions or variables under which a tester will determine whether an application
or software
system is working correctly or not.
Fields in test cases:
Test case id, Unit to test, What to be verified, Assumptions,
Test data, Variables and their valuesSteps to be executed, Expected result, Actual result, Pass/Fail.
0 comments:
Post a Comment