specFlow
This configuration section contains settings related to synchronizing SpecFlow projects. These settings are only required for old SpecFlow versions and for synchronizing automated test cases.
The following example shows the available options within this section.
Settings
specFlowGeneratorFolder
The path of the SpecFlow generator folder used by the project, that is usually the tools
folder of the SpecFlow NuGet package, e.g. packages\\SpecFlow.2.3.0\\tools
.
detect generator of the project
generateFeatureFileCodeBehinds
Specifies whether SpecSync should attempt to regenerate feature file code-behind files after they have been changed by SpecSync. This is only required for SpecFlow v2.
SpecSync automatically decides whether generation is necessary
scenarioOutlineAutomationWr appers
Specifies how automation wrapper methods should be generated for synchronizing scenario outlines to automated test cases. Available options: useTestCaseData
and iterateThroughExamples
. (Default: iterateThroughExamples
)
useTestCaseData
-- the generated wrapper method loads the test data for the iterations from the test case. Running the test cases through this wrapper in Azure DevOps generates a detailed report about each iteration, but it cannot be executed locally and also does not work in from Azure DevOps pipeline build. See related section of the Synchronizing automated test cases article for details.iterateThroughExamples
-- the generated wrapper method iterates through the examples and runs the test for each. A failure of an iteration does not block the remaining iterations. Running the test cases through this wrapper in Azure DevOps generates a single entry in the report, but the details of the entry contain all executed data set.
iterateThroughExam ples
wrapperMethodPrefix
The method prefix to be used for the generated automation wrapper methods.
_SpecSyncWrapper_
wrapperMethodCategory
The test category (trait) be added for the generated automation wrapper methods.
SpecSyncWrapper
Last updated