Testing Methods Part-2

February 20th, 2010 by

Testing methods:

  1. Black box testing: Black box testing methods include: equivalence partitioning , boundary value analysis , all-pairs testing, fuzz testing, model based testing, traceability matrix, exploratory testing  and specification-based test.
  1. White box testing: White is when the tester has access to the internal data structures and algorithms including the code that implement these.

Testing Levels:

Unit Testing

Unit testing refers to tests that verify the functionality of a specific section of code, Unit testing is also called Component Testing.

Integration Testing: Integration testing is any type of software testing that seeks to verify the interfaces between components against a software design. Software components may be integrated in an iterative way or all together (“big bang”). Normally the former is considered a better practice since it allows interface issues to be localised more quickly and fixed.

System Testing System testing tests a completely integrated system to verify that it meets its requirements.

Regression Testing Regression testing focuses on finding defects after a major code change has occurred. Such regressions occur whenever software functionality that was previously working correctly stops working as intended. Common methods of regression testing include re-running previously run tests and checking whether previously fixed faults have re-emerged.

Acceptance testing Acceptance testing can mean one of two things:

  1. A smoke test is used as an acceptance test prior to introducing a new build to the main testing process, i.e. before integration and regression .
  2. Acceptance testing performed by the customer, often in their lab environment on their own HW, is known as user acceptance testing (UAT). Acceptance testing may be performed as part of the hand-off process between any two phases of development.

Alpha testing Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers’ site.

Beta testing Beta testing comes after alpha testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has few faults or bugs.