Testing Oracle applications needs to be intensive. After the business requirements have been defined, the test scenarios and test plans may be developed for the four testing methodologies. The testing methods should be used in sequential order and should be utilized initially during implementation and later during patch or upgrade testing. The four testing methodologies are: unit, system, integrated, and Conference Room Pilot.

Unit testing tests the individual transactions within the application. For example, " Can I enter a supplier?" may be one unit test scenario. "Can I enter an invoice?" may be another.

System testing tests the transactions from cradle-to-grave within the application. System testing involves testing the entire business process within the application. For example, "Can I enter a supplier, enter a supplier invoice, and create a disbursement to the supplier?" maybe one system test scenario.

Integrated testing tests the transactions from cradle-to-grave, including all interfaces and customization for all applications. Testing the entire business process within all the applications is called integrated testing. "Can I load the supplier data from an interface, enter a supplier invoice, create a disbursement to the supplier, and post the journals in Oracle General Ledger?" may be one integrated test scenario.

Conference Room Pilot (CRP) testing tests the transactions from cradle-to-grave, including all interfaces and customization for all applications for an entire business period. Testing the entire business process as a monthly cycle is considered CRP testing. "Can I enter an entire month's worth of typical transactions for all Oracle applications?" may be the high-level CRP test scenario. The CRP testing should be signed off by the users and the steering committee. The CRP test plans should be saved for patch and upgrade testing. In addition, the test plans may also serve as the foundation for user training materials and user procedure documentation. As the use of Oracle applications change during the lifetime of the software, remember to incorporate the new features into the test plans.