Saturday 8 November 2014

  1. Acceptance Testing
  2. This test is conducted to determine that the software system complies with the customer’s requirements and is ready to be delivered to them. Every feature is checked from the user’s perspective by the testing team and the feature is marked accepted or rejected. The results of these tests are very subjective in nature and it takes a while to figure out the exact issue in the code.
  3. Installation Testing
  4. This type of Quality Assurance testing ensures that the installed system on the target environment i.e. customer’s hardware is working properly. Along with the verification of installation procedure, it is used for system testing in accordance with the hardware configuration requirements.
  5. Alpha-Beta Testing
  6. Alpha Testing is a form of internal acceptance test, in which simulated or actual  operational testing is done at the developer’s site. The tested software is then released to a limited number of audience who are not in the developing team, to ensure that the software has zero number of bugs. This type of external acceptance test is called Beta Testing
  7. Functional Testing
  8. Also known as Conformance Testing or Correctness Testing, this test is used to validate whether a particular function is as per the specifications or not. The recorded results answer “can the user do this” or “does this particular feature work.”
  9. Regression Testing
  10. Generally, regression in a software occurs as a result of program changes, when an existing code collides with the new one. In this scenario, Regression Testing is done by retesting of selective units or system, to check whether the previously tested software is still functioning properly or not.
  11. Performance Testing
  12. This type of testing is used to substantiate that the software system or sub-system meets the stated performance requirements like response time and capacity. It also investigates and measures other attributes like reliability, scalability and resource usage.
  13. Stress Testing
  14. Also known as Torture Testing, it exercises intense examination of the software which are beyond normal operational capacity and design load. This testing is used to determine breaking points and modes of failure, and to test the stability of the software outside its comfort zone.
  15. Usability Testing
  16. This technique is used to assess if the user interface is easy to learn and use by the customer. It is concerned with the use of software, user documentation, how it functions and recovers from the user errors.
  17. Security Testing
  18. This test is required to look for any loopholes in the security mechanism of the software system for complete protection and functionality of data. It includes elements of integrity, confidentiality, availability,  non-repudiation, authorization and authentication.

0 comments :

Post a Comment