Scribd
Upload
2 views15 pages

Manual Testing -Day 8th STLC Model

The document outlines the Software Testing Life Cycle (STLC), detailing the phases of system analysis, test planning, and execution, along with the importance of requirement traceability matrices. It emphasizes the need for test cases to be thoroughly documented, reviewed, and stored in a test management tool to ensure effective testing. Additionally, it discusses the significance of using appropriate test data and techniques for creating it to enhance testing effectiveness.

Uploaded by

rapakareehanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
2 views15 pages

Manual Testing -Day 8th STLC Model

The document outlines the Software Testing Life Cycle (STLC), detailing the phases of system analysis, test planning, and execution, along with the importance of requirement traceability matrices. It emphasizes the need for test cases to be thoroughly documented, reviewed, and stored in a test management tool to ensure effective testing. Additionally, it discusses the significance of using appropriate test data and techniques for creating it to enhance testing effectiveness.

Uploaded by

rapakareehanth
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 15

Manual Testing

- HemanthKumar C
Software Testing Life Cycle ( STLC )
System Analysis / Requirement Analysis

Activities:

Customer give the requirements in form of CRS. BA will convert CRS to →SRS & BA will Explain complete
requirement to entire team, it means BA will explain how each & every features works & also BA will explain
customers business workflow to entire team, every Developers & TE will try to understand the complete
requirement, if they get any doubts/questions/clarifications then they will communicate to BA & get the doubts
clarified. This complete process of understanding is called as System Analysis.

Deliverables :
• List of testable requirements .
Test Planning

What?
• Test Plan is a Document, which derives all the feature Testing Activates. Where in Test lead will
contribute 60%, Test Manager will contribute 20% also he will “approve the TP” & Test Engineers
will contribute 20%.
Requirement Traceability Matrix / Cross
Traceability Matrix

Definition ( what ) : Traceability Matrix is a document which ensure that each & every
requirement has got at least 1 Testcase’s
Senior TE / Test Manager some times TE can prepare Traceability Matrix.
Note : If TC is not present we have to write the status as unmapped and once we update then we
need to change the status as Mapped.
Types of Traceability Matrix’s
There are 3 types of Traceability Matrix’s
1.) Forward Traceability Matrix or Horizontal Traceability Matrix :
❖ Here we map requirement to the testcase & ensure that each & every requirement is having
at least 1 testcase.
❖ This is done before Testcase Execution.
❖ Here we ensure that we are building "Product right”. Requirement Testcase Name/ Id Status
1 TC 1 mapped
2.) Reverse/Backward/vertical RTM 2 TC 2 mapped
3 Unmapped
Here we map Testcases to the requirement and ensure that 4 TC 4 mapped
product is developed according to original requirement.
Reverse TM is prepared after Testcase execution.
Here, we ensure that are we building “Right Product”.
3.) Bi-Direction Traceability Matrix Advantage of Traceability Matrix
❖ It is a combination of Forward & reverse Traceability Matrix.
▪ We can ensure that each & every
Sl MODULE HIGHLEVEL DETAILED TESTCASE AUTOMATION EXECUTION
requirement has got at least 1 test
No. NAME REQURIEMT NAME/ID SCRIPTNAME TYPE cases.
1 Login Login Page 1) Usn test field
should be
Gmail_logi
n_FT01
Automation
Script_01
Automation
Testing
• We will also get to know, which
2)
present.
Psw Text field
testcases needs to be tested manually
should be
present.
or automation.
3) Login & cancel
button should
be present.
• Suddenly ,If customer changes the
2 Compose Compose page To text filed should Gmail_logi NA Manual requirement, we will get to know which
be present. n_FT02

Cc , BCC & Body,


Testing manual testcases exactly needs to be
Send and Cancel
button should be
changed or which automation scripts
present needs modification.
• We can make sure that Testcase
coverage is good.
Test Execution Test Closure / Project Closure

The process of Testing the software / build by


executing the Testcases is called as Test Execution. Activities:
• Documents do’s and don'ts
Activities:
• Quantitative analysis of application quality
• Verify test environment readiness
and testing process
• Selection of test cases
• Running of test cases
Deliverables:
• Recording of actual result
• Test summary report
• Record defects
• Test metrics

Deliverables:
• Test logs
• Defect reports
Defect Tracking

Definition : Deviation form the


customer requirement is know
as defect.
Test Scenario

What is Test Scenarios?


Test Scenarios is a high-level document of customer business workflow according to the
requirement
What is Test CASE?
It is a step by step procedure to test a feature which gives all the possible scenarios for
one particular requirement.
Testcase will be very brief & detailed. Consisting of all the navigation steps.
Testcase consist of Header, Body & Footer.
Test Case
• Specifies “how” to test the particular functionality
• Describes steps to be performed with input data and output expectations based on the user requirements
• Test cases are used while test execution to check the actual behaviour of the application.
How to document a Test case ??
Every test case should contain the following details :
• Test case ID
• Test case objective
• Pre-requisite / Pre-Condition
• Steps and data
• Expected result
• Actual result
• Status
Sr.No Test case ID Objective Pre- Test steps Test Expected Actual status
requisite data result result (pass/fail)

1 TC_001 To check the 1. Click on


process of ‘Register 'link
registration 2. Enter all the
for a new mandatory
user when fields in
all registration
mandatory form with
fields are correct data
specified 3. Click on
‘submit’
Test Case Review

Why review test cases??


• Test cases are the most important deliverable of test design phase and if needed, are shared with customers.
• To check correctness and completeness of documented test cases
Test case storage
• Test cases should be maintained in the Test management tool or in centralized controlled location
• Tools- jira, testrail, mantishub

Test management tool is an effective way of storing test cases.


Following are some of the features of test management tool with reference to the test case storage feature :
• Allows creating and modifying test cases
• Security- Access allowed only to authorised users. For example, Testing team
• Allows version control
• Allows quick searching of test cases
• Ability to map test cases to requirements
• Allows selecting a set of test cases to form test suite for test execution .
Test data

• Data used as an input to the application while testing .


• Effectiveness of the test case depends on the use of correct test data while testing .

Test Data Creation Technique


• The test data selection depends on the requirements .
• For any test condition, the number of possible data inputs can be very high based on the requirements.
It is not possible to check the test cases with all data values.
• Techniques used to achieve this are Equivalence class partitioning and Boundary value analysis
Thank you!!!

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy