- 
                Notifications
    You must be signed in to change notification settings 
- Fork 16
Summary of Test Configuration Options
        MarkAbrams edited this page Jan 22, 2024 
        ·
        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 options:
| Setting name | Permitted values | Default value | Description | 
|---|---|---|---|
| localSettingsFilename | Valid filename | local.settings.json | Name of the setting file to be used, if different from the default name. | 
| azurite.enableAzuritePortCheck | truefalse | true | trueif the framework is to check that Azurite is running and listening on the required ports, otherwisefalse. | 
| azurite.blobServicePort | 0 -> 65535 | 10000 | Port number of the Azurite Blob service, if different from the default port. | 
| azurite.queueServicePort | 0 -> 65535 | 10001 | Port number of the Azurite Queue service, if different from the default port . | 
| azurite.tableServicePort | 0 -> 65535 | 10002 | Port number of the Azurite Table service, if different from the default port. | 
| logging.writeFunctionRuntimeStartupLogs | truefalse | false | trueif the start-up logs are to be included in the test execution logs, otherwisefalse. | 
| logging.writeMockRequestMatchingLogs | truefalse | false | trueif the request matching evaluation for the fluent API is to be included in the test execution logs, otherwisefalse. | 
| runner.maxWorkflowExecutionDuration | 0 -> 65535 | 300 seconds (5 mins) | Maximum execution time (in seconds) for a workflow. | 
| runner.defaultHttpResponseStatusCode | Any valid numeric HTTP status code | 200 (OK) | The HTTP status code for the default mock response, used when no mock Request Matchers are matched and when the mock response delegate function is not set, or returns null. | 
| workflow.externalApiUrlsToMock | None | [ ] | List of host names that are to be replaced in the settings file with the URL of the mock HTTP server. | 
| workflow.builtInConnectorsToMock | 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 | truefalse | true | trueif the testing framework automatically sets theWorkflows.<workflow name>.OperationOptionssetting toWithStatelessRunHistoryfor stateless workflows, otherwisefalse. | 
| workflow.removeHttpRetryConfiguration | truefalse | true | trueif the retry policy in HTTP actions is to be replaced with anonepolicy, otherwisefalse. | 
| workflow.removeHttpChunkingConfiguration | truefalse | true | trueif the chunking configuration in HTTP actions is to be removed, otherwisefalse. | 
| workflow.removeManagedApiConnectionRetryConfiguration | truefalse | true | trueif the retry policy in actions using managed API connections is to be replaced with anonepolicy, otherwisefalse. | 
- 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