|
• Sanity testing or smoke testing – The sanity testing
is the usually performed during the initiation of the
testing activities to determine if the new version of
the application is credible enough to be put to actual
testing process or not. For example, if a newly
developed system is not working correctly when it is
started, or crashes within the first 5 minutes of its
usage, the rest of the testing is put to hold before the
crashing can be cured.
• Regression testing – Regression testing is the testing that is performed after once the testing has been completed and reported bugs and errors have been removed. Usually it is difficult to propose how much amount of re testing is required for a specific project, especially at the time of project completion or a little earlier than that. Regression testing demands the use of automated testing tools. • Acceptance testing – Acceptance testing is based on the requirements and specifications of the end user, or sometimes depends on the use by customers and/or end users over an extended but limited period of time. • Load testing – Usually these tests are undertaken to identify how much load can be handled by the application. This testing may incorporate activities like using a website under a defined range of loads to view the server response to the increased activity. • Stress testing – Stress testing is a term that is often used in place of performance testing and load testing. It is also used to explain the tests that identify how applications will behave when under heavy amount of loads, heavy database access, heavy repetition of input and output putting up high and complex queries to a database system. • Performance testing – Performance testing is usually used as a replacement term for stress testing and load testing. Mostly, performance testing and any other testing is defined in the QA plans and documents as well as the test plans devised by the testing staff. • Usability testing – Usability testing, as the name specifies, performs the testing for ‘how much user friendly an application is’. Now this is a subjective term and different users will perceive different aspects of an application to consider it more user friendly. However, for the testing team has to evaluate how user friendly the application is to the user who is the customer of the system. Several techniques like interviews, surveys, video recording sessions, conference calls and other ways can be used. However, the testing for usability is not appropriately done by the programmers and testers since they can not provide a user friendliness overview of the application. |
| Sponsored Links: |
| << back next >> |