-
Notifications
You must be signed in to change notification settings - Fork 14
Example Mock Requests and Responses
The testing framework will replace Call a Local Function and Invoke Workflow actions, and actions using built-in service provider connectors, with a HTTP action that is configured to call a mock HTTP server that is managed by the testing framework. This allows the action to run independently of any external dependency.
The following sections show examples of the requests that are generated by the replacement HTTP action so that you can understand how to assert the contents of the requests that are created and sent to the mock HTTP server. There are also examples of the responses that you can create in the test for various success and failure scenarios.
-
Built-In Connectors:
- Service Bus
- SMTP
- Storage Account
- SQL Server
Replacing an action with a HTTP action does not change the behaviour of the workflow.
- Home
- Using the Testing Framework
- Test Configuration
- Azurite
- Local Settings File
- Test Execution Logs
- Stateless Workflows
- Handling Workflow Dependencies
- Fluent API
- Automated testing using a DevOps pipeline
- Summary of Test Configuration Options
-
Example Mock Requests and Responses
- Call a Local Function action
- Invoke Workflow action
- Built-In Connectors:
- Service Bus
- SMTP
- Storage Account
- SQL Server