Currently, there is no agreed-upon definition of a test type. That is not unusual when techniques, levels and even test design strategy are considered as testing types. For instance, in some cases, white box testing method, boundary value analysis, integration testing are introduced as testing types.
In such a situation, we need to refer to official sources in order to avoid intricate interpretations and misunderstandings. (International Software Testing Qualifications Board – ISTQB for short) is an esteemed international organization that developed and set world-class standards for software testing.
According the definition of ISTQB, testing types are just the means to clearly define the goal of certain test level for the programme or project. A testing specialist strives to ensure that testing of the functionality of a component or an entire system is sufficient at each level to attain overall test objectives. With the focus on a specific test objective and appropriate testing type it is much easier to make and communicate decisions against testing objectives.
It is necessary to compare the four types of software testing:
- functional;
- non-functional;
- structural (white box-oriented);
- regression (change-related.
Surely, there are many subtypes of software testing. Well, to begin with, let us familiarize ourselves with functional testing.
Functional testing
Functional testing confirms that each function of the software app under test works in compliance with a requirements specification document. Functional testing demonstrates ‘what the system does’ and this is usually described in a functional specification, requirements specification or use cases. The goal is to verify the correctness of the system, i.e. to make sure that the functionality behaves as expected. It is usually accepted as a black box-testing though it is not totally true because this technique also includes non-functional testing.
There are main 5 steps of functional testing:
- preparing test input data based on the functional specification;
- creating test conditions from business-requirements that are actually inputs to functional testing;
- executing test cases;
- comparing actual outcomes with expected ones.
Testing of the functions of a system or its component can be done from 2 perspectives: business process-based and requirement-based.
There is a list of software testing companies for you to find a good specialist easily and quickly. It has been prepared for long time and all the candidates have shown themselves to good advantage. You are most likely to be happy to collaborate with any person selected from the list!
- Requirement-based testing uses the functional requirements specification as a basis for creating tests.
- Business-process-based testing relies on the knowledge of business processes.
Add Comment