Search This Blog

Wednesday, 14 September 2011

SOFTWARE TESTING INTRODUCTION



TESTING
      Testing is the process of executing a program or system with the intent of finding errors.

PRINCIPLES OF TESTING
1.      The goal of testing is to find defects bofore customers find them out.
2.      Testing applies all through the software life cycle and is not at the end of cycle.
3.      Understand the reason behind the test.
4.      Test the tests first.
5.      Testing requires talented,committed people who believe in themselves and work in teams

QUALITY
     Quality is meeting the requirements expected of the software, consistently and predictably.

QUALITY ASSURANCE
1.      Concentrates on the process of producing the products.
2.      Defect prevention oriented.
3.      Usually done throughout the life cycle.
4.      Example : reviews and audits.

QUALITY CONTROL
1.      Concentrates on specific products.
2.      Defect-detection and correction oriented.
3.      Usually done after the product is built.
4.      Example: Software testing at various levels.

VERIFICATION
     Verification is the process of evaluating a system or component to determine whether the products of a given phase satisfy the conditions imposed at the start of that phase.

VALIDATION
     Validation is the process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements

LEVELS OF TESTING
1.      Verification testing  2. Unit testing  3. Integration testing  4. System testing  5. User acceptance testing

STATIC VERSUS DYANAMIC TESTING
     Statis testing is perfomed using the software documentation. The code is not executing during static testing. Most verification techniques are static tests.
     Dynamic testing requires the code to be in an executable state to perform the tests. Most validation tests are dynamic tests.

1 comment: