Summary of Test Configuration Options

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.writeFunctionRuntimeStartupLogs	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.
runner.defaultHttpResponseStatusCode	Yes	Any valid numeric HTTP status code	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. Default is 200 (OK).
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.
workflow.removeHttpRetryConfiguration	Yes	true false	true if the retry policy in HTTP actions is to be replaced with a none policy, otherwise false. Default is true.
workflow.removeHttpChunkingConfiguration	Yes	true false	true if the chunking configuration in HTTP actions is to be removed, otherwise false. Default is true.
workflow.removeManagedApiConnectionRetryConfiguration	Yes	true false	true if the retry policy in actions using managed API connections is to be replaced with a none policy, otherwise false. Default is true.