Report on Software Testing and Quality Change Management Strategies

This report provides a comprehensive overview of software testing and quality change management. It begins with an introduction to the importance of software quality and the role of testing in achieving it. The report then delves into the theory of software testing, covering aspects like test teams, failure analysis, and the software development lifecycle. It explores the roles of both static and dynamic testing, emphasizing the importance of validation and verification. The core of the report outlines testing objectives, activities, and stages, including unit testing, integration testing, and user acceptance testing. The report concludes by referencing key literature in the field, providing a solid foundation for understanding software testing principles and practices. This report is a valuable resource for students seeking to understand software quality assurance and the process of testing throughout the software development lifecycle.

Software Quality Change Management
Presented by: HEMANTH VELAMATI (43918)

Contents
• Introduction
• Theory of software testing
• Role of testing
• Validation and verification
• Testing objectives
• Testing activities
• Testing Stages
• References

Introduction
 In this new era of technology, the application software those
will be used to meet organization’s objectives, must provide
quality outcomes.
 Whether a specific software is running accurately or not is
checked through software testing
 Software quality assurance is referred to as set of activities used
to ensure the quality of a specific software
 Three different stages of software testing are unit testing,
integrated testing and user acceptance testing

Theory of software testing
Software testing is a process set used to check software bugs or
problems in the line of codes of agenda which can be performed
through manual or automation testing.
The software testing theory includes different problem definition
in terms of test team, testing failure, participation, manual
testing, uncertain principles and selection of inaccurate test case.
In order to execute any software successfully throughout the
software development life cycle different stages are needed to be
followed in terms of initiation, planning, development, testing
and monitoring and closure.

Role of testing
Static testing: The process static analysis is conducted
after examining the software models, source codes,
design documents and requirement documents as well.
The static testing process involves review of codes,
algorithm analysis, inspection of codes etc.
Dynamic testing: In this analysis phase exact software
code is executed. The developer also observes the
performance and behavioral properties of the source
code or program

Validation and verification

Testing Objectives
 To reduce the numbers of risks or
chances of failure occurrences and
the cost for testing
 To satisfy the customers, bring
commercial profit and competitive
advantages as well
 To improve user experiences ,
brand images and company
reputation as well

Testing activities
• For testing a software product or application
accurately some testing activities are needed to be
performed successfully. Initially, the objective that
has to be tested is identified.
• At first the input is selected and then actual
outcomes are observed based on program
environment. Then the final result is analyzed
based on test verdict.
•

Testing Stages
• Unit testing: In this phase individual software
components are tested. The aim of the unit is to make
sure that all the software units are designed accurately.
• Integrated testing: After integrating all the software
units, in this phase the combined software components
are tested again. If any changes are required then those
can again incorporated to the system as per user
requirement.
• User acceptance testing: Before final delivery of the
software the internal clients are needed to test the
software.

References
 A., Lawanna,. The theory of software testing. AU Journal of Technology, 16(1)., 2012.
 V. Garousi, and M.V., Mäntylä,. A systematic literature review of literature reviews in software
testing. Information and Software Technology, 80, pp.195-216., 2016
 M.V., Mäntylä, B., Adams, F., Khomh, E. Engström, and K., Petersen,. On rapid releases and
software testing: a case study and a semi-systematic literature review. Empirical Software
Engineering, 20(5), pp.1384-1425., 2015.
 A.K., Chakraborty, P., Chatterjee, P. Chakraborty, and A., Chanda,. Optimum Testing Time of
Software using Size-Biased Concepts. arXiv preprint arXiv:1908.00307., 2019.
 Q., Luo, A., Nair, M. Grechanik, and D., Poshyvanyk,. Forepost: Finding performance problems
automatically with feedback-directed learning software testing. Empirical Software
Engineering, 22(1), pp.6-56., 2017.
 V. Garousi, and M., Felderer,. Worlds apart: industrial and academic focus areas in software
testing. IEEE Software, 34(5), pp.38-45., 2017.