-
Notifications
You must be signed in to change notification settings - Fork 16
Summary of Test Configuration Options
Mark Abrams edited this page Jul 27, 2023
·
7 revisions
The testConfiguration.json file is used to configure the test setup and execution. This is a summary of all of the available configuration attributes:
| Setting name | Optional? | Permitted values | Description |
|---|---|---|---|
| localSettingsFilename | Yes | Valid filename | Name of the setting file to be used, if different from the default of local.settings.json. |
| azurite.enableAzuritePortCheck | Yes |
true false
|
true if the framework is to check that Azurite is running and listening on the required ports, otherwise false. Default is true. |
| azurite.blobServicePort | Yes | 0 -> 65535 | Port number of the Azurite Blob service, if different from the default port 10000. |
| azurite.queueServicePort | Yes | 0 -> 65535 | Port number of the Azurite Queue service, if different from the default port 10001. |
| azurite.tableServicePort | Yes | 0 -> 65535 | Port number of the Azurite Table service, if different from the default port 10002. |
| logging.writeFunctionRuntineStartupLogs | Yes |
true false
|
true if the start-up logs are to be included in the test execution logs, otherwise false. Default is false. |
| logging.writeMockRequestMatchingLogs | Yes |
true false
|
true if the request matching evaluation for the fluent API is to be included in the test execution logs, otherwise false. Default is false. |
| runner.maxWorkflowExecutionDuration | Yes | 0 -> 65535 | Maximum execution time (in seconds) for a workflow. Default is 300 seconds, or 5 minutes. |
| workflow.externalApiUrlsToMock | Yes | List of host names | List of host names that are to be replaced in the settings file with the URL of the mock HTTP server. |
| workflow.builtInConnectorsToMock | Yes | List of valid connector names | List of built-in connector names where actions using these connectors are to be replaced with HTTP actions pointing at the mock HTTP server. |
| workflow.autoConfigureWithStatelessRunHistory | Yes |
true false
|
true if the testing framework automatically sets the Workflows.<workflow name>.OperationOptions setting to WithStatelessRunHistory for stateless workflows, otherwise false. Default is true. |
- 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