The Oracle Integration Test page is specifically designed to invoke integrations that are exposed as web services. In addition to REST-based triggers, integrations that use a SOAP Adapter as a trigger can also be run directly from this page. The Test page provides a user interface to formulate the request payload (XML for SOAP) and send it to the integration's endpoint, allowing developers to test the integration's logic without needing an external client application.

A. Event pattern integrations: These are triggered by business events from external applications (e.g., Oracle Fusion Cloud Apps) and cannot be initiated from the Test page.

B. Schedule pattern integrations: These are triggered based on a predefined time schedule. While they can be submitted to run immediately, this is done via the "Submit Now" action, not the Test page.

D. File trigger connection-based integrations: These are initiated when a file is placed in a configured directory (e.g., on an FTP server), not by a direct invocation from the Test page.

1. Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration 3: In the section "Activate, Monitor, and Manage Integrations," the subsection "Test Integrations" explicitly states: "You can test integrations that are triggered by a REST Adapter or SOAP Adapter connection from the Test page. For all other types of integrations, you must invoke them from the appropriate trigger connection."

2. Oracle Cloud Infrastructure Documentation, Using Integrations in Oracle Integration Generation 2: The chapter "Manage Integrations" includes the section "Test REST Adapter and SOAP Adapter-Triggered Integrations," which details the process. It confirms that only these two trigger types are supported for testing through the designer's Test page.