|
Introduction |
|
SE Concepts |
|
Performance Testing |
|
What tester does in the organization |
|
Functional Testing |
|
Testing Processes and Role of the test engineer in the company. |
|
Processes and Plans. |
|
Configuration Management. |
|
Mercury Tools QTP, Winrunner |
|
Testing Strategy |
|
Drivers, Stubbs |
|
Basis Path Testing |
|
Software Matrix |
|
Configuration Management |
|
Release Management |
|
Test Harness |
|
QTP |
|
Standards |
|
CMM level and KPA |
|
Software testing is an investigation conducted to provide information about the quality of the product, with respect to the context in which it is intended to operate. Software Testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks at implementation of the software. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs.
Software Testing can also be stated as the process of validating and verifying that a software program/application/product:
- Meets the business and technical requirements that guided its design and development;
- Works as expected; and
- Can be implemented with the same characteristics.
Software Testing , depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the Software Development methodology adopted |
|
|
