![]() |
VOOZH | about |
dotnet add package Futile.SpecFlow.Actions.Configuration --version 0.1.350.9
NuGet\Install-Package Futile.SpecFlow.Actions.Configuration -Version 0.1.350.9
<PackageReference Include="Futile.SpecFlow.Actions.Configuration" Version="0.1.350.9" />
<PackageVersion Include="Futile.SpecFlow.Actions.Configuration" Version="0.1.350.9" />Directory.Packages.props
<PackageReference Include="Futile.SpecFlow.Actions.Configuration" />Project file
paket add Futile.SpecFlow.Actions.Configuration --version 0.1.350.9
#r "nuget: Futile.SpecFlow.Actions.Configuration, 0.1.350.9"
#:package Futile.SpecFlow.Actions.Configuration@0.1.350.9
#addin nuget:?package=Futile.SpecFlow.Actions.Configuration&version=0.1.350.9Install as a Cake Addin
#tool nuget:?package=Futile.SpecFlow.Actions.Configuration&version=0.1.350.9Install as a Cake Tool
This SpecFlow.Action is used to read configuration values out of the specflow.actions.json file. You can also provide configurations for multiple targets, to run your scenarios with different configurations.
This SpecFlow.Action is used by every SpecFlow.Action that has a configuration.
Work on Specflow has been discontinued and the successor is reqnroll . This nuget package comes from a fork that:
net481 and net8.0Updated examples can be found here (Selenium and Playwright support multiple targets): Futile.SpecFlow-Examples.
specflow.actions.jsonspecflow.actions.%TARGET_NAME%.json files.You can configure this plugin via the specflow.actions.json.
Example:
{
"your_configuration": "value of the property"
}
This plugin supports tagreting of multiple configurations at runtime. For each configuration you provide, a class will be generated in your feature's code behind file when you build the project. This means that for any given test, the test will be executed against each target.
Example:
specflow.actions.json
{
"your_configuration": "value of the property",
"another_configuration": "another value"
}
specflow.actions.TARGET_1.json
{
"your_configuration": "TARGET 1 overrides this value"
}
specflow.actions.TARGET_2.json
{
"your_configuration": "TARGET 2 overrides this value"
}
[Binding]
public class A_Binding_Class
{
private readonly ISpecFlowActionsConfiguration _specFlowActionsConfiguration;
public A_Binding_Class(ISpecFlowActionsConfiguration specFlowActionsConfiguration)
{
_specFlowActionsConfiguration = specFlowActionsConfiguration;
}
public string GetConfigurationValue()
{
return _specFlowActionsConfiguration.Get("your_configuration", string.Empty);
}
}
With this configuration, you are getting every scenario twice in your test explorer.
The result of the GetConfigurationValue is the following:
| Target Name | your_configuration | another_configuration |
|---|---|---|
| Target_1 | TARGET 1 overrides this value | another value |
| Target_2 | TARGET 2 overrides this value | another value |
Get your configuration value as string. Throws an error if the configuration value doesn't exist.
Get your configuration value as string. If configuration value can't be found, the defaultValue is returned
Get your configuration value as double.
Get your configuration value as a string[]. This is used to get a list from your configuration json file.
Get the child elements of a node in your configuration json file.
Add the latest version of the SpecFlow.Actions.Configuration NuGet Package to your project.
Latest version:👁 Nuget
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net8.0 net8.0 is compatible. net8.0-android net8.0-android was computed. net8.0-browser net8.0-browser was computed. net8.0-ios net8.0-ios was computed. net8.0-maccatalyst net8.0-maccatalyst was computed. net8.0-macos net8.0-macos was computed. net8.0-tvos net8.0-tvos was computed. net8.0-windows net8.0-windows was computed. net9.0 net9.0 was computed. net9.0-android net9.0-android was computed. net9.0-browser net9.0-browser was computed. net9.0-ios net9.0-ios was computed. net9.0-maccatalyst net9.0-maccatalyst was computed. net9.0-macos net9.0-macos was computed. net9.0-tvos net9.0-tvos was computed. net9.0-windows net9.0-windows was computed. net10.0 net10.0 was computed. net10.0-android net10.0-android was computed. net10.0-browser net10.0-browser was computed. net10.0-ios net10.0-ios was computed. net10.0-maccatalyst net10.0-maccatalyst was computed. net10.0-macos net10.0-macos was computed. net10.0-tvos net10.0-tvos was computed. net10.0-windows net10.0-windows was computed. |
| .NET Framework | net481 net481 is compatible. |
Showing the top 5 NuGet packages that depend on Futile.SpecFlow.Actions.Configuration:
| Package | Downloads |
|---|---|
|
Futile.SpecFlow.Actions.WindowsAppDriver
Fork of SpecFlow.Actions.WindowsAppDriver |
|
|
Futile.SpecFlow.Actions.Appium
Fork of SpecFlow.Actions.Appium |
|
|
Futile.SpecFlow.Actions.Playwright
Fork of SpecFlow.Actions.Playwright |
|
|
Futile.SpecFlow.Actions.Selenium
Fork of SpecFlow.Actions.Selenium |
|
|
Futile.Specflow.Actions.FlaUI
SpecFlow plugin for FlaUI |
This package is not used by any popular GitHub repositories.