Functional Testing: (Iteration Testing) Testing the application against
business requirements by testing a slice of functionality of the whole system
ensuring that the software has all the required functionality that’s specified.
System Testing: Testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements, functional testing is also included in this phase.
Regression Testing: Software testing that seeks to uncover bugs in existing functional and non-functional areas after changes have been made to the system.
User Acceptance Testing: This is not System Testing, but rather ensures that the solution will work for the user. Testing is normally done by a subject-matter expert and is one of the final stages of a project often before a client or customer accepts the changes to the system.
Performance Testing: Testing performed to determine how the system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.
Beta Testing: Testing of a rerelease of a software product conducted by customers
Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well.
Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.
System Testing: Testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements, functional testing is also included in this phase.
Regression Testing: Software testing that seeks to uncover bugs in existing functional and non-functional areas after changes have been made to the system.
User Acceptance Testing: This is not System Testing, but rather ensures that the solution will work for the user. Testing is normally done by a subject-matter expert and is one of the final stages of a project often before a client or customer accepts the changes to the system.
Performance Testing: Testing performed to determine how the system performs in terms of responsiveness and stability under a particular workload. It can also serve to investigate, measure, validate or verify other quality attributes of the system, such as scalability, reliability and resource usage.
Beta Testing: Testing of a rerelease of a software product conducted by customers
Ad Hoc Testing: A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well.
Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.
