ISTQB – Foundation 2.3 – Test Types

Classification of testing

  1. Static Testing – non executable – work products test/Review- to find – omissions- missing info-loop holes are the flaws in the document – work product can be any doc in process to create the dynamic application- main purpose is to find defects in the very early stage so avoid defects in the dynamic testing stage.
    Informal- walkthrough- Technical Review- Inspection
  2. Dynamic Testing – Executable -Applications under test- validate by running the application
    Functional levels of testing
    1. Unit testing – done mostly by the developers (manual-automation)
    2. Integration Testing
    3. System testing
    4. Acceptance Testing
  3. Static testing- Reviews- Verification
  4. Dynamic testing – diff levels of testing – Validation
  5. Difference between Functional vs Non functional
    Functional – With out core features- application is not conceded as complete- user cannot work on the application – basically its what the system does- to meet the requirement
    Non-Functional – how the system works?
    Quality characteristics- enhance compatibility, portability, reliance, etc, any other than the 4 functional levels are non functional
    Ex: recovery, security, failover – to validate quality attribute.
    Unless client says we will have non functional- so functional testing is non-mandatory.

White BOX

Done by developer by executing the application
Also called as (See through- the code structure etc)
Structure Box,
Glass Box,
Open Box,
Clear Box
Transparent Box

Black BOX

Done by the tester with out knowlege of code and structure ont eh UI created for the customer use!

Also called as (could not see thru)
Skin Box,
Closed Box,
Opaque Box

Change related testing
Adding some maintenance testing with the regular process of the testing
In few companies- they rerun the test as after the fix that us called confirmation testing – to make sure the defect has been resolved- also known as re-testing.

Regression testing is followed after the Re-testing, to make sure the fix does not impact he existing ote modules which are working fine earlier, and not impacted but the new fix added
Regression- is the best candidate for Automation
Also conducted additional when we have environment changes-migration one plat form to other- or new functionality included like updates/upgrades.