Testing is context dependent, but, at a high level, there are common sets of test activities without which
testing is less likely to achieve test objectives. These sets of test activities form a test process. The test
process can be tailored to a given situation based on various factors. Which test activities are included in
this test process, how they are implemented, and when they occur is normally decided as part of the test
planning for the specific situation (see section 5.1).

1.1.What is Testing?
Software systems are an integral part of our daily life. Most people have had experience with software
that did not work as expected. Software that does not work correctly can lead to many problems,
including loss of money, time or business reputation, and, in extreme cases, even injury or death.

Testing, as a form of quality control, helps in achieving the agreed upon goals within the set scope, time,
quality, and budget constraints. Testing’s contribution to success should not be restricted to the test team
activities. Any stakeholder can use their testing skills to bring the project closer to success. Testing
components, systems, and associated documentation helps to identify defects in software