Software testing levels Principles of testing QC-QA презентация

to make sure their code works fine and meets the specifications of users. They check a piece of code (classes, functions, interfaces, procedures).

between components, the interaction of different parts of the system.

of the entire system from start to finish.

the software.

Acceptance testing can be performed as part of the process between any two phases of development.

Alpha testing, Beta testing

Alpha testing is done on the side of developers. This is done at the end of the development process.

Beta testing, beta testing is carried out on the customer side. This is done just before the launch of the product.

defects are present, but can not assure that there are no defects. Testing reduces the number of probable unfound defects and if defects are found, this does not guarantee their absence.

combinations introductions and preconditions) is not feasible except for trivial cases. Instead efforts, test all available risk analysis and priorities to help conduct targeted testing.

and focuses on defining goals.

expected and the resulting defect density on the modules. Several modules usually contain most of the defects found during doreliznoho testing-related or primarily with imperfections operating systems.

of test cases will not find new defects. Avoid "pesticide paradox" can be regular checking, updating and posting new tests.

the context of the product. For example, critical software is tested differently than the protection of commercial site.

fixing defects does not help if the system is useless and does not meet the needs and expectations of the user.