Software Quality Testing
Types, Activities
Jagreeti Gautam
??
what we discussed last Saturday ?
Revision
Testing in Day to Day life
Importance of Software Testing
Career Aspect in Software Quality Testing
What is Software Quality Testing
Software Quality Testing Types
Who should test
Software Quality Testing Lifecycle
Agenda
Software Quality Testing Activities
Software Quality Testing Types
Software Quality Testing Lifecycle
Software Quality Activities
Software Quality Testing Activities
Quality Assurance
activities that ensure the implementation of processes,
procedures and standards
Quality Control
activities that ensure the verification of a developed
software with respect to documented requirements
Difference in QA and QC
Quality Assurance Quality Control
Focuses on processes Focuses on actual
and procedures testing with an aim to
identify bug/defect
Product-oriented
Process-oriented
activities
activities
It is a Corrective
It is Preventive process.
process.
Proactive Activity
Reactive Activity
Difference in QA and QC
Quality Assurance Quality Control
It is a subset of considered as the subset
Software Test Life of Quality Assurance
Cycle (STLC)
Eg: Manual Testing,
Eg: Audit, Inspections, Automation testing,
reviews, Walkthrough, Integration testing,
formal meeting, System testing, Load
Planning, Overview testing.
preperation, Rework,
follow ups
Software Quality Testing Types
Manual Testing
Automation Testing
Manual Testing
Manual testing includes testing a software manually.
In this type, the tester takes over the role of an end-user and
tests the software to identify any unexpected behavior or bug
Testers use test plans, test cases, or test scenarios to test a
software to ensure the completeness of testing.
Manual testing also includes exploratory testing, as testers
explore the software to identify errors in it.
Automation Testing
Automation testing is when the tester writes scripts
and uses another software to test the product/software
This process involves automation of a manual process
Automation Testing is used to re-run the test scenarios
that were performed manually, quickly, and repeatedly.
Test Automation should be used
Wherever Possible ?
Yes, it is true that Test Automation reduces the testing time,
but it is not possible to start test automation at any time
during software development.
Test automaton should be started when the software has been
manually tested and is stable to some extent.
Moreover, test automation can never be used if requirements
keep changing.
What to Automate
Large and critical projects
Projects that require testing the same areas frequently
Requirements not changing frequently
Accessing the application for load and performance
with many virtual users
Stable software with respect to manual testing
Availability of time
Software Test Automation Tools
Selenium
Quick Test Professional
IBM Rational Functional Tester
SilkTest
WinRunner
LaodRunner
Apache Jmeter
Loadui
Software Testing Lifecycle
Project Initiation Summary Reports
System Study
Analysis
Test Plan
Regression Test
Design Test Cases Report Defects
Execute Test Cases
( manual /automated )
STLC : Project Initiation and Study
Project Initiation
Project is formally handed over to the Test Manager
High Level Test plan and High Level Estimation
defined
System Study
Analyze the Project requirement document, Business
document and QA format plan
Estimate the Test Cycles required
Define area of Functional and Non Functional testing
STLC : Design and Execution
Design
Define Test Scenarios
Develop Test Cases
Requirement Coverage Report
Execution
Test Data Creation for manual or/and Automation test
Executing Test Cases
Validation of the functions
STLC : Test Plan
Create Test Plan
Decide the Test Cycles required for the project and
regression testing
Levels of Testing agreed with stakeholders
Test Strategy
Estimate Resources
Define Matrices and Timelines
Develop Test case format
STLC : Defect Report & Regression
Report Defect
IF the Actual result of test case does not match the
Expected result report the defect.
Make sure they are fixed and retest to verify.
.
Regression test
When a defect is fixed test the system to verify that the
fixing has not impacted other areas of the software
STLC : Analysis & Summary
Analysis
Defect tracking metrics
Analyze complexity of open defects and design
metrics, update estimates for future test cases and test
plans and update accordingly
Summary Report
Prepare final Defect Report and associated metrics,
identify strategies to prevent similar problems in future
project
Thank U!!
Contact
avidiasolutions @gmail.com
jagreetigautam@sistec.ac.in
