Software testing levels Principles of testing QC-QA

1.

Software testing levels
Principles of testing
QC-QA

2.

Software Testing Levels

3.

Unit Testing
Unit (Component, Module) Testing: This is done primarily by developers to
make sure their code works fine and meets the specifications of users. They
check a piece of code (classes, functions, interfaces, procedures).

4.

Integration testing
This test two or more components to test the interaction between
components, the interaction of different parts of the system.

5.

System testing
System (or end- to- end) - it is the test of the entire system
from start to finish.

6.

Acceptance testing
Acceptance testing is performed at end-users or customer to test 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.

7.

Principles of testing
Principle 1. Testing shows presence of defects
Testing found that 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.

8.

Principles of testing
Principle 2. Exhaustive testing is impossible
Test total (all 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.

9.

Principles of testing
Principle 3. Early testing.
Testing begins as soon as possible and focuses on defining goals.

10.

Principles of testing
Principle 4. Defect clustering
Efforts testing focused proportionally to the 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.

11.

Principles of testing
Principle 5. Pesticide parade
If repeated tests, one set of test cases will not find new defects. Avoid
"pesticide paradox" can be regular checking, updating and posting new
tests.

12.

Principles of testing
Principle 6. Testing is context dependent
Testing different depending on the context of the product. For example,
critical software is tested differently than the protection of commercial site.

13.

Principles of testing
Principle 7. Absence - of - errors fallacy
Finding and fixing defects does not help if the system is useless and does
not meet the needs and expectations of the user.

14.

Quality Assurance/ Quality Control
QA
QC
What is it?
Quality assurance in the
software development
process (development
process)
Providing quality software
products (products)
Objective
Improving the development
and testing processes
Identify defects
Lifetime
During software
development
After phase encoding
software
Activities
Definition and
implementation of process
Certifications
Trainings
Perform testing

15.

Quality Assurance/ Quality Control