Software development project: will just one testing type suffice? (Buitech - QATestLab)

1
Liudmyla Potyomkina QATestLab Program Manager
Software development project will just one
testing type suffice?
Wyn H Devonald Global Operations Director
Founder at Buitech
2
The necessity of software testing is now beyond
all questions, but what testing types to apply
for in order to meet quality standards? The
number and choice of testing types depend on
several parameters that can be divided into
internal and external ones.
3
EXTERNAL PARAMETERS include target market and
location, customer and end users needs and
expectations, project budget, project deadline,
level and type of risks. On the basis of
external parameters, several internal ones can be
specified.
4
INTERNAL PARAMETERS include software type,
software requirements / project documentation,
development model, available development
resources, test objectives, QA team skills, and
available testing infrastructure.
5
By specifying the most critical aspects of your
software product, you will be able to single out
relevant testing types and prioritize them to
ensure the improvement of software quality and
optimization of the project budget.
6
To ensure a correct realization of the
requirements for system architecture and
functional logic, they should be outlined and
represented in a form of project specification.
7
A software development model determines what
testing techniques will be more suitable in order
to ensure the optimization of workflow for both
developers and testers. Planning of work stages
and distribution of processes help to reduce time
and costs.
8
Based on software requirements and the customers
expectations, you are able to specify
test objectives and get a clear vision of the
scope of testing activities to be performed.
Besides, the identified test objectives help to
select appropriate QA strategies and techniques.
9
The choice of testing type depends on the
competence and experience of your QA team and
available testing infrastructure including
devices, tools, and frameworks.
10
Being a stumbling block for software quality,
the project budget should always include testing
budget to avoid additional expenses on the
post-release fixing of detected bugs.
11
The analysis of potential risks at the QA stage
helps to prevent difficulties and to smooth the
processes. Risks may be connected with the lack
of required testing equipment, QA team size, and
test engineers competence.
12
By selecting a proper number and type of testing
on the basis of end users / customers
expectations, software specifics, project budget,
and deadline, you provide the end users with a
top-quality software product.
13
Thank you