Types of Testing
Compliance Testing
Involves test cases designed to verify that an application meets specific criteria, such as processing four-digit year dates, properly handling special data boundaries and other business requirements.
Intersystem Testing / Interface Testing
Integration testing where the interfaces between system components are tested
Integration testing where the interfaces between system components are tested
The intersystem testing is designed to check and verify the interconnection between application
function correctly
function correctly
Applications are frequently interconnected to other systems. The interconnection may be data coming into the system from another application, leaving for another application frequently in multiple cycles
The intersystem testing involves the operations of multiple systems in test. The basic need of intersystem test arises whenever there is a change in parameters between application systems, where multiple systems are integrated in cycles.
Parallel Testing
The process of comparing test results of processing production data concurrently in both the old and new systems.
The process of comparing test results of processing production data concurrently in both the old and new systems.
- Process in which both the old and new modules run at the same time so that performance and outcomes can be compared and corrected prior to deployment; commonly done with modules like Payroll.
- Testing a new or an alternate data processing system with the same source data that is used in another system. The other system is considered as the standard of comparison.
Database Testing
The database component is a critical piece of any data-enabled application. Today’s intricate mix of client-server and Web-enabled database applications is extremely difficult to Test productively. Testing at the data access layer is the point at which your application communicates with the database. Tests at this level are vital to improve not only your overall Test strategy, but also your product’s quality.
The database component is a critical piece of any data-enabled application. Today’s intricate mix of client-server and Web-enabled database applications is extremely difficult to Test productively. Testing at the data access layer is the point at which your application communicates with the database. Tests at this level are vital to improve not only your overall Test strategy, but also your product’s quality.
Database testing includes the process of validation of database stored procedures, database triggers; database APIs, backup, recovery, security and database conversion.
Manual support Testing
Manual support testing involves all functions performed by the people in preparing data for and using data from automated system. The objective of manual support testing is
Manual support testing involves all functions performed by the people in preparing data for and using data from automated system. The objective of manual support testing is
- Verify the manual – support procedures are documented and complete
- Determine the manual-support responsibilities has been assigned
- Determine manual support people are adequately trained.
Manual support testing involves first the evaluation of the adequacy of the process and seconds the execution of the process. The method of testing may be testing is same but the objective remains the same.
Ad-hoc Testing
Testing carried out using no recognised test case design technique.
Testing carried out using no recognised test case design technique.
Testing without a formal test plan or outside of a test plan. With some projects this type of testing is carried out as an adjunct to formal testing. If carried out by a skilled tester, it can often find problems that are not caught in regular testing. Sometimes, if testing occurs very late in the development cycle, this will be the only kind of testing that can be performed. Sometimes ad hoc testing is referred to as exploratory testing.
Configuration Testing
Testing to determine how well the product works with a broad range of hardware/peripheral equipment configurations as well as on different operating systems and software.
Testing to determine how well the product works with a broad range of hardware/peripheral equipment configurations as well as on different operating systems and software.
Pilot Testing
Testing that involves the users just before actual release to ensure that users become familiar with the release contents and ultimately accept it. Often is considered a Move-to-Production activity for ERP releases or a beta test for commercial products. Typically involves many users, is conducted over a short period of time and is tightly controlled.
Testing that involves the users just before actual release to ensure that users become familiar with the release contents and ultimately accept it. Often is considered a Move-to-Production activity for ERP releases or a beta test for commercial products. Typically involves many users, is conducted over a short period of time and is tightly controlled.
Automated Testing
Software testing that utilizes a variety of tools to automate the testing process and when the importance of having a person manually testing is diminished. Automated testing still requires a skilled quality assurance professional with knowledge of the automation tool and the software being tested to set up the tests.
Software testing that utilizes a variety of tools to automate the testing process and when the importance of having a person manually testing is diminished. Automated testing still requires a skilled quality assurance professional with knowledge of the automation tool and the software being tested to set up the tests.
Load Testing
Load Testing involves stress testing applications under real-world conditions to predict system behavior and performance and to identify and isolate problems. Load testing applications can emulate the workload of hundreds or even thousands of users, so that you can predict how an application will work under different user loads and determine the maximum number of concurrent users accessing the site at the same time.
Load Testing involves stress testing applications under real-world conditions to predict system behavior and performance and to identify and isolate problems. Load testing applications can emulate the workload of hundreds or even thousands of users, so that you can predict how an application will work under different user loads and determine the maximum number of concurrent users accessing the site at the same time.
Stress and Volume Testing
Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements.
Stress Testing: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements.
Volume Testing:
Testing where the system is subjected to large volumes of data. Testing with the intent of determining how well a product performs when a load is placed on the system resources that nears and then exceeds capacity.
Volume Testing, as its name implies, is testing that purposely subjects a system (both hardware and software) to a series of tests where the volume of data being processed is the subject of the test. Such systems can be transactions processing systems capturing real time sales or could be database updates and or data retrieval.
Usability Testing
Testing the ease with which users can learn and use a product.
Testing the ease with which users can learn and use a product.
All aspects of user interfaces are tested:
- Display screens
- messages
- report formats
- navigation and selection problems
Environmental Testing
These tests check the system’s ability to perform at the installation site. Requirements might include tolerance for
These tests check the system’s ability to perform at the installation site. Requirements might include tolerance for
- heat
- humidity
- chemical presence
- portability
- electrical or magnetic fields
- Disruption of power, etc.
