SOFTWARE

QUALITY
ASSURANCE AND
TESTING
Abdul Muqeet
Mashood ur Rehman Rana
Muhammad Zuwaib
WHAT IS SOFTWARE
QUALITY ASSURANCE?

Software Quality Assurance Plan

(SOAP) consists of those procedures,
techniques and tools used to ensure
that a product meets the requirements
specified in the software
requirements specification.
CUSTOMER WANTS

Basically customer don't buy product, they buy assurances that

their expectations with the product would met. Customer is in
absolute position to judge the quality. Only
assurances(Quality) can also be sold.
RESPONSIBILITIES OF
TESTING TEAM

 Analyze requirements and prepare a query list. If

requirements are incomplete, they need to ask meaningful
questions that will yield more information and help
perform testing effectively.
 Write and execute test cases to find system bugs like UI
and usability issues, etc.
 Check consistency across devices, browsers, and operating
systems
 Provide inputs on high-level test scenarios, challenges,
risks, resources, test estimates, etc., during test planning
meetings.
 In some cases, Teams can also cover test automation tasks.
TOOLS FOR SOFTWARE
QUALITY ASSURANCE
 Quality management tools (Micro Focus Quality Center,
TestDirector, Test Manager, TestLink, SpiraTest, TestRail,
HP-ALM (QC)) to organize and manage all phases of the
software testing process including planning, running tests,
and tracking defects, generating and storing test reports,
and interlinking them with the release requirements;
 Defect tracking tools (BugZilla, Mantis, IBM Rational
ClearQuest) to track the defects found in the application
and generate bug reports to communicate them to the dev
team;
 MS Excel or Test Studio to write large sets of test cases
and later import them into TMTs;
TOOLS FOR SOFTWARE
QUALITY ASSURANCE

 Project management software (Jim, Redmine, YouTrack,

and Backlog);
 SQL clients to connect to the database;
 API testing tools (Postman, SoapUl, Katalon) for automated
checks. They offer predefined snippets to automate API
testing without the need to write code to test the API;
 IDEs for writing code (VSCode, Visual Studio, IntelliJ
IDEA);
SOFTWARE
TESTING TEAM
 Software Testing Team

1 Test Manager

2 Test Leader

3 Testers
TEST MANAGER

 Prepares test strategy

 Prepare the test budget
 Define test levels and test cycles
 Develop strategy for estimating test effort
 Develop strategy for test documentation, metrics and
reporting
TEST LEADER

 Prepare the test plan at each test level based on test

strategy
 Define the objectives, test items, approaches, risk,
contingencies in testing process
 Assign roles and provide schedule to testers
 Identify the test specifications test activities for testers
 Gather metrics and track the testing progress
TESTERS
 Gather the test requirements
 Review the project documents to understand the
requirements and identify the errors
 Assist the test lead to prepare the test plan
 Create the test documents like traceability matrix, test data
and test cases
 Set up and verify the test environment
TESTING TEAM SKILLS

 Deep understanding of software testing, its main concepts,

and processes: the whole bug life cycle; different testing
levels, methods, and types; test estimation techniques.
 Ability to work in an Agile environment.
 Critical thinking and analytical skills to examine bug
reports and prioritize necessary tests, what information to
include in the daily status reports, prioritize and estimate
task execution.
TESTING TEAM SKILLS
 Good communication and teamwork skills to interact with
project team members, clients, and stakeholders as well as
work closely with the dev team - from reproducing the
reported issue and emphasizing the fix for critical bugs to
understanding how the bug has been fixed;
 Programming skills are always a plus including coding,
basic SQL knowledge to extract data for tests, XML,
general web development skills, and web services.
HOW SOFTWARE
QUALITY ASSURANCE
WORKS?

 Using some Planned and systematic

method that evaluate the quality of slw
products, standards, process &
procedures.

 Ensure that development follow

Standards and Procedures Done by

• Continuous Monitoring

• Product Evaluation

• Conducting Audits
SQA ACTIVITIES

 Product Evaluation & Process Monitoring

• Ensures development processes and the control processes
written in the management plan are carried out effectively
• Ensure that all the procedures and standards are correctly
followed
• Products are continuously monitored for checking that it is
following the standards and processes.
SQA ACTIVITIES
 Product Evaluation
• Assures standards are being followed
• Ensures that the software application product is developed by
conforming all the applicable standards as illustrated in the
Management Plan

 Product Monitoring
• Ensures that the appropriate steps are carried out during the
development process
• Comparing the actual steps carried out with those in the
documented procedures
• Ensures that the Management Plan specifies the methods that
should be used by the monitoring activity.
SQA ACTIVITIES
 Product Audits
• That looks the entire product and all the processes in depth
• Done by comparing them with the established standards and
procedures
• Its an important activity to review the management plan,
technical processes and assurance processes to provide the
actual status of the software application product
• Main idea behind this is control procedures are properly
followed and desired documentation is properly maintained

 SQA Product
• Is nothing but an audit report to display findings and
recommendations to obey standards and procedures
WHAT S/W REVIEW IS USED
FOR?
 "Filter" for software process
 Servers to uncover errors and defects that can then be
removed
 "Purify" s/w including
• Requirements
• Design models
• Code Testing data

 Primary objective is to find errors during the process so

that do not become defects after release of the s/w
THANK YOU
Abdul Muqeet

Mashood ur Rehman Rana

Muhammad Zuwaib