Testing Methods and Testing Types

1. Unit Testing

  • Unit Testing is primarily carried out by the developers themselves
  • Deals functional correctness and the completeness of individual program units
  • White box testing methods are employed

2. Integration Testing
  • Integration Testing: Deals with testing when several program units are integrated
  • Regression testing: Change of behavior due to modification or addition is called ‘Regression’. Used to bring changes from worst to least
  • Incremental Integration Testing: Checks out for bugs which encounter when a module has been integrated to the existing
  • Smoke Testing: It is the battery of test which checks the basic functionality of program. If fails then the program is not sent for further testing

3. System Testing

  • System Testing : Deals with testing the whole program system for its intended purpose
  • Recovery testing: System is forced to fail and is checked out how well the system recovers the failure
  • Security Testing: Checks the capability of system to defend itself from hostile attack on programs and data
  • Load & Stress Testing: The system is tested for max load and extreme stress points are figured out
  • Performance Testing: Used to determine the processing speed
  • Installation Testing: Installation & un-installation is checked out in the target platform

4. Acceptance Testing

  • UAT: ensures that the project satisfies the customer requirements
  • Alpha Testing : It is the test done by the client at the developer’s site
  • Beta Testing : This is the test done by the end-users at the client’s site
  • Long Term Testing : Checks out for faults occurrence in a long term usage of the product
  • Compatibility Testing : Determines how well the product is substantial to product transition


Testing Methods :
1. White Box

White box testing is also called ‘Structural Testing / Glass Box Testing’ is used for testing the code keeping the system specs in mind. Inner working is considered and thus Developers Test.
  • Mutation Testing- Number of mutants of the same program created with minor changes and none of their result should coincide with that of the result of the original program given same test case.
  • Basic Path Testing- Testing is done based on Flow graph notation, uses Cyclops metric complexity & Graph matrices.
  • Control Structure Testing- The Flow of control execution path is considered for testing. It does also checks :-
Conditional Testing : Branch Testing, Domain Testing
Data Flow Testing

Loop testing: Simple, Nested, Conditional, Unstructured Loops
    2. Gray Box
    Similar to Black box but the test cases, risk assessments, and test methods involved in gray box testing are developed based on the knowledge of the internal data and flow structures

    3. Black Box

    Also called ‘Functional Testing’ as it concentrates on testing of the functionality rather than the internal details of code.
    Test cases are designed based on the task descriptions
    • Comparison Testing-Test cases results are compared with the results of the test Oracle.
    • Graph Based Testing-Cause and effect graphs are generated and cyclometric complexity considered in using the test cases.
    • Boundary Value Testing-Boundary values of the Equivalence classes are considered and tested as they generally fail in Equivalence class testing.
    • Equivalence class Testing-Test inputs are classified into Equivalence classes such that one input check validates all the input values in that class.

    Load Testing Vs. Performance Testing


    Load Testing is:


    - Similar to, but not synonymous with performance testing

    - About how many requests you can process in an amount of time.
    - Concerned with the volume of traffic your website (or application) can handle or verifies capacity for users.
    - Not intended to break the system
    - Viewing the system from the user perspective
    - Associated with black box testing

    Performance Testing is:


    - A super-set of load testing

    - How fast a single request is processed
    - Concerned with speed and efficiency of various components of the web application
    - Useful with only one user and/or one transaction
    - Viewing the system from the architecture perspective (behind the server side curtain)
    - Associated with white box testing

    Simple Definitions:


    Performance Testing = how fast is the system?
    Load Testing = how much volume can the system process?


    Thanks & Regards ,


    Prashant Vadher | QA Engineer


    0 Comments:

    Post a Comment

     
    Design by Prashant Vadher