D2 of 30 Days' ISTQB: Test levels

Image result
There are four Test levels according to the above V Model in software life circle:

1, Component testing, also known as unit, module and program testing, searches for defects in, and veriries the functioning of software(e.g. modules, programs, objects,classes,etc.)that are separately testable.

2, Integration testing tests interfaces between components, interactions to different parts of a system such as operating system, file system and hardware or interfaces between system. Integration testing is often carried out by the integrator, but preferably by a specific integration tester or test team.

3, System testing is concerned with the behavior of the whole system/product as defined by the scope of a development project or product.
System testing is most often the final test on behalf of development to verify that the system to be delivered meets the specification and its purpose may be to find as many defects as possible. Most often it is carried out by specialist testers that form a dedicated, and sometimes independent, test team within development, reporting to the development manager or project manager.
System testing should investigate both functional and non-functional requirements of the system. Typical non-functional tests include performance and reliability.

4, Acceptance testing. When the development organization has performed its system test and has corrected all or most defects, the system will be delivered to the user or customer for acceptance testing.
The acceptance test should answer questions such as:
Can the system be releases?
What, if any, are the outstanding(business) risks?
Has development met their obligations?
Acceptance test is most often the responsibility of the user or customer, although other stakeholders may be involved as well.
The goal of acceptance testing is to establish confidence in the system, part of the system or specific non-functional characteristics, e.g.usability, of the system.
Acceptance testing is most often focused on a validation type of testing, whereby we are trying to determine if the system is fit for purpose. Finding defects should not be the main focus in acceptance testing.

0 comments:

Post a Comment