You are on page 1of 2

TEST MANAGEMENT

1. TEST SCENARIO
= ANY FUNCTIONALITY THAT CAN BE TESTED
=TEST CONDITION/TEST POSSIBILITY
=IS A VARIANT OF SOFTWARE TESTING SCENARIOS ARE USED FOR TESTING
=SCENARIOS CREATE AN EASIER WAY OF TESTING THE MORE COMPLICATED SYSTEMS
WHY?
- ENSURES COMPLETE TEST COVERAGE
- CAN BE APPROVED BY VARIOUS STAKEHOLDERS
- THEY SERVE  QUICK TOOL  TO DETERMINE THE TESTING WORK EFFORT
- THEY HELPDETERMINE THE MOST IMPORTANT END TO END TRANSACTIONS
How?
Step 1: read the REQUIREMENT DOCUMENTS
Step 2: for each REQUIREMENTFIGURE OUT POSSIBLE USERS ACTIONS +OBJECTIVES
Step 3: AFTER reading the REQUIREMENTS DOCUMENT +doing your due ANALYSISLIST OUT
DIFFERENT TEST SCENARIO THAT VERIFY EACH FEATURE OF THE SOFTWARE
Step 4: the scenarios created  ARE REVIEWED BY YOUR SUPERVISOR.

2. TEST CASE
- A set of actions executed to verify a particular feature or functionality of your software
application
- TEST SCENARIOS=ARE RATHER VAGUE+COVER A WIDE RANGE OF POSSIBILITIES
- TESTING BEING A VERY SPECIFIC,HENCE,TEST CASES ARE CREATED
Things to include in a Test Case:
- The description of what requirement is being tested
- The explanation of how system will be tested
- The test setup like:version of application under test, software,data files,operating
system,hardware,security access
- Inputs and outputs or actions and expected results
SOME BEST PRACTICES:
TEST CASES NEED TO BE SIMPLE
CREATE TEST CASE WITH END USER IN MIND
AVOID TEST CASE REPETITION
TEST CASES MUST BE IDENTIFIABLE

3. TRACEABILITY MATRIX
- A traceability matrix a document that co-relates any two-baseline documents that
require a many to many relationship to check the completeness of the relationship.
- Requirement Traceability Matrix or RTM captures all requirements proposed by the client
or software development team and their traceability in a single document delivered at the
conclusion of the life cycle.
- Types of Traceability Matrix:
- FORWARD TRACEABILITY: It is used to check wheather the project progresses in the
desired direction and for the right product.
- BACKWARD OR REVERSE TRACEABILITY:It is used to ensure wheather the current product
remains on the right track.The scope of the project is not expanded
- BI-DIRECTIONAL TRACEABILIRY (FORWARD AND BACKWARD) :this traceability matrix
ensures that all requirementa are covered by test cases
-
4. TEST PLAN: a detailed document outlines the test strategy,test objectives,resources
(manpower, software, hardware) required for testing,test schedule,test estimation and test
deliverables
- It serves as a blueprint to conduct software testing activities as a defined process which is
minutely monitored and controlled by the test manager.
TEST PLAN SHOULD INCLUDE:
TEST OBJECTIVES/RESOURCE PLANNING/ ESTIMATIONS / TEST SCHEDULE/TEST
DELIVERIES/TEST STRATEGY.
A) TEST OBJECTIVES
-the overall goal and achievement of the test execution/ensure that the software under
test has been tested before release/list all the software features which may need to
test/define the target or the goal of the test based on above features

B) RESOURCE PLANNING
- A detailed summary of all types of resources required to complete project task/ resource
could bu human,equipement and materials needed to complete a project

C) ESTIMATIONS
- Usually done in man-days/help have an overview of the testing timeline/keep in mind
resources,time and human skills

D) TEST SCHEDULE
- After estimation ,we should create the schedule to complete the tasks/by creating a solid
schedule in the Test Planning,Test Manager, can use it as tool for monitoring

E) TEST DELIVERABLES
- A list of all documents ,tools and other components that has to be developed and
maintained in support of the testing effort
- BEFORE: test plan doc/test cases doc
- DURING: TEST CASES EXECUTIONS/TEST DATA/TEST TRACEABILITY MATRIX
- AFTER: TEST RESULTES/REPORTS/DEFECT REPORT
-