-
Notifications
You must be signed in to change notification settings - Fork 13
Service Bus Send Message action
MarkAbrams edited this page Feb 5, 2024
·
1 revision
This is an example of JSON request message content for a mocked Service Bus Send Message action.
The name of the topic or queue is located in the entityName
field. The content of the Service Bus message is located in the message.contentData
field.
{
"entityName": "customer-topic",
"message": {
"contentData": {
"id": 12345,
"title": "Mr",
"firstName": "Peter",
"lastName": "Smith",
"dateOfBirth": "1970-04-25",
"language": {
"code": "en-GB",
"name": "English (United Kingdom)"
}
},
"contentType": "application/json",
"sessionId": "12345",
"userProperties": {
"entityId": 12345,
"entityType": "customer"
},
"messageId": "ff421d65-5be6-4084-b748-af490100c9a5",
"label": "customer-12345"
}
}
The test case should respond with a HTTP 200 (OK) status code. The action does not generate any response content.
- 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