1.
VALUE
OF
- TRANSPOSE SOLUTIONS
www.transposesolutions.com
1/17/2018

2.
www.transposesolutions.com
Introduction
Software Testing adds organizational value in quantitative and
qualitative ways.
Software Testing can save time and money by eliminating the defects
at a early stage that can cause rework and delay in delivery timelines.
Improved customer satisfaction helps to build goodwill and more
customers.

3.
www.transposesolutions.com
Benefits and Cost of Software Testing
The benefits of software testing can vary based on the industry and the organization.
It is important to have a structure and process which includes appropriate documentation
and feedback mechanisms.
Benefits are not necessarily be on monetary aspect, reduced risk of defects can help you
avoid claims, hassle and rework.
Cost comes in the form of structure (Test Team & Tools for Testing) and setting up a
process (Level of Testing, Testing Types, Methods and Techniques).

4.
www.transposesolutions.com
Goals and Objectives
Successful organizations recognize the importance of quality. Establishing a quality-oriented
mindset is the responsibility of business leadership.
Some organizations have both testing teams and quality assurance teams, while other organizations
rely on their test teams to serve both roles.
In such scenarios, quality assurance activities are integrated into the entire software process and
lifecycle. This involves key practices such as reviews, verification and validation, process
standardization and software process maturity.
Organization need to foster a culture of quality, then, through rigorous process, team responsibility,
and objective metrics.

5.
www.transposesolutions.com
Keys aspects of Testing Team:
Organizational structures vary widely, many organizations adopt different
structures on a project by project basis. Common characteristics of a
testing team:
Open Communication
Good Documentation
Strong Technical Skills
Domain Knowledge
Best Practices

6.
www.transposesolutions.com
Roles and Responsibilities:
The roles and responsibilities can vary based on the organization and the project, here is
the template for standard test team structure:
 Project Manager – Project Management oversees all technical, quality, cost and
schedule aspects of efforts and performance.
 Test Manager - Providing test approach and test plan documentation for a given
project.
 Test Analyst – Gathers information's needed to support key metrics, identify and
defining required tests, monitor, evaluate test coverage and overall quality of
testing.
 Tester - Review and contribute to test plans, as well as analyzing, reviewing and
assessing requirements and design specifications.

7.
www.transposesolutions.com
Usage of Tools:
Integrating tools across the organization is an important process of
testing.
Example:
A defect tracking tool may be used by the test team for tracking defects,
by the development team for tracking their implementation tasks and by
the business analyst for tracking requirements.

8.
www.transposesolutions.com
When to start testing:
It is recommended that testing be performed at every stage of the SDLC
(Requirement Gathering, Analysis, Design, Development, Operation and
Maintenance).
Example:
With agile teams, the testers are a part of the integrated development
team (often including analysts and users/customers).

9.
www.transposesolutions.com
Levels of Testing:
Life cycle model (Waterfall, V-model, Iterative and Agile) determines the
moment of involvement, level of involvement.
There are 5 levels of testing, each of which carries a specific functional
purpose:
Test Planning
Unit Testing
Integration Testing
Systems Testing
Acceptance Testing (Alpha/Beta)

10.
www.transposesolutions.com
Types of Testing:
Test type is focused on a particular test objective, which could
be any of the following:
Functional Testing
Non Functional Testing
Structural Testing
Regression Testing
Maintenance Testing

11.
www.transposesolutions.com
Testing Techniques:
Different approaches are considered to test the software based on the
life cycle model of the project:
Static Technique
Test Design Technique
Specification or Black Box Testing
Structure-based or White Box Testing

12.
www.transposesolutions.com
Test Strategies:
Test strategies can vary based on the industry and the project. Mixing
strategies is the best approach to a project in order to maximize the
benefits of the various strategies while minimizing the risks.
Most common test strategies widely followed :
Requirements-based testing
Risk-based testing

13.
www.transposesolutions.com
When to Stop Testing?
Goal is to ensure that software meets the requirements including, functional,
performance, reliability, security and usability.
Test closure criteria could be:
 Reporting of all test activities
 Closing incident reports or raising change records for any that remain open.
 Documenting acceptance of the system.
 Archiving test results, test environment and test infrastructure for later use.
 Recommendations.

14.
www.transposesolutions.com
Conclusion:
The results of the testing should be gathered and presented
to stakeholders to address that the team was able to achieve
the quality goals, objective and recorded the accurate
information which can help to build respect and value for the
organization.

15.
www.transposesolutions.com
Code of ethics
It is important to engage Certified Testers and Professional
Organization who shall maintain integrity and the highest professional
standard.
A code of ethics is necessary to ensure that the confidential and
privileged information is not put to appropriate use.

16.
www.transposesolutions.com
Thank you..