diff --git a/.gitignore b/.gitignore index 4cdcbd2cc..95cf9cf04 100644 --- a/.gitignore +++ b/.gitignore @@ -46,8 +46,6 @@ _ReSharper*/ *.resharper .fake/ -#Project files -[Bb]uild/* #Subversion files .svn @@ -63,6 +61,7 @@ reports/ merged/ test/ Documentation-*/ +artifacts/ #Output/ #nCrunch files diff --git a/.nuke/build.schema.json b/.nuke/build.schema.json new file mode 100644 index 000000000..5ad8e574c --- /dev/null +++ b/.nuke/build.schema.json @@ -0,0 +1,115 @@ +{ + "$schema": "http://json-schema.org/draft-04/schema#", + "title": "Build Schema", + "$ref": "#/definitions/build", + "definitions": { + "build": { + "type": "object", + "properties": { + "Configuration": { + "type": "string", + "description": "Configuration to build - Default is 'Debug' (local) or 'Release' (server)", + "enum": [ + "Debug", + "Release" + ] + }, + "Continue": { + "type": "boolean", + "description": "Indicates to continue a previously failed build attempt" + }, + "Help": { + "type": "boolean", + "description": "Shows the help text for this build assembly" + }, + "Host": { + "type": "string", + "description": "Host for execution. Default is 'automatic'", + "enum": [ + "AppVeyor", + "AzurePipelines", + "Bamboo", + "Bitrise", + "GitHubActions", + "GitLab", + "Jenkins", + "Rider", + "SpaceAutomation", + "TeamCity", + "Terminal", + "TravisCI", + "VisualStudio", + "VSCode" + ] + }, + "NoLogo": { + "type": "boolean", + "description": "Disables displaying the NUKE logo" + }, + "Partition": { + "type": "string", + "description": "Partition to use on CI" + }, + "Plan": { + "type": "boolean", + "description": "Shows the execution plan (HTML)" + }, + "Profile": { + "type": "array", + "description": "Defines the profiles to load", + "items": { + "type": "string" + } + }, + "Root": { + "type": "string", + "description": "Root directory during build execution" + }, + "Skip": { + "type": "array", + "description": "List of targets to be skipped. Empty list skips all dependencies", + "items": { + "type": "string", + "enum": [ + "Clean", + "GenerateSampleOutput", + "Pack", + "Publish", + "PublishNuGet", + "Test" + ] + } + }, + "Solution": { + "type": "string", + "description": "Path to a solution file that is automatically loaded" + }, + "Target": { + "type": "array", + "description": "List of targets to be invoked. Default is '{default_target}'", + "items": { + "type": "string", + "enum": [ + "Clean", + "GenerateSampleOutput", + "Pack", + "Publish", + "PublishNuGet", + "Test" + ] + } + }, + "Verbosity": { + "type": "string", + "description": "Logging verbosity during build execution. Default is 'Normal'", + "enum": [ + "Minimal", + "Normal", + "Quiet", + "Verbose" + ] + } + } + } + } +} \ No newline at end of file diff --git a/.nuke/parameters.json b/.nuke/parameters.json new file mode 100644 index 000000000..4ac978499 --- /dev/null +++ b/.nuke/parameters.json @@ -0,0 +1,4 @@ +{ + "$schema": "./build.schema.json", + "Solution": "src/Pickles/Pickles.sln" +} \ No newline at end of file diff --git a/CHANGELOG.md b/CHANGELOG.md index 56411d5b0..0a50e7095 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -14,6 +14,23 @@ Features in Experimental are subject to change and removal without being conside This document is formatted according to the principles of [Keep A CHANGELOG](http://keepachangelog.com). +## [3.0.1] - 2021-10-04 + +### Updated +- .NET Core 3.1/.NET 5 Support! +- All libraries are .NET Standard 2.0 so they will work with anything from .NET Framework 4.6.1 to .NET 5. +- Dropping support for the UI project for the time being until a cross-platform solution can be created. +- Not including a Chocolatey distribution for the time being until a non-windows deployment can be created. +- MsBuild NuGet package is still being worked on. Zip file will be available with this release. +- Development can now be done on Windows, Mac or (potentially) Linux. +- [Nuke](https://nuke.build/index.html) build will simplify and speed up releases. Removed old build files. +- Multiple updates thanks to [Andrey Leskov](https://github.com/andrey-covergo)! (See PR [618](https://github.com/picklesdoc/pickles/pull/618)) + - Update tests to launch on non-windows platform + - Update cucumber json report format to match official json schema + - Add feature uri to cucumer json report [#609](https://github.com/picklesdoc/pickles/issues/609) + - Add feature and step id, hidden field to Cucumber json report + - Make Pickles.CommandLine packable as dotnet tool + ## [2.3.3] - 2021-03-11 ### Fixed diff --git a/CNAME b/CNAME deleted file mode 100644 index 632b59178..000000000 --- a/CNAME +++ /dev/null @@ -1 +0,0 @@ -www.picklesdoc.com diff --git a/CreateTestResults.ps1 b/CreateTestResults.ps1 deleted file mode 100644 index cfed67235..000000000 --- a/CreateTestResults.ps1 +++ /dev/null @@ -1,84 +0,0 @@ -Write-Host "Remember to build the solution first!" - -# NUnit2 -Start-Process -FilePath "$PSScriptRoot\test-harness\packages\NUnit.Runners.2.7.0\tools\nunit-console.exe" -ArgumentList "$PSScriptRoot\test-harness\nunit\bin\Debug\nunitHarness.dll", "/result=$PSScriptRoot\results-example-nunit.xml" -NoNewWindow -Wait - -# NUnit 2 with NUnit3 runner -Start-Process -FilePath "$PSScriptRoot\test-harness\packages\NUnit.ConsoleRunner.3.9.0\tools\nunit3-console.exe" -ArgumentList "$PSScriptRoot\test-harness\nunit\bin\Debug\nunitHarness.dll", "/result=$PSScriptRoot\results-example-nunit2-with-nunit3-runner.xml" -NoNewWindow -Wait - -# NUnit 3 -Start-Process -FilePath "$PSScriptRoot\test-harness\packages\NUnit.ConsoleRunner.3.9.0\tools\nunit3-console.exe" -ArgumentList "$PSScriptRoot\test-harness\nunit3\bin\Debug\nunit3Harness.dll", "/result=$PSScriptRoot\results-example-nunit3.xml" -NoNewWindow -Wait - -# SpecRun -Start-Process -FilePath "$PSScriptRoot\test-harness\packages\SpecRun.Runner.1.2.0\tools\specrun.exe" -ArgumentList "run default.srprofile", "/baseFolder:$PSScriptRoot\test-harness\SpecRun\bin\Debug", "/log:specrun.log", "/report:$PSScriptRoot\results-example-specrun.html" -NoNewWindow -Wait - -# XUnit 1 -Start-Process -FilePath "$PSScriptRoot\test-harness\packagesNonNuget\xunit.runner\xunit.console.clr4.exe" -ArgumentList "$PSScriptRoot\test-harness\xunit\bin\Debug\xunitHarness.dll", "/xml $PSScriptRoot\results-example-xunit.xml" -NoNewWindow -Wait - -# XUnit 2 -Start-Process -FilePath "$PSScriptRoot\test-harness\packages\xunit.runner.console.2.4.0\tools\net452\xunit.console.exe" -ArgumentList "$PSScriptRoot\test-harness\xunit2\bin\Debug\xunit2Harness.dll", "-xml $PSScriptRoot\results-example-xunit2.xml", "-parallel none" -NoNewWindow -Wait - -# MSTest -$MSTest = Get-ChildItem -Path "${env:ProgramFiles(x86)}\Microsoft Visual Studio\2017" -Recurse | Where-Object { $_.Name -eq "MSTest.exe" } | Select-Object -First 1 -$MsTestResultFilePath = "$PSScriptRoot\results-example-mstest.trx" -if (Test-Path $MsTestResultFilePath) { - Remove-Item $MsTestResultFilePath -} - -Start-Process -FilePath $MSTest.FullName -ArgumentList "/testcontainer:$PSScriptRoot\test-harness\mstest\bin\Debug\mstestHarness.dll", "/resultsfile:$MsTestResultFilePath", "/testsettings:$PSScriptRoot\test-harness\TestSettings.testsettings" -NoNewWindow -Wait - -# Cucumber -Set-Location -Path "$PSScriptRoot\test-harness\Cucumber" -& "cucumber" --format json_pretty --out "$PSScriptRoot\results-example-json.json" --tags ~@ignore -Set-Location $PSScriptRoot - -# CucumberJS -Set-Location -Path "$PSScriptRoot\test-harness\CucumberJS" -& "$PSScriptRoot\node_modules\.bin\cucumber-js" --format json:"$PSScriptRoot\results-example-cucumberjs-json.json" -Write-Host "Waiting for CucumberJS to finish. You might need to increase the sleep time as the test suite increases." -Start-Sleep -s 2 -Set-Location $PSScriptRoot - -# VSTest -## Get VSTest console runner location -$VSTest = Get-ChildItem -Path "${env:ProgramFiles(x86)}\Microsoft Visual Studio\2017" -Recurse | Where-Object { $_.Name -eq "vstest.console.exe" } | Select-Object -First 1 - -## Remove any previous .trx files -Get-ChildItem -Path "$PSScriptRoot\TestResults" | Where-Object { $_.Extension -eq ".trx" } | Remove-Item - -Start-Process -FilePath $VSTest.FullName -ArgumentList "$PSScriptRoot\test-harness\mstest\bin\Debug\mstestHarness.dll", "/logger:trx" -NoNewWindow -Wait - -## Get the .trx file -$VsTestResultFile = Get-ChildItem -Path "$PSScriptRoot\TestResults" | Where-Object {$_.Extension -eq ".trx" } | Sort-Object CreationTime -Descending | Select-Object -First 1 - -# Moving result files to corresponding unit test projects -Write-Host "Moving NUnit 2 results" -Move-Item -Path "$PSScriptRoot\results-example-nunit.xml" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\NUnit\NUnit2\" -Force - -Write-Host "Moving NUnit 2 with NUnit3 runner results" -Move-Item -Path "$PSScriptRoot\results-example-nunit2-with-nunit3-runner.xml" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\NUnit\NUnit3\" -Force - -Write-Host "Moving NUnit 3 results" -Move-Item -Path "$PSScriptRoot\results-example-nunit3.xml" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\NUnit\NUnit3\" -Force - -Write-Host "Moving XUnit 1 results" -Move-Item -Path "$PSScriptRoot\results-example-xunit.xml" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\XUnit\XUnit1\" -Force - -Write-Host "Moving XUnit 2 results" -Move-Item -Path "$PSScriptRoot\results-example-xunit2.xml" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\XUnit\XUnit2\" -Force - -Write-Host "Moving SpecRun results" -Move-Item -Path "$PSScriptRoot\results-example-specrun.html" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\SpecRun\" -Force - -Write-Host "Moving Cucumber JSON results" -Move-Item -Path "$PSScriptRoot\results-example-json.json" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\CucumberJSON\" -Force - -Write-Host "Moving MSTest results" -Move-Item -Path "$PSScriptRoot\results-example-mstest.trx" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\MsTest\" -Force - -Write-Host "Moving CucumberJS JSON results" -Write-Host "The tags do not seem to work - remember to manually remove the ignored scenarios from the result" -Move-Item -Path "$PSScriptRoot\results-example-cucumberjs-json.json" -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\CucumberJSON\" -Force - -Write-Host "Moving VSTest results" -Move-Item -Path $VsTestResultFile.FullName -Destination "$PSScriptRoot\src\Pickles\Pickles.TestFrameworks.UnitTests\VsTest\results-example-vstest.trx" -Force \ No newline at end of file diff --git a/DeployArtifacts.cmd b/DeployArtifacts.cmd deleted file mode 100644 index aae3b8997..000000000 --- a/DeployArtifacts.cmd +++ /dev/null @@ -1,4 +0,0 @@ -@ECHO OFF -call DeployOutput.cmd %1 -call DeployToChocolatey.cmd %1 -call DeployToNuget.cmd %1 diff --git a/DeployOutput.cmd b/DeployOutput.cmd deleted file mode 100644 index 1fae032c8..000000000 --- a/DeployOutput.cmd +++ /dev/null @@ -1,10 +0,0 @@ -@ECHO OFF - -cd docs -rmdir Output /s /q -echo D | xcopy ..\Output Output /e -powershell -Command "(gc index_template.html) -replace 'VERSION_PLACEHOLDER', '%1' | Out-File -encoding ASCII index.html" - -git add -A -git commit -m "Version %1" -cd .. \ No newline at end of file diff --git a/DeployToChocolatey.cmd b/DeployToChocolatey.cmd deleted file mode 100644 index 8109e932a..000000000 --- a/DeployToChocolatey.cmd +++ /dev/null @@ -1,8 +0,0 @@ -@ECHO OFF - -REM this script supposes you set the chocolatey API key by running this command: -REM choco apikey -s"https://push.chocolatey.org/" -k="" -REM Mind the trailing slash! - -.\packages\chocolatey\tools\chocolateyInstall\choco push .\deploy\chocolatey\pickles.%1.nupkg -.\packages\chocolatey\tools\chocolateyInstall\choco push .\deploy\chocolatey\picklesui.%1.nupkg diff --git a/DeployToNuget.cmd b/DeployToNuget.cmd deleted file mode 100644 index 395ffc76b..000000000 --- a/DeployToNuget.cmd +++ /dev/null @@ -1,8 +0,0 @@ -@ECHO OFF - -REM this script supposes you set the nuget API key by running this command: -REM NuGet SetApiKey -Source https://www.nuget.org/api/v2/package - -.\packages\nuget\nuget push .\deploy\nuget\Pickles.%1.nupkg -Source https://www.nuget.org/api/v2/package -.\packages\nuget\nuget push .\deploy\nuget\Pickles.CommandLine.%1.nupkg -Source https://www.nuget.org/api/v2/package -.\packages\nuget\nuget push .\deploy\nuget\Pickles.MSBuild.%1.nupkg -Source https://www.nuget.org/api/v2/package diff --git a/InstallPackages.cmd b/InstallPackages.cmd deleted file mode 100644 index 29fd13e96..000000000 --- a/InstallPackages.cmd +++ /dev/null @@ -1,10 +0,0 @@ -cd .\deploy\chocolatey -..\..\packages\nuget\nuget.exe install Pickles -Source %cd% -OutputDirectory .\packages -..\..\packages\nuget\nuget.exe install PicklesUI -Source %cd% -OutputDirectory .\packages -cd ..\.. - -cd .\deploy\nuget -..\..\packages\nuget\nuget.exe install Pickles -Source %cd% -OutputDirectory .\packages -..\..\packages\nuget\nuget.exe install Pickles.CommandLine -Source %cd% -OutputDirectory .\packages -..\..\packages\nuget\nuget.exe install Pickles.MSBuild -Source %cd% -OutputDirectory .\packages -cd ..\.. diff --git a/Output/Cucumber/cucumberResult.json b/Output/Cucumber/cucumberResult.json index 0ec000752..74bef325a 100644 --- a/Output/Cucumber/cucumberResult.json +++ b/Output/Cucumber/cucumberResult.json @@ -1,11 +1,14 @@ [ { + "id": "showing-basic-gherkin-syntax", "keyword": "Feature", "name": "Showing basic gherkin syntax", + "uri": "Features/00BasicGherkin/BasicGherkin.feature", "tags": [], "line": 1, "elements": [ { + "id": "showing-basic-gherkin-syntax;simple-gwt", "keyword": "Scenario", "name": "Simple GWT", "line": 8, @@ -16,8 +19,9 @@ "keyword": "Given", "name": "the initial state of the application is Running", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -25,8 +29,9 @@ "keyword": "When", "name": "I ask what the application state is", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -34,14 +39,16 @@ "keyword": "Then", "name": "I should see Running as the answer", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-basic-gherkin-syntax;using-and-and-but", "keyword": "Scenario", "name": "Using And and But", "line": 13, @@ -52,8 +59,9 @@ "keyword": "Given", "name": "the initial state of the application is Running", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -61,8 +69,9 @@ "keyword": "And", "name": "I have authorization to ask application state", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -70,8 +79,9 @@ "keyword": "When", "name": "I ask what the application state is", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -79,8 +89,9 @@ "keyword": "Then", "name": "I should see Running as the answer", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -88,8 +99,9 @@ "keyword": "And", "name": "I should see the time of the application", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -97,8 +109,9 @@ "keyword": "But", "name": "the state of the application should not be Stopped", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -107,12 +120,15 @@ ] }, { + "id": "the-test-runner-is-not-very-important", "keyword": "Feature", "name": "The test runner is not (very) important", + "uri": "Features/01TestRunner/TestRunnerIsNotImportant.feature", "tags": [], "line": 1, "elements": [ { + "id": "the-test-runner-is-not-very-important;a-couple-of-simple-steps", "keyword": "Scenario", "name": "A couple of simple steps", "line": 6, @@ -123,8 +139,9 @@ "keyword": "Given", "name": "I have step defintions in place", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -132,8 +149,9 @@ "keyword": "When", "name": "I call a step", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -141,8 +159,9 @@ "keyword": "Then", "name": "the step should have been called", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -151,12 +170,15 @@ ] }, { + "id": "addition", "keyword": "Feature", "name": "Addition", + "uri": "Features/02TagsAndHooks/Hooks.feature", "tags": [], "line": 1, "elements": [ { + "id": "addition;hooking-into-pre-conditions-for-test-runs-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Test Runs in SpecFlow", "line": 6, @@ -167,8 +189,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -176,14 +199,16 @@ "keyword": "Then", "name": "the BeforeTestRun hook should have been executed", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-features-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Features in SpecFlow", "line": 10, @@ -194,8 +219,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -203,14 +229,16 @@ "keyword": "Then", "name": "the BeforeFeature hook should have been executed", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-scenarios-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Scenarios in SpecFlow", "line": 14, @@ -221,8 +249,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -230,14 +259,16 @@ "keyword": "Then", "name": "the BeforeScenario hook should have been executed", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-scenarioblocks-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for ScenarioBlocks in SpecFlow", "line": 18, @@ -248,8 +279,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -257,14 +289,16 @@ "keyword": "Then", "name": "the BeforeScenarioBlock hook should have been executed", "line": 20, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-steps-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Steps in SpecFlow", "line": 22, @@ -275,8 +309,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -284,8 +319,9 @@ "keyword": "Then", "name": "the BeforeStep hook should have been executed", "line": 24, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -294,8 +330,10 @@ ] }, { + "id": "tag-demonstrator", "keyword": "Feature", "name": "Tag demonstrator", + "uri": "Features/02TagsAndHooks/TagDemo.feature", "tags": [ { "name": "@allAboutTags" @@ -307,6 +345,7 @@ "line": 1, "elements": [ { + "id": "tag-demonstrator;ignored-scenario", "keyword": "Scenario", "name": "Ignored scenario", "line": 8, @@ -321,8 +360,9 @@ "keyword": "Given", "name": "that my scenario has the @ignore tag", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -330,8 +370,9 @@ "keyword": "When", "name": "I run the scenario", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -339,8 +380,9 @@ "keyword": "Then", "name": "the scenario is ignored", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -348,14 +390,16 @@ "keyword": "And", "name": "the missing step definitions are not reported", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-without-tags", "keyword": "Scenario", "name": "A scenario without tags", "line": 14, @@ -366,8 +410,9 @@ "keyword": "Given", "name": "that my scenario has 0 tags", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -375,8 +420,9 @@ "keyword": "When", "name": "I run the scenario", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -384,14 +430,16 @@ "keyword": "Then", "name": "before scenario hook with '' is run", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-with-1-tag", "keyword": "Scenario", "name": "A scenario with 1 tag", "line": 20, @@ -406,8 +454,9 @@ "keyword": "Given", "name": "that my scenario has 1 tags", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -415,8 +464,9 @@ "keyword": "When", "name": "I run the scenario", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -424,14 +474,16 @@ "keyword": "Then", "name": "before scenario hook with 'testTag1' is run", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-with-3-tags", "keyword": "Scenario", "name": "A scenario with 3 tags", "line": 26, @@ -452,8 +504,9 @@ "keyword": "Given", "name": "that my scenario has 3 tags", "line": 27, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -461,8 +514,9 @@ "keyword": "When", "name": "I run the scenario", "line": 28, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -470,14 +524,16 @@ "keyword": "Then", "name": "before scenario hook with 'testTag1, testTag2, testTag3' is run", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-with-2-tags", "keyword": "Scenario", "name": "A scenario with 2 tags", "line": 32, @@ -495,8 +551,9 @@ "keyword": "Given", "name": "that my scenario has 2 tags", "line": 33, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -504,8 +561,9 @@ "keyword": "When", "name": "I run the scenario", "line": 34, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -513,8 +571,9 @@ "keyword": "Then", "name": "before scenario hook with 'testTag1, testTag3' is run", "line": 35, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -523,24 +582,28 @@ ] }, { + "id": "scenario-outline", "keyword": "Feature", "name": "Scenario outline", + "uri": "Features/03ScenarioOutline/ScenarioOutline.feature", "tags": [], "line": 1, "elements": [ { - "keyword": "Scenario Outline", + "id": "scenario-outline;add-two-positive-numbers-with-many-examples", + "keyword": "Scenario", "name": "Add two positive numbers with many examples", "line": 8, - "type": "scenario_outline", + "type": "scenario", "tags": [], "steps": [ { "keyword": "Given", "name": "I enter into the calculator", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -548,8 +611,9 @@ "keyword": "And", "name": "I enter into the calculator", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -557,8 +621,9 @@ "keyword": "When", "name": "I perform add", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -566,26 +631,29 @@ "keyword": "Then", "name": "the result should be ", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { - "keyword": "Scenario Outline", + "id": "scenario-outline;add-two-negative-numbers-with-many-examples", + "keyword": "Scenario", "name": "Add two negative numbers with many examples", "line": 28, - "type": "scenario_outline", + "type": "scenario", "tags": [], "steps": [ { "keyword": "Given", "name": "I enter into the calculator", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -593,8 +661,9 @@ "keyword": "And", "name": "I enter into the calculator", "line": 30, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -602,8 +671,9 @@ "keyword": "When", "name": "I perform add", "line": 31, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -611,8 +681,9 @@ "keyword": "Then", "name": "the result should be ", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -621,12 +692,15 @@ ] }, { + "id": "scenario-context-features", "keyword": "Feature", "name": "Scenario Context features", + "uri": "Features/031ScenarioContext/ScenarioContext.feature", "tags": [], "line": 1, "elements": [ { + "id": "scenario-context-features;store-and-retrive-person-marcus-from-scenariocontext", "keyword": "Scenario", "name": "Store and retrive Person Marcus from ScenarioContext", "line": 6, @@ -637,8 +711,9 @@ "keyword": "When", "name": "I store a person called Marcus in the Current ScenarioContext", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -646,14 +721,16 @@ "keyword": "Then", "name": "a person called Marcus can easily be retrieved", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;showing-information-of-the-scenario", "keyword": "Scenario", "name": "Showing information of the scenario", "line": 11, @@ -671,8 +748,9 @@ "keyword": "When", "name": "I execute any scenario", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -680,14 +758,16 @@ "keyword": "Then", "name": "the ScenarioInfo contains the following information", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;show-the-type-of-step-were-currently-on", "keyword": "Scenario", "name": "Show the type of step we're currently on", "line": 18, @@ -698,8 +778,9 @@ "keyword": "Given", "name": "I have a Given step", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -707,8 +788,9 @@ "keyword": "And", "name": "I have another Given step", "line": 20, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -716,8 +798,9 @@ "keyword": "When", "name": "I have a When step", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -725,14 +808,16 @@ "keyword": "Then", "name": "I have a Then step", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;display-error-information-in-afterscenario", "keyword": "Scenario", "name": "Display error information in AfterScenario", "line": 27, @@ -750,14 +835,16 @@ "keyword": "When", "name": "an error occurs in a step", "line": 28, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;pending-step", "keyword": "Scenario", "name": "Pending step", "line": 30, @@ -768,8 +855,9 @@ "keyword": "When", "name": "I set the ScenarioContext.Current to pending", "line": 31, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -777,8 +865,9 @@ "keyword": "Then", "name": "this step will not even be executed", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -787,8 +876,10 @@ ] }, { + "id": "featurecontext-features", "keyword": "Feature", "name": "FeatureContext features", + "uri": "Features/032FeatureContext/FeatureContextFeatures.feature", "tags": [ { "name": "@showUpInScenarioInfo" @@ -800,6 +891,7 @@ "line": 1, "elements": [ { + "id": "featurecontext-features;store-and-retrive-person-marcus-from-featurecontext-current", "keyword": "Scenario", "name": "Store and retrive Person Marcus from FeatureContext Current", "line": 7, @@ -810,8 +902,9 @@ "keyword": "When", "name": "I store a person called Marcus in the current FeatureContext", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -819,14 +912,16 @@ "keyword": "Then", "name": "a person called Marcus can easily be retrieved from the current FeatureContext", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "featurecontext-features;showing-information-of-the-feature", "keyword": "Scenario", "name": "Showing information of the feature", "line": 11, @@ -837,8 +932,9 @@ "keyword": "When", "name": "I execute any scenario in the feature", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -846,8 +942,9 @@ "keyword": "Then", "name": "the FeatureInfo contains the following information", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -856,12 +953,15 @@ ] }, { + "id": "show-the-use-of-background", "keyword": "Feature", "name": "Show the use of background", + "uri": "Features/04Background/BackgroundFeature.feature", "tags": [], "line": 1, "elements": [ { + "id": "show-the-use-of-background;add-1-to-the-sum", "keyword": "Scenario", "name": "Add 1 to the sum", "line": 10, @@ -872,8 +972,9 @@ "keyword": "When", "name": "I add 1 to the Sum-variable", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -881,14 +982,16 @@ "keyword": "Then", "name": "the total sum should be 2", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "show-the-use-of-background;add-2-to-the-sum", "keyword": "Scenario", "name": "Add 2 to the sum", "line": 14, @@ -899,8 +1002,9 @@ "keyword": "When", "name": "I add 2 to the Sum-variable", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -908,8 +1012,9 @@ "keyword": "Then", "name": "the total sum should be 3", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -918,12 +1023,15 @@ ] }, { + "id": "showing-table-usage", "keyword": "Feature", "name": "Showing table usage", + "uri": "Features/05TablesAndAssist/TableScenario.feature", "tags": [], "line": 1, "elements": [ { + "id": "showing-table-usage;using-tables", "keyword": "Scenario", "name": "Using tables", "line": 6, @@ -934,8 +1042,9 @@ "keyword": "Given", "name": "I have the following persons", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -943,8 +1052,9 @@ "keyword": "When", "name": "I search for Jocke", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -952,14 +1062,16 @@ "keyword": "Then", "name": "the following person should be returned", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-table-usage;using-tables-with-specflow-assist", "keyword": "Scenario", "name": "Using tables with SpecFlow Assist", "line": 17, @@ -970,8 +1082,9 @@ "keyword": "Given", "name": "I have the following persons using assist", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -979,8 +1092,9 @@ "keyword": "When", "name": "I search for Jocke", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -988,14 +1102,16 @@ "keyword": "Then", "name": "the following person should be returned using assist", "line": 24, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-table-usage;creating-a-entity-from-field-value", "keyword": "Scenario", "name": "Creating a entity from field value", "line": 28, @@ -1006,8 +1122,9 @@ "keyword": "When", "name": "I fill out the form like this", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1015,14 +1132,16 @@ "keyword": "Then", "name": "the following person should be returned using assist", "line": 35, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-table-usage;example-of-a-wide-table", "keyword": "Scenario", "name": "Example of a wide table", "line": 39, @@ -1033,8 +1152,9 @@ "keyword": "Given", "name": "this wide table", "line": 40, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1043,12 +1163,15 @@ ] }, { + "id": "show-the-compare-to-feature", "keyword": "Feature", "name": "Show the compare to feature", + "uri": "Features/06CompareToAssist/CompareTo.feature", "tags": [], "line": 1, "elements": [ { + "id": "show-the-compare-to-feature;comparetoinstance", "keyword": "Scenario", "name": "CompareToInstance", "line": 8, @@ -1059,8 +1182,9 @@ "keyword": "Given", "name": "I have the following person", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1068,8 +1192,9 @@ "keyword": "Then", "name": "CompareToInstance should match this guy", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1077,8 +1202,9 @@ "keyword": "And", "name": "CompareToInstance should match this guy", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1086,14 +1212,16 @@ "keyword": "But", "name": "CompareToInstance should not match this guy", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "show-the-compare-to-feature;comparetoset", "keyword": "Scenario", "name": "CompareToSet", "line": 31, @@ -1104,8 +1232,9 @@ "keyword": "Given", "name": "I have the following persons using assist", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1113,8 +1242,9 @@ "keyword": "Then", "name": "CompareToSet should match this", "line": 37, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1122,8 +1252,9 @@ "keyword": "But", "name": "CompareToSet should not match this", "line": 42, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1132,12 +1263,15 @@ ] }, { + "id": "svenska---summering", "keyword": "Feature", "name": "Svenska - Summering", + "uri": "Features/07Localization/Svenska.feature", "tags": [], "line": 1, "elements": [ { + "id": "svenska---summering;summera-5-och-7-ska-vara-12", "keyword": "Scenario", "name": "Summera 5 och 7 ska vara 12", "line": 9, @@ -1148,8 +1282,9 @@ "keyword": "Given", "name": "att jag har knappat in 5", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1157,8 +1292,9 @@ "keyword": "And", "name": "att jag har knappat in 7", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1166,8 +1302,9 @@ "keyword": "When", "name": "jag summerar", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1175,8 +1312,9 @@ "keyword": "Then", "name": "ska resultatet vara 12", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1185,12 +1323,15 @@ ] }, { + "id": "test-de-cultuur-in-het-vlaams", "keyword": "Feature", "name": "Test de Cultuur in het Vlaams", + "uri": "Features/07Localization/Vlaams.feature", "tags": [], "line": 1, "elements": [ { + "id": "test-de-cultuur-in-het-vlaams;het-scenario", "keyword": "Scenario", "name": "Het Scenario", "line": 4, @@ -1201,8 +1342,9 @@ "keyword": "Given", "name": "dat ik 50 ingeef", "line": 5, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1210,8 +1352,9 @@ "keyword": "And", "name": "dat ik 70 ingeef", "line": 6, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1219,8 +1362,9 @@ "keyword": "When", "name": "ik plus druk", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1228,8 +1372,9 @@ "keyword": "Then", "name": "moet het resultaat 120 zijn", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1238,12 +1383,15 @@ ] }, { + "id": "attribute-overloading", "keyword": "Feature", "name": "Attribute overloading", + "uri": "Features/08AttributeOverloading/AttributeOverloading.feature", "tags": [], "line": 1, "elements": [ { + "id": "attribute-overloading;checking-number-for-evenness", "keyword": "Scenario", "name": "Checking number for evenness", "line": 6, @@ -1254,8 +1402,9 @@ "keyword": "Given", "name": "I have this simple step", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1263,8 +1412,9 @@ "keyword": "And", "name": "this simple step", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1272,8 +1422,9 @@ "keyword": "And", "name": "also this step", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1281,8 +1432,9 @@ "keyword": "When", "name": "I do something", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1290,8 +1442,9 @@ "keyword": "Then", "name": "I could validate that the number 2 is even", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1299,8 +1452,9 @@ "keyword": "And", "name": "that the number 4 is even", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1308,8 +1462,9 @@ "keyword": "But", "name": "the number 3 is odd", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1318,12 +1473,15 @@ ] }, { + "id": "calling-steps-from-stepdefinitions", "keyword": "Feature", "name": "Calling Steps from StepDefinitions", + "uri": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", "tags": [], "line": 1, "elements": [ { + "id": "calling-steps-from-stepdefinitions;log-in", "keyword": "Scenario", "name": "Log in", "line": 6, @@ -1334,8 +1492,9 @@ "keyword": "Given", "name": "I am on the index page", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1343,8 +1502,9 @@ "keyword": "When", "name": "I enter my unsername nad password", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1352,8 +1512,9 @@ "keyword": "And", "name": "I click the login button", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1361,14 +1522,16 @@ "keyword": "Then", "name": "the welcome page should be displayed", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "calling-steps-from-stepdefinitions;do-something-meaningful", "keyword": "Scenario", "name": "Do something meaningful", "line": 12, @@ -1379,8 +1542,9 @@ "keyword": "Given", "name": "I am logged in", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1388,8 +1552,9 @@ "keyword": "When", "name": "I dosomething meaningful", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1397,8 +1562,9 @@ "keyword": "Then", "name": "I should get rewarded", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1407,12 +1573,15 @@ ] }, { + "id": "step-argument-transformations", "keyword": "Feature", "name": "Step Argument Transformations", + "uri": "Features/10StepTransformation/StepTransformation.feature", "tags": [], "line": 1, "elements": [ { + "id": "step-argument-transformations;steps-with-non-string-arguments", "keyword": "Scenario", "name": "Steps with non-string arguments", "line": 6, @@ -1423,8 +1592,9 @@ "keyword": "Given", "name": "Dan has been registered at date 2003/03/13", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1432,8 +1602,9 @@ "keyword": "And", "name": "Aslak has been registered at terminal 2", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1441,8 +1612,9 @@ "keyword": "Then", "name": "I should be able to see Aslak at terminal 2", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1451,12 +1623,15 @@ ] }, { + "id": "injecting-context-into-step-specifications", "keyword": "Feature", "name": "Injecting context into step specifications", + "uri": "Features/11ContextInjection/ContextInjection.feature", "tags": [], "line": 1, "elements": [ { + "id": "injecting-context-into-step-specifications;feature-with-no-context", "keyword": "Scenario", "name": "Feature with no context", "line": 8, @@ -1467,8 +1642,9 @@ "keyword": "Given", "name": "a feature which requires no context", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1476,14 +1652,16 @@ "keyword": "Then", "name": "everything is dandy", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-a-single-context", "keyword": "Scenario", "name": "Feature with a single context", "line": 12, @@ -1494,8 +1672,9 @@ "keyword": "Given", "name": "a feature which requires a single context", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1503,14 +1682,16 @@ "keyword": "Then", "name": "the context is set", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-multiple-contexts", "keyword": "Scenario", "name": "Feature with multiple contexts", "line": 16, @@ -1521,8 +1702,9 @@ "keyword": "Given", "name": "a feature which requires multiple contexts", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1530,14 +1712,16 @@ "keyword": "Then", "name": "the contexts are set", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-recursive-contexts", "keyword": "Scenario", "name": "Feature with recursive contexts", "line": 20, @@ -1548,8 +1732,9 @@ "keyword": "Given", "name": "a feature which requires a recursive context", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1557,8 +1742,9 @@ "keyword": "Then", "name": "the context is set", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1566,14 +1752,16 @@ "keyword": "And", "name": "its sub-context is set", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-a-dependent-context", "keyword": "Scenario", "name": "Feature with a dependent context", "line": 25, @@ -1584,8 +1772,9 @@ "keyword": "Given", "name": "a feature which requires a single context", "line": 26, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1593,8 +1782,9 @@ "keyword": "Then", "name": "the context is set", "line": 27, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1602,8 +1792,9 @@ "keyword": "And", "name": "the context was created by the feature with a single context scenario", "line": 28, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1612,12 +1803,15 @@ ] }, { + "id": "nested-folder-example", "keyword": "Feature", "name": "Nested Folder Example", + "uri": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", "tags": [], "line": 1, "elements": [ { + "id": "nested-folder-example;nested---add-two-numbers", "keyword": "Scenario", "name": "Nested - Add two numbers", "line": 7, @@ -1632,8 +1826,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1641,8 +1836,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1650,8 +1846,9 @@ "keyword": "When", "name": "I press add", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1659,8 +1856,9 @@ "keyword": "Then", "name": "the result should be 120 on the screen", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1669,12 +1867,15 @@ ] }, { + "id": "multiline-feature-example", "keyword": "Feature", "name": "Multiline Feature Example", + "uri": "Features/13MultilineText/MultilineFeatureExample.feature", "tags": [], "line": 1, "elements": [ { + "id": "multiline-feature-example;mutliline-output", "keyword": "Scenario", "name": "Mutliline Output", "line": 7, @@ -1689,8 +1890,9 @@ "keyword": "Given", "name": "I have read in some text from the user", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1698,8 +1900,9 @@ "keyword": "When", "name": "I process this input", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1707,8 +1910,9 @@ "keyword": "Then", "name": "the result will be saved to the multiline text data store", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1717,12 +1921,15 @@ ] }, { + "id": "sample-markdown-feature", "keyword": "Feature", "name": "Sample Markdown Feature", + "uri": "Features/14MarkdownExample/MarkdownExamples.feature", "tags": [], "line": 1, "elements": [ { + "id": "sample-markdown-feature;sample-markdown-scenario-example", "keyword": "Scenario", "name": "Sample Markdown Scenario Example", "line": 44, @@ -1733,8 +1940,9 @@ "keyword": "Given", "name": "this", "line": 62, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1742,18 +1950,20 @@ "keyword": "Then", "name": "that", "line": 63, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { - "keyword": "Scenario Outline", + "id": "sample-markdown-feature;sample-markdown-scenario-outline-example", + "keyword": "Scenario", "name": "Sample Markdown Scenario Outline Example", "line": 66, - "type": "scenario_outline", + "type": "scenario", "tags": [ { "name": "@AddingATag" @@ -1764,8 +1974,9 @@ "keyword": "Given", "name": "this: ", "line": 72, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1773,8 +1984,9 @@ "keyword": "Then", "name": "that: ", "line": 73, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1783,12 +1995,15 @@ ] }, { + "id": "interactive-dhtml-view", "keyword": "Feature", "name": "Interactive DHTML View", + "uri": "Features/15Pickles/InteractiveDHTMLView.feature", "tags": [], "line": 1, "elements": [ { + "id": "interactive-dhtml-view;scenario-with-large-data-table", "keyword": "Scenario", "name": "Scenario with large data table", "line": 7, @@ -1799,8 +2014,9 @@ "keyword": "Given", "name": "a feature with a large table of data:", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1808,8 +2024,9 @@ "keyword": "When", "name": "I click on the table heading", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1817,8 +2034,9 @@ "keyword": "Then", "name": "the table body should collapse", "line": 33, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1827,12 +2045,15 @@ ] }, { + "id": "kinds-of-verification", "keyword": "Feature", "name": "Kinds of verification", + "uri": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "tags": [], "line": 1, "elements": [ { + "id": "kinds-of-verification;verified-automatically", "keyword": "Scenario", "name": "Verified automatically", "line": 8, @@ -1847,8 +2068,9 @@ "keyword": "Given", "name": "a feature that is verified automatically", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1856,8 +2078,9 @@ "keyword": "When", "name": "I run pickles", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1865,14 +2088,16 @@ "keyword": "Then", "name": "it appears in the @automated summary", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "kinds-of-verification;verified-manually", "keyword": "Scenario", "name": "Verified manually", "line": 14, @@ -1887,8 +2112,9 @@ "keyword": "Given", "name": "a feature that is verified manually", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1896,8 +2122,9 @@ "keyword": "When", "name": "I run pickles", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1905,14 +2132,16 @@ "keyword": "Then", "name": "it appears in the @manual summary", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "kinds-of-verification;verified-automatically", "keyword": "Scenario", "name": "Verified automatically", "line": 20, @@ -1927,8 +2156,9 @@ "keyword": "Given", "name": "a feature that is not verified", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1936,8 +2166,9 @@ "keyword": "When", "name": "I run pickles", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1945,8 +2176,9 @@ "keyword": "Then", "name": "it appears in the @notTested summary", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1955,12 +2187,15 @@ ] }, { + "id": "arithmetic", "keyword": "Feature", "name": "Arithmetic", + "uri": "Features/Arithmetic.feature", "tags": [], "line": 1, "elements": [ { + "id": "arithmetic;add-two-numbers", "keyword": "Scenario", "name": "Add two numbers", "line": 10, @@ -1978,8 +2213,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1987,8 +2223,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1996,8 +2233,9 @@ "keyword": "When", "name": "I press add", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2005,14 +2243,16 @@ "keyword": "Then", "name": "the result should be 120 on the screen", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "arithmetic;subtract-two-numbers", "keyword": "Scenario", "name": "Subtract two numbers", "line": 21, @@ -2030,8 +2270,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2039,8 +2280,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2048,8 +2290,9 @@ "keyword": "When", "name": "I press subtract", "line": 24, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2057,14 +2300,16 @@ "keyword": "Then", "name": "the result should be -20 on the screen", "line": 25, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "arithmetic;multiply-two-numbers", "keyword": "Scenario", "name": "Multiply two numbers", "line": 28, @@ -2082,8 +2327,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2091,8 +2337,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 30, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2100,8 +2347,9 @@ "keyword": "When", "name": "I press multiply", "line": 31, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2109,14 +2357,16 @@ "keyword": "Then", "name": "the result should be 3500 on the screen", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "arithmetic;divide-two-numbers", "keyword": "Scenario", "name": "Divide two numbers", "line": 35, @@ -2134,8 +2384,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 36, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2143,8 +2394,9 @@ "keyword": "And", "name": "I have entered 2 into the calculator", "line": 37, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2152,8 +2404,9 @@ "keyword": "When", "name": "I press divide", "line": 38, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2161,8 +2414,9 @@ "keyword": "Then", "name": "the result should be 25 on the screen", "line": 39, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -2171,12 +2425,15 @@ ] }, { + "id": "trigonometry", "keyword": "Feature", "name": "Trigonometry", + "uri": "Features/Trigonometry.feature", "tags": [], "line": 1, "elements": [ { + "id": "trigonometry;sine", "keyword": "Scenario", "name": "Sine", "line": 7, @@ -2194,8 +2451,9 @@ "keyword": "Given", "name": "I have entered 90 into the calculator", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2203,8 +2461,9 @@ "keyword": "When", "name": "I press sin", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2212,14 +2471,16 @@ "keyword": "Then", "name": "the result should be 1 on the screen", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "trigonometry;cosine", "keyword": "Scenario", "name": "Cosine", "line": 13, @@ -2237,8 +2498,9 @@ "keyword": "Given", "name": "I have entered 0 into the calculator", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2246,8 +2508,9 @@ "keyword": "When", "name": "I press cos", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2255,14 +2518,16 @@ "keyword": "Then", "name": "the result should be 1 on the screen", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "trigonometry;tangent", "keyword": "Scenario", "name": "Tangent", "line": 19, @@ -2280,8 +2545,9 @@ "keyword": "Given", "name": "I have entered 45 into the calculator", "line": 20, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2289,8 +2555,9 @@ "keyword": "When", "name": "I press tan", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2298,8 +2565,9 @@ "keyword": "Then", "name": "the result should be 1 on the screen", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -2308,12 +2576,15 @@ ] }, { + "id": "clearing-screen", "keyword": "Feature", "name": "Clearing Screen", + "uri": "Features/Workflow/ClearingScreen.feature", "tags": [], "line": 1, "elements": [ { + "id": "clearing-screen;clear-the-screen", "keyword": "Scenario", "name": "Clear the screen", "line": 7, @@ -2331,8 +2602,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2340,8 +2612,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2349,8 +2622,9 @@ "keyword": "When", "name": "I press C", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2358,8 +2632,9 @@ "keyword": "Then", "name": "the screen should be empty", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } diff --git a/Output/Dhtml/Index.html b/Output/Dhtml/Index.html index 6bc691b98..12d020a91 100644 --- a/Output/Dhtml/Index.html +++ b/Output/Dhtml/Index.html @@ -14,13 +14,7 @@ - - - + diff --git a/Output/Dhtml/default.htm b/Output/Dhtml/default.htm deleted file mode 100644 index 3e777c9dc..000000000 --- a/Output/Dhtml/default.htm +++ /dev/null @@ -1,554 +0,0 @@ - - - - - - Features - - - - - - - - - - - - - - -
- Loading... -
- - - - - - - - - - - - -
-
-
-
-
-
-
-
- -
- - -
- -
Generated on:
-
-
-
- -
-
-
-
- - - - -
-

-
-
- -
-
-
-

Background:

-
-
    -
    -
    - -
    -
    - - - - - -
    - -
    -
    - -
    -

    -
    -
    - -
    - -
      - -
        -
      • -
        - - - - - - -
        -
        - : -
        -
        -
        -
        • -
      - -
      - - - Get Link for Scenario - -
      -
      -
      - - -
      - - -
      -
      - - - -
      - - -
      -
      -
      -
      -
      - -
      - -
      -
      -

      Scenario Summary by Root Namespace

      - -
      -
      -

      Scenario Summary by Top 20 Tags

      - -
      -
      -

      @NotTested Scenario Summary by Root Namespace

      - -
      -
      -
      - -
      - - - - - - - - - - - - - - - - - - - - - - - diff --git a/Output/Dhtml/img/glyphicons-halflings-white.png b/Output/Dhtml/img/glyphicons-halflings-white.png index a001c35f8..776b00aef 100644 Binary files a/Output/Dhtml/img/glyphicons-halflings-white.png and b/Output/Dhtml/img/glyphicons-halflings-white.png differ diff --git a/Output/Dhtml/img/glyphicons-halflings.png b/Output/Dhtml/img/glyphicons-halflings.png index f15c257ee..39207652a 100644 Binary files a/Output/Dhtml/img/glyphicons-halflings.png and b/Output/Dhtml/img/glyphicons-halflings.png differ diff --git a/Output/Dhtml/img/link.png b/Output/Dhtml/img/link.png index 68fc43b7c..312176330 100644 Binary files a/Output/Dhtml/img/link.png and b/Output/Dhtml/img/link.png differ diff --git a/Output/Dhtml/pickledFeatures.js b/Output/Dhtml/pickledFeatures.js index 5219e541a..26b15eb4a 100644 --- a/Output/Dhtml/pickledFeatures.js +++ b/Output/Dhtml/pickledFeatures.js @@ -1,12 +1,13 @@ jsonPWrapper ({ "Features": [ { - "RelativeFolder": "Features\\00BasicGherkin\\BasicGherkin.feature", + "RelativeFolder": "Features/00BasicGherkin/BasicGherkin.feature", "Feature": { "Name": "Showing basic gherkin syntax", - "Description": "In order to see that gherkin is a very simple language \r\nAs a SpecFlow evangelist \r\nI want to show that basic syntax\r\n\r\n![Test Image](test.jpg)", + "Description": "In order to see that gherkin is a very simple language \nAs a SpecFlow evangelist \nI want to show that basic syntax\n\n![Test Image](test.jpg)", "FeatureElements": [ { + "Examples": [], "Name": "Simple GWT", "Slug": "simple-gwt", "Description": "", @@ -41,6 +42,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Using And and But", "Slug": "using-and-and-but", "Description": "", @@ -110,12 +112,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\01TestRunner\\TestRunnerIsNotImportant.feature", + "RelativeFolder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", "Feature": { "Name": "The test runner is not (very) important", - "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to be able to call my steps in the same manner inspite of the testrunner configured", + "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \nAs a SpecFlow evanglist \nI want to be able to call my steps in the same manner inspite of the testrunner configured", "FeatureElements": [ { + "Examples": [], "Name": "A couple of simple steps", "Slug": "a-couple-of-simple-steps", "Description": "", @@ -164,12 +167,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\Hooks.feature", + "RelativeFolder": "Features/02TagsAndHooks/Hooks.feature", "Feature": { "Name": "Addition", - "Description": "In order to explain the order in which hooks are run \r\nAs a SpecFlow evanglist \r\nI wan to be able to hook into pre and post conditions in SpecFlow", + "Description": "In order to explain the order in which hooks are run \nAs a SpecFlow evanglist \nI wan to be able to hook into pre and post conditions in SpecFlow", "FeatureElements": [ { + "Examples": [], "Name": "Hooking into pre conditions for Test Runs in SpecFlow", "Slug": "hooking-into-pre-conditions-for-test-runs-in-specflow", "Description": "", @@ -197,6 +201,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Features in SpecFlow", "Slug": "hooking-into-pre-conditions-for-features-in-specflow", "Description": "", @@ -224,6 +229,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Scenarios in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarios-in-specflow", "Description": "", @@ -251,6 +257,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for ScenarioBlocks in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarioblocks-in-specflow", "Description": "", @@ -278,6 +285,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Steps in SpecFlow", "Slug": "hooking-into-pre-conditions-for-steps-in-specflow", "Description": "", @@ -319,12 +327,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\TagDemo.feature", + "RelativeFolder": "Features/02TagsAndHooks/TagDemo.feature", "Feature": { "Name": "Tag demonstrator", - "Description": "In order to show the capabilities of tags in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to write scenarios that has tags and show their usage in code", + "Description": "In order to show the capabilities of tags in SpecFlow \nAs a SpecFlow evanglist \nI want to write scenarios that has tags and show their usage in code", "FeatureElements": [ { + "Examples": [], "Name": "Ignored scenario", "Slug": "ignored-scenario", "Description": "", @@ -368,6 +377,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario without tags", "Slug": "a-scenario-without-tags", "Description": "", @@ -402,6 +412,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario with 1 tag", "Slug": "a-scenario-with-1-tag", "Description": "", @@ -438,6 +449,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario with 3 tags", "Slug": "a-scenario-with-3-tags", "Description": "", @@ -476,6 +488,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario with 2 tags", "Slug": "a-scenario-with-2-tags", "Description": "", @@ -530,10 +543,10 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\03ScenarioOutline\\ScenarioOutline.feature", + "RelativeFolder": "Features/03ScenarioOutline/ScenarioOutline.feature", "Feature": { "Name": "Scenario outline", - "Description": "In order to not have to type the same scenario over and over \r\nAs a SpecFlow evangelist \r\nI want to show how to use ScenarioOutline", + "Description": "In order to not have to type the same scenario over and over \nAs a SpecFlow evangelist \nI want to show how to use ScenarioOutline", "FeatureElements": [ { "Examples": [ @@ -801,12 +814,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\031ScenarioContext\\ScenarioContext.feature", + "RelativeFolder": "Features/031ScenarioContext/ScenarioContext.feature", "Feature": { "Name": "Scenario Context features", - "Description": "In order to show how to use ScenarioContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in ScenarioContext", + "Description": "In order to show how to use ScenarioContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in ScenarioContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from ScenarioContext", "Slug": "store-and-retrive-person-marcus-from-scenariocontext", "Description": "", @@ -834,6 +848,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Showing information of the scenario", "Slug": "showing-information-of-the-scenario", "Description": "", @@ -880,6 +895,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Show the type of step we're currently on", "Slug": "show-the-type-of-step-were-currently-on", "Description": "", @@ -928,6 +944,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Display error information in AfterScenario", "Slug": "display-error-information-in-afterscenario", "Description": "", @@ -951,6 +968,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Pending step", "Slug": "pending-step", "Description": "", @@ -992,12 +1010,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\032FeatureContext\\FeatureContextFeatures.feature", + "RelativeFolder": "Features/032FeatureContext/FeatureContextFeatures.feature", "Feature": { "Name": "FeatureContext features", - "Description": "In order to show how to use FeatureContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in FeatureContext", + "Description": "In order to show how to use FeatureContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in FeatureContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from FeatureContext Current", "Slug": "store-and-retrive-person-marcus-from-featurecontext-current", "Description": "", @@ -1025,6 +1044,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Showing information of the feature", "Slug": "showing-information-of-the-feature", "Description": "", @@ -1097,12 +1117,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\04Background\\BackgroundFeature.feature", + "RelativeFolder": "Features/04Background/BackgroundFeature.feature", "Feature": { "Name": "Show the use of background", - "Description": "In order to show how to use the Background keyword of Gherkin \r\nAs a SpecFlow evanglist \r\nI want to show that background steps are called before any scenario step", + "Description": "In order to show how to use the Background keyword of Gherkin \nAs a SpecFlow evanglist \nI want to show that background steps are called before any scenario step", "FeatureElements": [ { + "Examples": [], "Name": "Add 1 to the sum", "Slug": "add-1-to-the-sum", "Description": "", @@ -1130,6 +1151,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Add 2 to the sum", "Slug": "add-2-to-the-sum", "Description": "", @@ -1158,6 +1180,7 @@ jsonPWrapper ({ } ], "Background": { + "Examples": [], "Name": "", "Description": "", "Steps": [ @@ -1197,12 +1220,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\05TablesAndAssist\\TableScenario.feature", + "RelativeFolder": "Features/05TablesAndAssist/TableScenario.feature", "Feature": { "Name": "Showing table usage", - "Description": "In order to show how to use tables \r\nAs a SpecFlow evanglist \r\nI want to write some simple scenarios that uses tables tables", + "Description": "In order to show how to use tables \nAs a SpecFlow evanglist \nI want to write some simple scenarios that uses tables tables", "FeatureElements": [ { + "Examples": [], "Name": "Using tables", "Slug": "using-tables", "Description": "", @@ -1281,6 +1305,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Using tables with SpecFlow Assist", "Slug": "using-tables-with-specflow-assist", "Description": "", @@ -1359,6 +1384,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Creating a entity from field value", "Slug": "creating-a-entity-from-field-value", "Description": "", @@ -1426,6 +1452,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Example of a wide table", "Slug": "example-of-a-wide-table", "Description": "", @@ -1532,12 +1559,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\06CompareToAssist\\CompareTo.feature", + "RelativeFolder": "Features/06CompareToAssist/CompareTo.feature", "Feature": { "Name": "Show the compare to feature", - "Description": "In order to show the compare to features of SpecFlow Assist \r\nAs a SpecFlow evanglist \r\nI want to show how the different versions of compareTo works", + "Description": "In order to show the compare to features of SpecFlow Assist \nAs a SpecFlow evanglist \nI want to show how the different versions of compareTo works", "FeatureElements": [ { + "Examples": [], "Name": "CompareToInstance", "Slug": "comparetoinstance", "Description": "", @@ -1662,6 +1690,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "CompareToSet", "Slug": "comparetoset", "Description": "", @@ -1777,12 +1806,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\07Localization\\Svenska.feature", + "RelativeFolder": "Features/07Localization/Svenska.feature", "Feature": { "Name": "Svenska - Summering", - "Description": "För att slippa att göra dumma fel \r\nSom räknare \r\nVill jag kunna lägga summera", + "Description": "För att slippa att göra dumma fel \nSom räknare \nVill jag kunna lägga summera", "FeatureElements": [ { + "Examples": [], "Name": "Summera 5 och 7 ska vara 12", "Slug": "summera-5-och-7-ska-vara-12", "Description": "", @@ -1838,12 +1868,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\07Localization\\Vlaams.feature", + "RelativeFolder": "Features/07Localization/Vlaams.feature", "Feature": { "Name": "Test de Cultuur in het Vlaams", "Description": "", "FeatureElements": [ { + "Examples": [], "Name": "Het Scenario", "Slug": "het-scenario", "Description": "", @@ -1899,12 +1930,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\08AttributeOverloading\\AttributeOverloading.feature", + "RelativeFolder": "Features/08AttributeOverloading/AttributeOverloading.feature", "Feature": { "Name": "Attribute overloading", - "Description": "In order to show that steps can be used with multiple attributes \r\nAs a SpecFlow Evangelist \r\nI want to show that similar attributes can be applied to the same step definition", + "Description": "In order to show that steps can be used with multiple attributes \nAs a SpecFlow Evangelist \nI want to show that similar attributes can be applied to the same step definition", "FeatureElements": [ { + "Examples": [], "Name": "Checking number for evenness", "Slug": "checking-number-for-evenness", "Description": "", @@ -1981,12 +2013,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\09CallingStepsFromSteps\\CallingStepsFromSteps.feature", + "RelativeFolder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", "Feature": { "Name": "Calling Steps from StepDefinitions", - "Description": "In order to create steps of a higher abstraction \r\nAs a SpecFlow evangelist \r\nI want reuse other steps in my step definitions", + "Description": "In order to create steps of a higher abstraction \nAs a SpecFlow evangelist \nI want reuse other steps in my step definitions", "FeatureElements": [ { + "Examples": [], "Name": "Log in", "Slug": "log-in", "Description": "", @@ -2028,6 +2061,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Do something meaningful", "Slug": "do-something-meaningful", "Description": "", @@ -2076,12 +2110,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\10StepTransformation\\StepTransformation.feature", + "RelativeFolder": "Features/10StepTransformation/StepTransformation.feature", "Feature": { "Name": "Step Argument Transformations", - "Description": "In order to reduce the amount of code and repetitive tasks in my steps \r\nAs a SpecFlow evanglist \r\nI want to define reusable transformations for my step arguments", + "Description": "In order to reduce the amount of code and repetitive tasks in my steps \nAs a SpecFlow evanglist \nI want to define reusable transformations for my step arguments", "FeatureElements": [ { + "Examples": [], "Name": "Steps with non-string arguments", "Slug": "steps-with-non-string-arguments", "Description": "", @@ -2130,12 +2165,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\11ContextInjection\\ContextInjection.feature", + "RelativeFolder": "Features/11ContextInjection/ContextInjection.feature", "Feature": { "Name": "Injecting context into step specifications", - "Description": "In order to don't have to rely on the global shared state\r\nand to be able to define the contexts required for each scenario. \r\nAs a SpecFlow Evanglist \r\nI would like to have the system automatically inject an instance of any class as\r\ndefined in the constructor of a step file", + "Description": "In order to don't have to rely on the global shared state\nand to be able to define the contexts required for each scenario. \nAs a SpecFlow Evanglist \nI would like to have the system automatically inject an instance of any class as\ndefined in the constructor of a step file", "FeatureElements": [ { + "Examples": [], "Name": "Feature with no context", "Slug": "feature-with-no-context", "Description": "", @@ -2163,6 +2199,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with a single context", "Slug": "feature-with-a-single-context", "Description": "", @@ -2190,6 +2227,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with multiple contexts", "Slug": "feature-with-multiple-contexts", "Description": "", @@ -2217,6 +2255,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with recursive contexts", "Slug": "feature-with-recursive-contexts", "Description": "", @@ -2251,6 +2290,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with a dependent context", "Slug": "feature-with-a-dependent-context", "Description": "", @@ -2299,12 +2339,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\12NestedFolders\\ChildFolder\\ChildChildFolder\\NestedFolderExample.feature", + "RelativeFolder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", "Feature": { "Name": "Nested Folder Example", - "Description": "In order to test nested folder output \r\nAs a silly contributer \r\nI want to create an example of something several folders deep", + "Description": "In order to test nested folder output \nAs a silly contributer \nI want to create an example of something several folders deep", "FeatureElements": [ { + "Examples": [], "Name": "Nested - Add two numbers", "Slug": "nested---add-two-numbers", "Description": "", @@ -2362,12 +2403,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\13MultilineText\\MultilineFeatureExample.feature", + "RelativeFolder": "Features/13MultilineText/MultilineFeatureExample.feature", "Feature": { "Name": "Multiline Feature Example", - "Description": "In order capture this particular Gherkin feature \r\nAs a Pickles contributer \r\nI want to demonstrate an example of using multiline text in a Scenario", + "Description": "In order capture this particular Gherkin feature \nAs a Pickles contributer \nI want to demonstrate an example of using multiline text in a Scenario", "FeatureElements": [ { + "Examples": [], "Name": "Mutliline Output", "Slug": "mutliline-output", "Description": "", @@ -2376,7 +2418,7 @@ jsonPWrapper ({ "Keyword": "Given", "NativeKeyword": "Given ", "Name": "I have read in some text from the user", - "DocStringArgument": "This is line 1.\r\nThis is line 2!\r\nThis is line 3!!", + "DocStringArgument": "This is line 1.\nThis is line 2!\nThis is line 3!!", "StepComments": [], "AfterLastStepComments": [] }, @@ -2419,15 +2461,16 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\14MarkdownExample\\MarkdownExamples.feature", + "RelativeFolder": "Features/14MarkdownExample/MarkdownExamples.feature", "Feature": { "Name": "Sample Markdown Feature", - "Description": "# Header 1\r\n\r\n## Header 2\r\n\r\n### Header 3\r\n\r\n#### Header 4\r\n\r\n##### Header 5\r\n\r\n###### Header 6\r\n\r\nThis is a *significant* word\r\n\r\n1. Ordered #1\r\n2. Ordered #2\r\n3. Ordered #3\r\n\r\n- Unordered #1\r\n- Unordered #2\r\n- Unordered #3\r\n\r\nHorizontal Rule:\r\n- - -\r\n\r\nTable example:\r\n\r\n| First Header | Second Header |\r\n| ------------- | ------------- |\r\n| Content Cell | Content Cell |\r\n| Content Cell | Content Cell |\r\n\r\n- - -\r\n\r\nIncluding a picture: ![](./image.png)", + "Description": "# Header 1\n\n## Header 2\n\n### Header 3\n\n#### Header 4\n\n##### Header 5\n\n###### Header 6\n\nThis is a *significant* word\n\n1. Ordered #1\n2. Ordered #2\n3. Ordered #3\n\n- Unordered #1\n- Unordered #2\n- Unordered #3\n\nHorizontal Rule:\n- - -\n\nTable example:\n\n| First Header | Second Header |\n| ------------- | ------------- |\n| Content Cell | Content Cell |\n| Content Cell | Content Cell |\n\n- - -\n\nIncluding a picture: ![](./image.png)", "FeatureElements": [ { + "Examples": [], "Name": "Sample Markdown Scenario Example", "Slug": "sample-markdown-scenario-example", - "Description": "This is **important** text\r\n\r\nCode Block:\r\n\r\n```\r\nvar x = 2;\r\n```\r\n\r\nApple\r\n: Pomaceous fruit of plants of the genus Malus in\r\n the family Rosaceae.\r\n: An American computer company.\r\n\r\nOrange\r\n: The fruit of an evergreen tree of the genus Citrus.", + "Description": "This is **important** text\n\nCode Block:\n\n```\nvar x = 2;\n```\n\nApple\n: Pomaceous fruit of plants of the genus Malus in\n the family Rosaceae.\n: An American computer company.\n\nOrange\n: The fruit of an evergreen tree of the genus Citrus.", "Steps": [ { "Keyword": "Given", @@ -2479,7 +2522,7 @@ jsonPWrapper ({ ], "Name": "Sample Markdown Scenario Outline Example", "Slug": "sample-markdown-scenario-outline-example", - "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\r\n\r\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", + "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\n\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", "Steps": [ { "Keyword": "Given", @@ -2507,6 +2550,7 @@ jsonPWrapper ({ } ], "Background": { + "Examples": [], "Name": "", "Description": "This is the *coolest* background", "Steps": [ @@ -2546,12 +2590,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\15Pickles\\InteractiveDHTMLView.feature", + "RelativeFolder": "Features/15Pickles/InteractiveDHTMLView.feature", "Feature": { "Name": "Interactive DHTML View", - "Description": "In order to increase stakeholder engagement with pickled specs \r\nAs a SpecFlow evangelist \r\nI want to adjust the level of detail in the DHTML view to suite my audience \r\nSo that I do not overwhelm them.", + "Description": "In order to increase stakeholder engagement with pickled specs \nAs a SpecFlow evangelist \nI want to adjust the level of detail in the DHTML view to suite my audience \nSo that I do not overwhelm them.", "FeatureElements": [ { + "Examples": [], "Name": "Scenario with large data table", "Slug": "scenario-with-large-data-table", "Description": "", @@ -2696,12 +2741,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\15Pickles\\NotTestedAutomatedManualTags.feature", + "RelativeFolder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Feature": { "Name": "Kinds of verification", - "Description": "In order to increase stakeholder engagement with pickled specs\r\nAs a SpecFlow evangelist\r\nI want to make clear how many scenarios are automated, manually tested and not tested\r\nSo that the stakeholders have a better overview of progress", + "Description": "In order to increase stakeholder engagement with pickled specs\nAs a SpecFlow evangelist\nI want to make clear how many scenarios are automated, manually tested and not tested\nSo that the stakeholders have a better overview of progress", "FeatureElements": [ { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2738,6 +2784,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Verified manually", "Slug": "verified-manually", "Description": "", @@ -2774,6 +2821,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2824,12 +2872,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\Arithmetic.feature", + "RelativeFolder": "Features/Arithmetic.feature", "Feature": { "Name": "Arithmetic", - "Description": "In order to avoid silly mistakes \r\nAs a math idiot \r\nI want to be able to perform arithmetic on the calculator\r\n\r\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\r\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", + "Description": "In order to avoid silly mistakes \nAs a math idiot \nI want to be able to perform arithmetic on the calculator\n\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", "FeatureElements": [ { + "Examples": [], "Name": "Add two numbers", "Slug": "add-two-numbers", "Description": "$50 + 70 = 120$", @@ -2878,6 +2927,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Subtract two numbers", "Slug": "subtract-two-numbers", "Description": "", @@ -2922,6 +2972,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Multiply two numbers", "Slug": "multiply-two-numbers", "Description": "", @@ -2966,6 +3017,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Divide two numbers", "Slug": "divide-two-numbers", "Description": "", @@ -3024,12 +3076,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\Trigonometry.feature", + "RelativeFolder": "Features/Trigonometry.feature", "Feature": { "Name": "Trigonometry", - "Description": "In order to avoid perform more advanced calculations \r\nAs a math idiot \r\nI want to be able to use trigonometric functions", + "Description": "In order to avoid perform more advanced calculations \nAs a math idiot \nI want to be able to use trigonometric functions", "FeatureElements": [ { + "Examples": [], "Name": "Sine", "Slug": "sine", "Description": "", @@ -3067,6 +3120,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Cosine", "Slug": "cosine", "Description": "", @@ -3104,6 +3158,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Tangent", "Slug": "tangent", "Description": "", @@ -3155,12 +3210,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\Workflow\\ClearingScreen.feature", + "RelativeFolder": "Features/Workflow/ClearingScreen.feature", "Feature": { "Name": "Clearing Screen", - "Description": "In order to restart a new set of calculations \r\nAs a math idiot \r\nI want to be able to clear the screen", + "Description": "In order to restart a new set of calculations \nAs a math idiot \nI want to be able to clear the screen", "FeatureElements": [ { + "Examples": [], "Name": "Clear the screen", "Slug": "clear-the-screen", "Description": "", @@ -3364,20 +3420,342 @@ jsonPWrapper ({ ], "Folders": [ { - "Folder": "Features", - "Total": 57, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, "Passing": 0, "Failing": 0, - "Inconclusive": 57 + "Inconclusive": 1 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 } ], "NotTestedFolders": [ { - "Folder": "Features", + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Total": 1, "Passing": 0, "Failing": 0, "Inconclusive": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 } ], "Scenarios": { @@ -3394,17 +3772,178 @@ jsonPWrapper ({ }, "FoldersWithTestKinds": [ { - "Folder": "Features", - "Total": 57, - "Automated": 55, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Automated": 1, "Manual": 1, "NotTested": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Automated": 3, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 } ] }, "Configuration": { "SutName": "Pickles", - "SutVersion": "2.3.3", - "GeneratedOn": "11 March 2021 17:02:53" + "SutVersion": "3.0.1", + "GeneratedOn": "4 October 2021 17:16:08" } }); \ No newline at end of file diff --git a/Output/Excel/features.xlsx b/Output/Excel/features.xlsx index 68f0ab9f2..e69397311 100644 Binary files a/Output/Excel/features.xlsx and b/Output/Excel/features.xlsx differ diff --git a/Output/Html/Features/00BasicGherkin/BasicGherkin.html b/Output/Html/Features/00BasicGherkin/BasicGherkin.html index 55d790e72..6f0b2c7d2 100644 --- a/Output/Html/Features/00BasicGherkin/BasicGherkin.html +++ b/Output/Html/Features/00BasicGherkin/BasicGherkin.html @@ -257,7 +257,9 @@

      Showing basic gherkin syntax

      -

      In order to see that gherkin is a very simple language
      As a SpecFlow evangelist
      I want to show that basic syntax

      +

      In order to see that gherkin is a very simple language
      +As a SpecFlow evangelist
      +I want to show that basic syntax

      Test Image

      @@ -308,9 +310,9 @@

      Using And and But

      diff --git a/Output/Html/Features/00BasicGherkin/index.html b/Output/Html/Features/00BasicGherkin/index.html index 5260e7fb4..eba16bd42 100644 --- a/Output/Html/Features/00BasicGherkin/index.html +++ b/Output/Html/Features/00BasicGherkin/index.html @@ -271,9 +271,9 @@

      00 Basic Gherkin

      diff --git a/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html b/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html index cc4d2c6b4..ac735d653 100644 --- a/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html +++ b/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html @@ -257,7 +257,9 @@

      The test runner is not (very) important

      -

      In order to show that the test runner is just for the autogenerated stuff in SpecFlow
      As a SpecFlow evanglist
      I want to be able to call my steps in the same manner inspite of the testrunner configured

      +

      In order to show that the test runner is just for the autogenerated stuff in SpecFlow
      +As a SpecFlow evanglist
      +I want to be able to call my steps in the same manner inspite of the testrunner configured

      • @@ -281,9 +283,9 @@

        A couple of simple steps

      diff --git a/Output/Html/Features/01TestRunner/index.html b/Output/Html/Features/01TestRunner/index.html index 511029880..e6173d275 100644 --- a/Output/Html/Features/01TestRunner/index.html +++ b/Output/Html/Features/01TestRunner/index.html @@ -269,9 +269,9 @@

      01 Test Runner

      diff --git a/Output/Html/Features/02TagsAndHooks/Hooks.html b/Output/Html/Features/02TagsAndHooks/Hooks.html index 1d948078b..3e0293e76 100644 --- a/Output/Html/Features/02TagsAndHooks/Hooks.html +++ b/Output/Html/Features/02TagsAndHooks/Hooks.html @@ -257,7 +257,9 @@

      Addition

      -

      In order to explain the order in which hooks are run
      As a SpecFlow evanglist
      I wan to be able to hook into pre and post conditions in SpecFlow

      +

      In order to explain the order in which hooks are run
      +As a SpecFlow evanglist
      +I wan to be able to hook into pre and post conditions in SpecFlow

      • @@ -343,9 +345,9 @@

        Hooking into pre conditions for Steps in SpecFlow

      diff --git a/Output/Html/Features/02TagsAndHooks/TagDemo.html b/Output/Html/Features/02TagsAndHooks/TagDemo.html index e74c4c3ef..232fed700 100644 --- a/Output/Html/Features/02TagsAndHooks/TagDemo.html +++ b/Output/Html/Features/02TagsAndHooks/TagDemo.html @@ -258,7 +258,9 @@

      Tags: @allAboutTags, @important

      Tag demonstrator

      -

      In order to show the capabilities of tags in SpecFlow
      As a SpecFlow evanglist
      I want to write scenarios that has tags and show their usage in code

      +

      In order to show the capabilities of tags in SpecFlow
      +As a SpecFlow evanglist
      +I want to write scenarios that has tags and show their usage in code

      • @@ -361,9 +363,9 @@

        A scenario with 2 tags

      diff --git a/Output/Html/Features/02TagsAndHooks/index.html b/Output/Html/Features/02TagsAndHooks/index.html index 8895d244d..57afffe24 100644 --- a/Output/Html/Features/02TagsAndHooks/index.html +++ b/Output/Html/Features/02TagsAndHooks/index.html @@ -278,9 +278,9 @@

      02 Tags And Hooks

      diff --git a/Output/Html/Features/031ScenarioContext/ScenarioContext.html b/Output/Html/Features/031ScenarioContext/ScenarioContext.html index b8305a2b2..d99e2ede2 100644 --- a/Output/Html/Features/031ScenarioContext/ScenarioContext.html +++ b/Output/Html/Features/031ScenarioContext/ScenarioContext.html @@ -257,7 +257,9 @@

      Scenario Context features

      -

      In order to show how to use ScenarioContext
      As a SpecFlow evangelist
      I want to write some simple scenarios with data in ScenarioContext

      +

      In order to show how to use ScenarioContext
      +As a SpecFlow evangelist
      +I want to write some simple scenarios with data in ScenarioContext

      • @@ -347,9 +349,9 @@

        Pending step

      diff --git a/Output/Html/Features/031ScenarioContext/index.html b/Output/Html/Features/031ScenarioContext/index.html index a57b846ef..1865046a4 100644 --- a/Output/Html/Features/031ScenarioContext/index.html +++ b/Output/Html/Features/031ScenarioContext/index.html @@ -269,9 +269,9 @@

      031 Scenario Context

      diff --git a/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html b/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html index 929845e6d..639ab80fe 100644 --- a/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html +++ b/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html @@ -258,7 +258,9 @@

      Tags: @andThisToo, @showUpInScenarioInfo

      FeatureContext features

      -

      In order to show how to use FeatureContext
      As a SpecFlow evangelist
      I want to write some simple scenarios with data in FeatureContext

      +

      In order to show how to use FeatureContext
      +As a SpecFlow evangelist
      +I want to write some simple scenarios with data in FeatureContext

      • @@ -298,9 +300,9 @@

        Showing information of the feature

      diff --git a/Output/Html/Features/032FeatureContext/index.html b/Output/Html/Features/032FeatureContext/index.html index 29f4e1f42..16d747f53 100644 --- a/Output/Html/Features/032FeatureContext/index.html +++ b/Output/Html/Features/032FeatureContext/index.html @@ -269,9 +269,9 @@

      032 Feature Context

      diff --git a/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html b/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html index 2617fa54c..580583bff 100644 --- a/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html +++ b/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html @@ -257,7 +257,9 @@

      Scenario outline

      -

      In order to not have to type the same scenario over and over
      As a SpecFlow evangelist
      I want to show how to use ScenarioOutline

      +

      In order to not have to type the same scenario over and over
      +As a SpecFlow evangelist
      +I want to show how to use ScenarioOutline

      • @@ -433,9 +435,9 @@

        Examples: more than 100

      diff --git a/Output/Html/Features/03ScenarioOutline/index.html b/Output/Html/Features/03ScenarioOutline/index.html index a9fc1ee7a..97ce98022 100644 --- a/Output/Html/Features/03ScenarioOutline/index.html +++ b/Output/Html/Features/03ScenarioOutline/index.html @@ -269,9 +269,9 @@

      03 Scenario Outline

      diff --git a/Output/Html/Features/04Background/BackgroundFeature.html b/Output/Html/Features/04Background/BackgroundFeature.html index ea6696cfa..3d9bbe534 100644 --- a/Output/Html/Features/04Background/BackgroundFeature.html +++ b/Output/Html/Features/04Background/BackgroundFeature.html @@ -257,13 +257,12 @@

      Show the use of background

      -

      In order to show how to use the Background keyword of Gherkin
      As a SpecFlow evanglist
      I want to show that background steps are called before any scenario step

      +

      In order to show how to use the Background keyword of Gherkin
      +As a SpecFlow evanglist
      +I want to show that background steps are called before any scenario step

      • -
        -

        -
        • @@ -308,9 +307,9 @@

          Add 2 to the sum

      diff --git a/Output/Html/Features/04Background/index.html b/Output/Html/Features/04Background/index.html index 2342b2e21..9f8af10b9 100644 --- a/Output/Html/Features/04Background/index.html +++ b/Output/Html/Features/04Background/index.html @@ -269,9 +269,9 @@

      04 Background

      diff --git a/Output/Html/Features/05TablesAndAssist/TableScenario.html b/Output/Html/Features/05TablesAndAssist/TableScenario.html index ba3ae752e..bd9054386 100644 --- a/Output/Html/Features/05TablesAndAssist/TableScenario.html +++ b/Output/Html/Features/05TablesAndAssist/TableScenario.html @@ -257,7 +257,9 @@

      Showing table usage

      -

      In order to show how to use tables
      As a SpecFlow evanglist
      I want to write some simple scenarios that uses tables tables

      +

      In order to show how to use tables
      +As a SpecFlow evanglist
      +I want to write some simple scenarios that uses tables tables

      • @@ -329,9 +331,9 @@

        Example of a wide table

      diff --git a/Output/Html/Features/05TablesAndAssist/index.html b/Output/Html/Features/05TablesAndAssist/index.html index 73412c68a..2819484d9 100644 --- a/Output/Html/Features/05TablesAndAssist/index.html +++ b/Output/Html/Features/05TablesAndAssist/index.html @@ -269,9 +269,9 @@

      05 Tables And Assist

      diff --git a/Output/Html/Features/06CompareToAssist/CompareTo.html b/Output/Html/Features/06CompareToAssist/CompareTo.html index 8a79d6a53..9a03e7024 100644 --- a/Output/Html/Features/06CompareToAssist/CompareTo.html +++ b/Output/Html/Features/06CompareToAssist/CompareTo.html @@ -257,7 +257,9 @@

      Show the compare to feature

      -

      In order to show the compare to features of SpecFlow Assist
      As a SpecFlow evanglist
      I want to show how the different versions of compareTo works

      +

      In order to show the compare to features of SpecFlow Assist
      +As a SpecFlow evanglist
      +I want to show how the different versions of compareTo works

      • @@ -301,9 +303,9 @@

        CompareToSet

      diff --git a/Output/Html/Features/06CompareToAssist/index.html b/Output/Html/Features/06CompareToAssist/index.html index 8da9acf15..1f7139890 100644 --- a/Output/Html/Features/06CompareToAssist/index.html +++ b/Output/Html/Features/06CompareToAssist/index.html @@ -269,9 +269,9 @@

      06 Compare To Assist

      diff --git a/Output/Html/Features/07Localization/Svenska.html b/Output/Html/Features/07Localization/Svenska.html index 765d0c125..f9ca59dde 100644 --- a/Output/Html/Features/07Localization/Svenska.html +++ b/Output/Html/Features/07Localization/Svenska.html @@ -257,7 +257,9 @@

      Svenska - Summering

      -

      För att slippa att göra dumma fel
      Som räknare
      Vill jag kunna lägga summera

      +

      För att slippa att göra dumma fel
      +Som räknare
      +Vill jag kunna lägga summera

      • @@ -283,9 +285,9 @@

        Summera 5 och 7 ska vara 12

      diff --git a/Output/Html/Features/07Localization/Vlaams.html b/Output/Html/Features/07Localization/Vlaams.html index 1d8f16a71..de487e577 100644 --- a/Output/Html/Features/07Localization/Vlaams.html +++ b/Output/Html/Features/07Localization/Vlaams.html @@ -280,9 +280,9 @@

      Het Scenario

      diff --git a/Output/Html/Features/07Localization/index.html b/Output/Html/Features/07Localization/index.html index 7a2d93d0b..6c1276cb7 100644 --- a/Output/Html/Features/07Localization/index.html +++ b/Output/Html/Features/07Localization/index.html @@ -276,9 +276,9 @@

      07 Localization

      diff --git a/Output/Html/Features/07Svenska/Svenska.html b/Output/Html/Features/07Svenska/Svenska.html deleted file mode 100644 index f048cc883..000000000 --- a/Output/Html/Features/07Svenska/Svenska.html +++ /dev/null @@ -1,291 +0,0 @@ - - - - - Summering - - - - - - - - -
      -
      - -
      -

      Summering

      -
      - 
      -            För att slippa att göra dumma fel
-Som räknare
-Vill jag kunna lägga summera
-
-
      -
      -
        -
      • -
        -

        Summera 5 och 7 ska vara 12

        -
        -
        -
          -
        • - Givet att jag har knappat in 5
          • -
        • - Och att jag har knappat in 7
          • -
        • - När jag summerar
          • -
        • - Så ska resultatet vara 12
          • -
        -
        - - - -
        • -
      -
      - -
      - - \ No newline at end of file diff --git a/Output/Html/Features/07Svenska/index.html b/Output/Html/Features/07Svenska/index.html deleted file mode 100644 index 7baaa912e..000000000 --- a/Output/Html/Features/07Svenska/index.html +++ /dev/null @@ -1,272 +0,0 @@ - - - - - 07 Svenska - - - - - - - - -
      -
      - - - -
      - - \ No newline at end of file diff --git a/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html b/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html index b1dfa138a..f278f71be 100644 --- a/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html +++ b/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html @@ -257,7 +257,9 @@

      Attribute overloading

      -

      In order to show that steps can be used with multiple attributes
      As a SpecFlow Evangelist
      I want to show that similar attributes can be applied to the same step definition

      +

      In order to show that steps can be used with multiple attributes
      +As a SpecFlow Evangelist
      +I want to show that similar attributes can be applied to the same step definition

      • @@ -289,9 +291,9 @@

        Checking number for evenness

      diff --git a/Output/Html/Features/08AttributeOverloading/index.html b/Output/Html/Features/08AttributeOverloading/index.html index 93bcccd3d..35cb28a88 100644 --- a/Output/Html/Features/08AttributeOverloading/index.html +++ b/Output/Html/Features/08AttributeOverloading/index.html @@ -269,9 +269,9 @@

      08 Attribute Overloading

      diff --git a/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html b/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html index c58a87aae..9edcb964f 100644 --- a/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html +++ b/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html @@ -257,7 +257,9 @@

      Calling Steps from StepDefinitions

      -

      In order to create steps of a higher abstraction
      As a SpecFlow evangelist
      I want reuse other steps in my step definitions

      +

      In order to create steps of a higher abstraction
      +As a SpecFlow evangelist
      +I want reuse other steps in my step definitions

      • @@ -301,9 +303,9 @@

        Do something meaningful

      diff --git a/Output/Html/Features/09CallingStepsFromSteps/index.html b/Output/Html/Features/09CallingStepsFromSteps/index.html index 189592f00..2c52fbfa3 100644 --- a/Output/Html/Features/09CallingStepsFromSteps/index.html +++ b/Output/Html/Features/09CallingStepsFromSteps/index.html @@ -269,9 +269,9 @@

      09 Calling Steps From Steps

      diff --git a/Output/Html/Features/10StepTransformation/StepTransformation.html b/Output/Html/Features/10StepTransformation/StepTransformation.html index 3ff82cc5a..e693d6877 100644 --- a/Output/Html/Features/10StepTransformation/StepTransformation.html +++ b/Output/Html/Features/10StepTransformation/StepTransformation.html @@ -257,7 +257,9 @@

      Step Argument Transformations

      -

      In order to reduce the amount of code and repetitive tasks in my steps
      As a SpecFlow evanglist
      I want to define reusable transformations for my step arguments

      +

      In order to reduce the amount of code and repetitive tasks in my steps
      +As a SpecFlow evanglist
      +I want to define reusable transformations for my step arguments

      • @@ -281,9 +283,9 @@

        Steps with non-string arguments

      diff --git a/Output/Html/Features/10StepTransformation/index.html b/Output/Html/Features/10StepTransformation/index.html index 9e1e09ba6..0c844ae9b 100644 --- a/Output/Html/Features/10StepTransformation/index.html +++ b/Output/Html/Features/10StepTransformation/index.html @@ -269,9 +269,9 @@

      10 Step Transformation

      diff --git a/Output/Html/Features/11ContextInjection/ContextInjection.html b/Output/Html/Features/11ContextInjection/ContextInjection.html index bf3c84006..16cf5d0d7 100644 --- a/Output/Html/Features/11ContextInjection/ContextInjection.html +++ b/Output/Html/Features/11ContextInjection/ContextInjection.html @@ -258,7 +258,9 @@

      Injecting context into step specifications

      In order to don't have to rely on the global shared state -and to be able to define the contexts required for each scenario.
      As a SpecFlow Evanglist
      I would like to have the system automatically inject an instance of any class as +and to be able to define the contexts required for each scenario.
      +As a SpecFlow Evanglist
      +I would like to have the system automatically inject an instance of any class as defined in the constructor of a step file

        @@ -349,9 +351,9 @@

        Feature with a dependent context

      diff --git a/Output/Html/Features/11ContextInjection/index.html b/Output/Html/Features/11ContextInjection/index.html index fcc20fbe2..aa92ee7fa 100644 --- a/Output/Html/Features/11ContextInjection/index.html +++ b/Output/Html/Features/11ContextInjection/index.html @@ -271,9 +271,9 @@

      11 Context Injection

      diff --git a/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html b/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html index 8b34ffc05..9d0bbadb0 100644 --- a/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html +++ b/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html @@ -257,7 +257,9 @@

      Nested Folder Example

      -

      In order to test nested folder output
      As a silly contributer
      I want to create an example of something several folders deep

      +

      In order to test nested folder output
      +As a silly contributer
      +I want to create an example of something several folders deep

      • @@ -284,9 +286,9 @@

        Nested - Add two numbers

      diff --git a/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html b/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html index 4a7d67fc0..3e4857ac0 100644 --- a/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html +++ b/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html @@ -269,9 +269,9 @@

      Child Child Folder

      diff --git a/Output/Html/Features/12NestedFolders/ChildFolder/index.html b/Output/Html/Features/12NestedFolders/ChildFolder/index.html index aded3db1f..f185f0d95 100644 --- a/Output/Html/Features/12NestedFolders/ChildFolder/index.html +++ b/Output/Html/Features/12NestedFolders/ChildFolder/index.html @@ -259,9 +259,9 @@

      Child Folder

        diff --git a/Output/Html/Features/12NestedFolders/index.html b/Output/Html/Features/12NestedFolders/index.html index 3935a9575..b91d7c697 100644 --- a/Output/Html/Features/12NestedFolders/index.html +++ b/Output/Html/Features/12NestedFolders/index.html @@ -259,9 +259,9 @@

        12 Nested Folders

          diff --git a/Output/Html/Features/13MultilineText/MultilineFeatureExample.html b/Output/Html/Features/13MultilineText/MultilineFeatureExample.html index 034eb328e..0b51a0636 100644 --- a/Output/Html/Features/13MultilineText/MultilineFeatureExample.html +++ b/Output/Html/Features/13MultilineText/MultilineFeatureExample.html @@ -257,7 +257,9 @@

          Multiline Feature Example

          -

          In order capture this particular Gherkin feature
          As a Pickles contributer
          I want to demonstrate an example of using multiline text in a Scenario

          +

          In order capture this particular Gherkin feature
          +As a Pickles contributer
          +I want to demonstrate an example of using multiline text in a Scenario

          • @@ -284,9 +286,9 @@

            Mutliline Output

          diff --git a/Output/Html/Features/13MultilineText/index.html b/Output/Html/Features/13MultilineText/index.html index 4cfbc186a..ded1a85c5 100644 --- a/Output/Html/Features/13MultilineText/index.html +++ b/Output/Html/Features/13MultilineText/index.html @@ -269,9 +269,9 @@

          13 Multiline Text

        diff --git a/Output/Html/Features/14MarkdownExample/MarkdownExamples.html b/Output/Html/Features/14MarkdownExample/MarkdownExamples.html index 72d2a3730..ba0d9f487 100644 --- a/Output/Html/Features/14MarkdownExample/MarkdownExamples.html +++ b/Output/Html/Features/14MarkdownExample/MarkdownExamples.html @@ -257,23 +257,25 @@

        Sample Markdown Feature

        -

        Header 1

        -

        Header 2

        -

        Header 3

        -

        Header 4

        -
        Header 5
        -
        Header 6
        +

        Header 1

        +

        Header 2

        +

        Header 3

        +

        Header 4

        +
        Header 5
        +
        Header 6

        This is a significant word

        1. Ordered #1
        2. Ordered #2
          3. -
        3. Ordered #3
          4. -
        -
          -
        • Unordered #1
          • +
        • +

          Ordered #3

          +
          • +
        • +

          Unordered #1

          +
        • Unordered #2
        • Unordered #3
          • -
        +

        Horizontal Rule:

        Table example:

        @@ -296,16 +298,10 @@
        Header 6
        -

        Including a picture:

        +

        Including a picture:

        • -
          -

          -
          -

          This is the coolest background

          -
          -
          • @@ -325,12 +321,16 @@

            Sample Markdown Scenario Example

            var x = 2; -

            Apple -: Pomaceous fruit of plants of the genus Malus in - the family Rosaceae. -: An American computer company.

            -

            Orange -: The fruit of an evergreen tree of the genus Citrus.

            +
            +
            Apple
            +
            +

            Pomaceous fruit of plants of the genus Malus in +the family Rosaceae.

            +
            +
            An American computer company.
            +
            Orange
            +
            The fruit of an evergreen tree of the genus Citrus.
            +
        @@ -398,9 +398,9 @@

        Examples:

      diff --git a/Output/Html/Features/14MarkdownExample/index.html b/Output/Html/Features/14MarkdownExample/index.html index dd17317bc..205a941b8 100644 --- a/Output/Html/Features/14MarkdownExample/index.html +++ b/Output/Html/Features/14MarkdownExample/index.html @@ -301,9 +301,9 @@

      14 Markdown Example

      diff --git a/Output/Html/Features/15Pickles/InteractiveDHTMLView.html b/Output/Html/Features/15Pickles/InteractiveDHTMLView.html index b2d4d264e..84218ed32 100644 --- a/Output/Html/Features/15Pickles/InteractiveDHTMLView.html +++ b/Output/Html/Features/15Pickles/InteractiveDHTMLView.html @@ -257,7 +257,10 @@

      Interactive DHTML View

      -

      In order to increase stakeholder engagement with pickled specs
      As a SpecFlow evangelist
      I want to adjust the level of detail in the DHTML view to suite my audience
      So that I do not overwhelm them.

      +

      In order to increase stakeholder engagement with pickled specs
      +As a SpecFlow evangelist
      +I want to adjust the level of detail in the DHTML view to suite my audience
      +So that I do not overwhelm them.

      • @@ -281,9 +284,9 @@

        Scenario with large data table

      diff --git a/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html b/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html index 38585f475..4f08ce0ce 100644 --- a/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html +++ b/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html @@ -323,9 +323,9 @@

      Verified automatically

      diff --git a/Output/Html/Features/15Pickles/index.html b/Output/Html/Features/15Pickles/index.html index 7e1eb9344..c82ef1bdd 100644 --- a/Output/Html/Features/15Pickles/index.html +++ b/Output/Html/Features/15Pickles/index.html @@ -280,9 +280,9 @@

      15 Pickles

      diff --git a/Output/Html/Features/Arithmetic.html b/Output/Html/Features/Arithmetic.html index fdb63e0b5..7ea9d57bf 100644 --- a/Output/Html/Features/Arithmetic.html +++ b/Output/Html/Features/Arithmetic.html @@ -257,7 +257,9 @@

      Arithmetic

      -

      In order to avoid silly mistakes
      As a math idiot
      I want to be able to perform arithmetic on the calculator

      +

      In order to avoid silly mistakes
      +As a math idiot
      +I want to be able to perform arithmetic on the calculator

      When $a \ne 0$, there are two solutions to $(ax^2 + bx + c = 0)$ and they are $$x = {-b \pm \sqrt{b^2-4ac} \over 2a}.$$

      @@ -353,9 +355,9 @@

      Divide two numbers

      diff --git a/Output/Html/Features/Trigonometry.html b/Output/Html/Features/Trigonometry.html index 5cb40794d..c657e3803 100644 --- a/Output/Html/Features/Trigonometry.html +++ b/Output/Html/Features/Trigonometry.html @@ -257,7 +257,9 @@

      Trigonometry

      -

      In order to avoid perform more advanced calculations
      As a math idiot
      I want to be able to use trigonometric functions

      +

      In order to avoid perform more advanced calculations
      +As a math idiot
      +I want to be able to use trigonometric functions

      • @@ -320,9 +322,9 @@

        Tangent

      diff --git a/Output/Html/Features/Workflow/ClearingScreen.html b/Output/Html/Features/Workflow/ClearingScreen.html index d41ba84f2..d1d7c369f 100644 --- a/Output/Html/Features/Workflow/ClearingScreen.html +++ b/Output/Html/Features/Workflow/ClearingScreen.html @@ -257,7 +257,9 @@

      Clearing Screen

      -

      In order to restart a new set of calculations
      As a math idiot
      I want to be able to clear the screen

      +

      In order to restart a new set of calculations
      +As a math idiot
      +I want to be able to clear the screen

      • @@ -284,9 +286,9 @@

        Clear the screen

      diff --git a/Output/Html/Features/Workflow/index.html b/Output/Html/Features/Workflow/index.html index 3906e4c4c..08418f2c6 100644 --- a/Output/Html/Features/Workflow/index.html +++ b/Output/Html/Features/Workflow/index.html @@ -269,9 +269,9 @@

      Workflow

      diff --git a/Output/Html/Features/index.html b/Output/Html/Features/index.html index 3618017a1..8aafdfc7e 100644 --- a/Output/Html/Features/index.html +++ b/Output/Html/Features/index.html @@ -281,9 +281,9 @@

      Features

      diff --git a/Output/Html/img/failure.png b/Output/Html/img/failure.png index b622cd135..03db140b9 100644 Binary files a/Output/Html/img/failure.png and b/Output/Html/img/failure.png differ diff --git a/Output/Html/img/inconclusive.png b/Output/Html/img/inconclusive.png index 0b3bf52e0..6bcceb509 100644 Binary files a/Output/Html/img/inconclusive.png and b/Output/Html/img/inconclusive.png differ diff --git a/Output/Html/img/success.png b/Output/Html/img/success.png index 2748ec6a7..6b888627e 100644 Binary files a/Output/Html/img/success.png and b/Output/Html/img/success.png differ diff --git a/Output/Html/index.html b/Output/Html/index.html index 5ac3eed20..f5a3f69f4 100644 --- a/Output/Html/index.html +++ b/Output/Html/index.html @@ -259,9 +259,9 @@

      Examples

        diff --git a/Output/Html/readme.html b/Output/Html/readme.html index 10adf9d99..7a5b90de2 100644 --- a/Output/Html/readme.html +++ b/Output/Html/readme.html @@ -258,9 +258,9 @@

        In the Features-folders you'll find quite a large population of .feature files that you can use to test out pickles on.

        diff --git a/Output/JSON/pickledFeatures.json b/Output/JSON/pickledFeatures.json index 014821554..57bd07582 100644 --- a/Output/JSON/pickledFeatures.json +++ b/Output/JSON/pickledFeatures.json @@ -1,12 +1,13 @@ { "Features": [ { - "RelativeFolder": "Features\\00BasicGherkin\\BasicGherkin.feature", + "RelativeFolder": "Features/00BasicGherkin/BasicGherkin.feature", "Feature": { "Name": "Showing basic gherkin syntax", - "Description": "In order to see that gherkin is a very simple language \r\nAs a SpecFlow evangelist \r\nI want to show that basic syntax\r\n\r\n![Test Image](test.jpg)", + "Description": "In order to see that gherkin is a very simple language \nAs a SpecFlow evangelist \nI want to show that basic syntax\n\n![Test Image](test.jpg)", "FeatureElements": [ { + "Examples": [], "Name": "Simple GWT", "Slug": "simple-gwt", "Description": "", @@ -41,6 +42,7 @@ } }, { + "Examples": [], "Name": "Using And and But", "Slug": "using-and-and-but", "Description": "", @@ -110,12 +112,13 @@ } }, { - "RelativeFolder": "Features\\01TestRunner\\TestRunnerIsNotImportant.feature", + "RelativeFolder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", "Feature": { "Name": "The test runner is not (very) important", - "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to be able to call my steps in the same manner inspite of the testrunner configured", + "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \nAs a SpecFlow evanglist \nI want to be able to call my steps in the same manner inspite of the testrunner configured", "FeatureElements": [ { + "Examples": [], "Name": "A couple of simple steps", "Slug": "a-couple-of-simple-steps", "Description": "", @@ -164,12 +167,13 @@ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\Hooks.feature", + "RelativeFolder": "Features/02TagsAndHooks/Hooks.feature", "Feature": { "Name": "Addition", - "Description": "In order to explain the order in which hooks are run \r\nAs a SpecFlow evanglist \r\nI wan to be able to hook into pre and post conditions in SpecFlow", + "Description": "In order to explain the order in which hooks are run \nAs a SpecFlow evanglist \nI wan to be able to hook into pre and post conditions in SpecFlow", "FeatureElements": [ { + "Examples": [], "Name": "Hooking into pre conditions for Test Runs in SpecFlow", "Slug": "hooking-into-pre-conditions-for-test-runs-in-specflow", "Description": "", @@ -197,6 +201,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Features in SpecFlow", "Slug": "hooking-into-pre-conditions-for-features-in-specflow", "Description": "", @@ -224,6 +229,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Scenarios in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarios-in-specflow", "Description": "", @@ -251,6 +257,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for ScenarioBlocks in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarioblocks-in-specflow", "Description": "", @@ -278,6 +285,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Steps in SpecFlow", "Slug": "hooking-into-pre-conditions-for-steps-in-specflow", "Description": "", @@ -319,12 +327,13 @@ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\TagDemo.feature", + "RelativeFolder": "Features/02TagsAndHooks/TagDemo.feature", "Feature": { "Name": "Tag demonstrator", - "Description": "In order to show the capabilities of tags in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to write scenarios that has tags and show their usage in code", + "Description": "In order to show the capabilities of tags in SpecFlow \nAs a SpecFlow evanglist \nI want to write scenarios that has tags and show their usage in code", "FeatureElements": [ { + "Examples": [], "Name": "Ignored scenario", "Slug": "ignored-scenario", "Description": "", @@ -368,6 +377,7 @@ } }, { + "Examples": [], "Name": "A scenario without tags", "Slug": "a-scenario-without-tags", "Description": "", @@ -402,6 +412,7 @@ } }, { + "Examples": [], "Name": "A scenario with 1 tag", "Slug": "a-scenario-with-1-tag", "Description": "", @@ -438,6 +449,7 @@ } }, { + "Examples": [], "Name": "A scenario with 3 tags", "Slug": "a-scenario-with-3-tags", "Description": "", @@ -476,6 +488,7 @@ } }, { + "Examples": [], "Name": "A scenario with 2 tags", "Slug": "a-scenario-with-2-tags", "Description": "", @@ -530,10 +543,10 @@ } }, { - "RelativeFolder": "Features\\03ScenarioOutline\\ScenarioOutline.feature", + "RelativeFolder": "Features/03ScenarioOutline/ScenarioOutline.feature", "Feature": { "Name": "Scenario outline", - "Description": "In order to not have to type the same scenario over and over \r\nAs a SpecFlow evangelist \r\nI want to show how to use ScenarioOutline", + "Description": "In order to not have to type the same scenario over and over \nAs a SpecFlow evangelist \nI want to show how to use ScenarioOutline", "FeatureElements": [ { "Examples": [ @@ -801,12 +814,13 @@ } }, { - "RelativeFolder": "Features\\031ScenarioContext\\ScenarioContext.feature", + "RelativeFolder": "Features/031ScenarioContext/ScenarioContext.feature", "Feature": { "Name": "Scenario Context features", - "Description": "In order to show how to use ScenarioContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in ScenarioContext", + "Description": "In order to show how to use ScenarioContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in ScenarioContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from ScenarioContext", "Slug": "store-and-retrive-person-marcus-from-scenariocontext", "Description": "", @@ -834,6 +848,7 @@ } }, { + "Examples": [], "Name": "Showing information of the scenario", "Slug": "showing-information-of-the-scenario", "Description": "", @@ -880,6 +895,7 @@ } }, { + "Examples": [], "Name": "Show the type of step we're currently on", "Slug": "show-the-type-of-step-were-currently-on", "Description": "", @@ -928,6 +944,7 @@ } }, { + "Examples": [], "Name": "Display error information in AfterScenario", "Slug": "display-error-information-in-afterscenario", "Description": "", @@ -951,6 +968,7 @@ } }, { + "Examples": [], "Name": "Pending step", "Slug": "pending-step", "Description": "", @@ -992,12 +1010,13 @@ } }, { - "RelativeFolder": "Features\\032FeatureContext\\FeatureContextFeatures.feature", + "RelativeFolder": "Features/032FeatureContext/FeatureContextFeatures.feature", "Feature": { "Name": "FeatureContext features", - "Description": "In order to show how to use FeatureContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in FeatureContext", + "Description": "In order to show how to use FeatureContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in FeatureContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from FeatureContext Current", "Slug": "store-and-retrive-person-marcus-from-featurecontext-current", "Description": "", @@ -1025,6 +1044,7 @@ } }, { + "Examples": [], "Name": "Showing information of the feature", "Slug": "showing-information-of-the-feature", "Description": "", @@ -1097,12 +1117,13 @@ } }, { - "RelativeFolder": "Features\\04Background\\BackgroundFeature.feature", + "RelativeFolder": "Features/04Background/BackgroundFeature.feature", "Feature": { "Name": "Show the use of background", - "Description": "In order to show how to use the Background keyword of Gherkin \r\nAs a SpecFlow evanglist \r\nI want to show that background steps are called before any scenario step", + "Description": "In order to show how to use the Background keyword of Gherkin \nAs a SpecFlow evanglist \nI want to show that background steps are called before any scenario step", "FeatureElements": [ { + "Examples": [], "Name": "Add 1 to the sum", "Slug": "add-1-to-the-sum", "Description": "", @@ -1130,6 +1151,7 @@ } }, { + "Examples": [], "Name": "Add 2 to the sum", "Slug": "add-2-to-the-sum", "Description": "", @@ -1158,6 +1180,7 @@ } ], "Background": { + "Examples": [], "Name": "", "Description": "", "Steps": [ @@ -1197,12 +1220,13 @@ } }, { - "RelativeFolder": "Features\\05TablesAndAssist\\TableScenario.feature", + "RelativeFolder": "Features/05TablesAndAssist/TableScenario.feature", "Feature": { "Name": "Showing table usage", - "Description": "In order to show how to use tables \r\nAs a SpecFlow evanglist \r\nI want to write some simple scenarios that uses tables tables", + "Description": "In order to show how to use tables \nAs a SpecFlow evanglist \nI want to write some simple scenarios that uses tables tables", "FeatureElements": [ { + "Examples": [], "Name": "Using tables", "Slug": "using-tables", "Description": "", @@ -1281,6 +1305,7 @@ } }, { + "Examples": [], "Name": "Using tables with SpecFlow Assist", "Slug": "using-tables-with-specflow-assist", "Description": "", @@ -1359,6 +1384,7 @@ } }, { + "Examples": [], "Name": "Creating a entity from field value", "Slug": "creating-a-entity-from-field-value", "Description": "", @@ -1426,6 +1452,7 @@ } }, { + "Examples": [], "Name": "Example of a wide table", "Slug": "example-of-a-wide-table", "Description": "", @@ -1532,12 +1559,13 @@ } }, { - "RelativeFolder": "Features\\06CompareToAssist\\CompareTo.feature", + "RelativeFolder": "Features/06CompareToAssist/CompareTo.feature", "Feature": { "Name": "Show the compare to feature", - "Description": "In order to show the compare to features of SpecFlow Assist \r\nAs a SpecFlow evanglist \r\nI want to show how the different versions of compareTo works", + "Description": "In order to show the compare to features of SpecFlow Assist \nAs a SpecFlow evanglist \nI want to show how the different versions of compareTo works", "FeatureElements": [ { + "Examples": [], "Name": "CompareToInstance", "Slug": "comparetoinstance", "Description": "", @@ -1662,6 +1690,7 @@ } }, { + "Examples": [], "Name": "CompareToSet", "Slug": "comparetoset", "Description": "", @@ -1777,12 +1806,13 @@ } }, { - "RelativeFolder": "Features\\07Localization\\Svenska.feature", + "RelativeFolder": "Features/07Localization/Svenska.feature", "Feature": { "Name": "Svenska - Summering", - "Description": "För att slippa att göra dumma fel \r\nSom räknare \r\nVill jag kunna lägga summera", + "Description": "För att slippa att göra dumma fel \nSom räknare \nVill jag kunna lägga summera", "FeatureElements": [ { + "Examples": [], "Name": "Summera 5 och 7 ska vara 12", "Slug": "summera-5-och-7-ska-vara-12", "Description": "", @@ -1838,12 +1868,13 @@ } }, { - "RelativeFolder": "Features\\07Localization\\Vlaams.feature", + "RelativeFolder": "Features/07Localization/Vlaams.feature", "Feature": { "Name": "Test de Cultuur in het Vlaams", "Description": "", "FeatureElements": [ { + "Examples": [], "Name": "Het Scenario", "Slug": "het-scenario", "Description": "", @@ -1899,12 +1930,13 @@ } }, { - "RelativeFolder": "Features\\08AttributeOverloading\\AttributeOverloading.feature", + "RelativeFolder": "Features/08AttributeOverloading/AttributeOverloading.feature", "Feature": { "Name": "Attribute overloading", - "Description": "In order to show that steps can be used with multiple attributes \r\nAs a SpecFlow Evangelist \r\nI want to show that similar attributes can be applied to the same step definition", + "Description": "In order to show that steps can be used with multiple attributes \nAs a SpecFlow Evangelist \nI want to show that similar attributes can be applied to the same step definition", "FeatureElements": [ { + "Examples": [], "Name": "Checking number for evenness", "Slug": "checking-number-for-evenness", "Description": "", @@ -1981,12 +2013,13 @@ } }, { - "RelativeFolder": "Features\\09CallingStepsFromSteps\\CallingStepsFromSteps.feature", + "RelativeFolder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", "Feature": { "Name": "Calling Steps from StepDefinitions", - "Description": "In order to create steps of a higher abstraction \r\nAs a SpecFlow evangelist \r\nI want reuse other steps in my step definitions", + "Description": "In order to create steps of a higher abstraction \nAs a SpecFlow evangelist \nI want reuse other steps in my step definitions", "FeatureElements": [ { + "Examples": [], "Name": "Log in", "Slug": "log-in", "Description": "", @@ -2028,6 +2061,7 @@ } }, { + "Examples": [], "Name": "Do something meaningful", "Slug": "do-something-meaningful", "Description": "", @@ -2076,12 +2110,13 @@ } }, { - "RelativeFolder": "Features\\10StepTransformation\\StepTransformation.feature", + "RelativeFolder": "Features/10StepTransformation/StepTransformation.feature", "Feature": { "Name": "Step Argument Transformations", - "Description": "In order to reduce the amount of code and repetitive tasks in my steps \r\nAs a SpecFlow evanglist \r\nI want to define reusable transformations for my step arguments", + "Description": "In order to reduce the amount of code and repetitive tasks in my steps \nAs a SpecFlow evanglist \nI want to define reusable transformations for my step arguments", "FeatureElements": [ { + "Examples": [], "Name": "Steps with non-string arguments", "Slug": "steps-with-non-string-arguments", "Description": "", @@ -2130,12 +2165,13 @@ } }, { - "RelativeFolder": "Features\\11ContextInjection\\ContextInjection.feature", + "RelativeFolder": "Features/11ContextInjection/ContextInjection.feature", "Feature": { "Name": "Injecting context into step specifications", - "Description": "In order to don't have to rely on the global shared state\r\nand to be able to define the contexts required for each scenario. \r\nAs a SpecFlow Evanglist \r\nI would like to have the system automatically inject an instance of any class as\r\ndefined in the constructor of a step file", + "Description": "In order to don't have to rely on the global shared state\nand to be able to define the contexts required for each scenario. \nAs a SpecFlow Evanglist \nI would like to have the system automatically inject an instance of any class as\ndefined in the constructor of a step file", "FeatureElements": [ { + "Examples": [], "Name": "Feature with no context", "Slug": "feature-with-no-context", "Description": "", @@ -2163,6 +2199,7 @@ } }, { + "Examples": [], "Name": "Feature with a single context", "Slug": "feature-with-a-single-context", "Description": "", @@ -2190,6 +2227,7 @@ } }, { + "Examples": [], "Name": "Feature with multiple contexts", "Slug": "feature-with-multiple-contexts", "Description": "", @@ -2217,6 +2255,7 @@ } }, { + "Examples": [], "Name": "Feature with recursive contexts", "Slug": "feature-with-recursive-contexts", "Description": "", @@ -2251,6 +2290,7 @@ } }, { + "Examples": [], "Name": "Feature with a dependent context", "Slug": "feature-with-a-dependent-context", "Description": "", @@ -2299,12 +2339,13 @@ } }, { - "RelativeFolder": "Features\\12NestedFolders\\ChildFolder\\ChildChildFolder\\NestedFolderExample.feature", + "RelativeFolder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", "Feature": { "Name": "Nested Folder Example", - "Description": "In order to test nested folder output \r\nAs a silly contributer \r\nI want to create an example of something several folders deep", + "Description": "In order to test nested folder output \nAs a silly contributer \nI want to create an example of something several folders deep", "FeatureElements": [ { + "Examples": [], "Name": "Nested - Add two numbers", "Slug": "nested---add-two-numbers", "Description": "", @@ -2362,12 +2403,13 @@ } }, { - "RelativeFolder": "Features\\13MultilineText\\MultilineFeatureExample.feature", + "RelativeFolder": "Features/13MultilineText/MultilineFeatureExample.feature", "Feature": { "Name": "Multiline Feature Example", - "Description": "In order capture this particular Gherkin feature \r\nAs a Pickles contributer \r\nI want to demonstrate an example of using multiline text in a Scenario", + "Description": "In order capture this particular Gherkin feature \nAs a Pickles contributer \nI want to demonstrate an example of using multiline text in a Scenario", "FeatureElements": [ { + "Examples": [], "Name": "Mutliline Output", "Slug": "mutliline-output", "Description": "", @@ -2376,7 +2418,7 @@ "Keyword": "Given", "NativeKeyword": "Given ", "Name": "I have read in some text from the user", - "DocStringArgument": "This is line 1.\r\nThis is line 2!\r\nThis is line 3!!", + "DocStringArgument": "This is line 1.\nThis is line 2!\nThis is line 3!!", "StepComments": [], "AfterLastStepComments": [] }, @@ -2419,15 +2461,16 @@ } }, { - "RelativeFolder": "Features\\14MarkdownExample\\MarkdownExamples.feature", + "RelativeFolder": "Features/14MarkdownExample/MarkdownExamples.feature", "Feature": { "Name": "Sample Markdown Feature", - "Description": "# Header 1\r\n\r\n## Header 2\r\n\r\n### Header 3\r\n\r\n#### Header 4\r\n\r\n##### Header 5\r\n\r\n###### Header 6\r\n\r\nThis is a *significant* word\r\n\r\n1. Ordered #1\r\n2. Ordered #2\r\n3. Ordered #3\r\n\r\n- Unordered #1\r\n- Unordered #2\r\n- Unordered #3\r\n\r\nHorizontal Rule:\r\n- - -\r\n\r\nTable example:\r\n\r\n| First Header | Second Header |\r\n| ------------- | ------------- |\r\n| Content Cell | Content Cell |\r\n| Content Cell | Content Cell |\r\n\r\n- - -\r\n\r\nIncluding a picture: ![](./image.png)", + "Description": "# Header 1\n\n## Header 2\n\n### Header 3\n\n#### Header 4\n\n##### Header 5\n\n###### Header 6\n\nThis is a *significant* word\n\n1. Ordered #1\n2. Ordered #2\n3. Ordered #3\n\n- Unordered #1\n- Unordered #2\n- Unordered #3\n\nHorizontal Rule:\n- - -\n\nTable example:\n\n| First Header | Second Header |\n| ------------- | ------------- |\n| Content Cell | Content Cell |\n| Content Cell | Content Cell |\n\n- - -\n\nIncluding a picture: ![](./image.png)", "FeatureElements": [ { + "Examples": [], "Name": "Sample Markdown Scenario Example", "Slug": "sample-markdown-scenario-example", - "Description": "This is **important** text\r\n\r\nCode Block:\r\n\r\n```\r\nvar x = 2;\r\n```\r\n\r\nApple\r\n: Pomaceous fruit of plants of the genus Malus in\r\n the family Rosaceae.\r\n: An American computer company.\r\n\r\nOrange\r\n: The fruit of an evergreen tree of the genus Citrus.", + "Description": "This is **important** text\n\nCode Block:\n\n```\nvar x = 2;\n```\n\nApple\n: Pomaceous fruit of plants of the genus Malus in\n the family Rosaceae.\n: An American computer company.\n\nOrange\n: The fruit of an evergreen tree of the genus Citrus.", "Steps": [ { "Keyword": "Given", @@ -2479,7 +2522,7 @@ ], "Name": "Sample Markdown Scenario Outline Example", "Slug": "sample-markdown-scenario-outline-example", - "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\r\n\r\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", + "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\n\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", "Steps": [ { "Keyword": "Given", @@ -2507,6 +2550,7 @@ } ], "Background": { + "Examples": [], "Name": "", "Description": "This is the *coolest* background", "Steps": [ @@ -2546,12 +2590,13 @@ } }, { - "RelativeFolder": "Features\\15Pickles\\InteractiveDHTMLView.feature", + "RelativeFolder": "Features/15Pickles/InteractiveDHTMLView.feature", "Feature": { "Name": "Interactive DHTML View", - "Description": "In order to increase stakeholder engagement with pickled specs \r\nAs a SpecFlow evangelist \r\nI want to adjust the level of detail in the DHTML view to suite my audience \r\nSo that I do not overwhelm them.", + "Description": "In order to increase stakeholder engagement with pickled specs \nAs a SpecFlow evangelist \nI want to adjust the level of detail in the DHTML view to suite my audience \nSo that I do not overwhelm them.", "FeatureElements": [ { + "Examples": [], "Name": "Scenario with large data table", "Slug": "scenario-with-large-data-table", "Description": "", @@ -2696,12 +2741,13 @@ } }, { - "RelativeFolder": "Features\\15Pickles\\NotTestedAutomatedManualTags.feature", + "RelativeFolder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Feature": { "Name": "Kinds of verification", - "Description": "In order to increase stakeholder engagement with pickled specs\r\nAs a SpecFlow evangelist\r\nI want to make clear how many scenarios are automated, manually tested and not tested\r\nSo that the stakeholders have a better overview of progress", + "Description": "In order to increase stakeholder engagement with pickled specs\nAs a SpecFlow evangelist\nI want to make clear how many scenarios are automated, manually tested and not tested\nSo that the stakeholders have a better overview of progress", "FeatureElements": [ { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2738,6 +2784,7 @@ } }, { + "Examples": [], "Name": "Verified manually", "Slug": "verified-manually", "Description": "", @@ -2774,6 +2821,7 @@ } }, { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2824,12 +2872,13 @@ } }, { - "RelativeFolder": "Features\\Arithmetic.feature", + "RelativeFolder": "Features/Arithmetic.feature", "Feature": { "Name": "Arithmetic", - "Description": "In order to avoid silly mistakes \r\nAs a math idiot \r\nI want to be able to perform arithmetic on the calculator\r\n\r\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\r\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", + "Description": "In order to avoid silly mistakes \nAs a math idiot \nI want to be able to perform arithmetic on the calculator\n\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", "FeatureElements": [ { + "Examples": [], "Name": "Add two numbers", "Slug": "add-two-numbers", "Description": "$50 + 70 = 120$", @@ -2878,6 +2927,7 @@ } }, { + "Examples": [], "Name": "Subtract two numbers", "Slug": "subtract-two-numbers", "Description": "", @@ -2922,6 +2972,7 @@ } }, { + "Examples": [], "Name": "Multiply two numbers", "Slug": "multiply-two-numbers", "Description": "", @@ -2966,6 +3017,7 @@ } }, { + "Examples": [], "Name": "Divide two numbers", "Slug": "divide-two-numbers", "Description": "", @@ -3024,12 +3076,13 @@ } }, { - "RelativeFolder": "Features\\Trigonometry.feature", + "RelativeFolder": "Features/Trigonometry.feature", "Feature": { "Name": "Trigonometry", - "Description": "In order to avoid perform more advanced calculations \r\nAs a math idiot \r\nI want to be able to use trigonometric functions", + "Description": "In order to avoid perform more advanced calculations \nAs a math idiot \nI want to be able to use trigonometric functions", "FeatureElements": [ { + "Examples": [], "Name": "Sine", "Slug": "sine", "Description": "", @@ -3067,6 +3120,7 @@ } }, { + "Examples": [], "Name": "Cosine", "Slug": "cosine", "Description": "", @@ -3104,6 +3158,7 @@ } }, { + "Examples": [], "Name": "Tangent", "Slug": "tangent", "Description": "", @@ -3155,12 +3210,13 @@ } }, { - "RelativeFolder": "Features\\Workflow\\ClearingScreen.feature", + "RelativeFolder": "Features/Workflow/ClearingScreen.feature", "Feature": { "Name": "Clearing Screen", - "Description": "In order to restart a new set of calculations \r\nAs a math idiot \r\nI want to be able to clear the screen", + "Description": "In order to restart a new set of calculations \nAs a math idiot \nI want to be able to clear the screen", "FeatureElements": [ { + "Examples": [], "Name": "Clear the screen", "Slug": "clear-the-screen", "Description": "", @@ -3364,20 +3420,342 @@ ], "Folders": [ { - "Folder": "Features", - "Total": 57, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, "Passing": 0, "Failing": 0, - "Inconclusive": 57 + "Inconclusive": 1 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 } ], "NotTestedFolders": [ { - "Folder": "Features", + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Total": 1, "Passing": 0, "Failing": 0, "Inconclusive": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 } ], "Scenarios": { @@ -3394,17 +3772,178 @@ }, "FoldersWithTestKinds": [ { - "Folder": "Features", - "Total": 57, - "Automated": 55, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Automated": 1, "Manual": 1, "NotTested": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Automated": 3, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 } ] }, "Configuration": { "SutName": "Pickles", - "SutVersion": "2.3.3", - "GeneratedOn": "11 March 2021 17:02:55" + "SutVersion": "3.0.1", + "GeneratedOn": "4 October 2021 17:16:11" } } \ No newline at end of file diff --git a/Output/Markdown/fail.png b/Output/Markdown/fail.png index 0e749af87..a5fcbf8f0 100644 Binary files a/Output/Markdown/fail.png and b/Output/Markdown/fail.png differ diff --git a/Output/Markdown/features.md b/Output/Markdown/features.md index f5d1061f3..f28062580 100644 --- a/Output/Markdown/features.md +++ b/Output/Markdown/features.md @@ -1,6 +1,6 @@ # Features -Generated on: 11 March 2021 at 17:02:55 +Generated on: 04 October 2021 at 17:16:12 ### Showing basic gherkin syntax @@ -162,7 +162,7 @@ As a SpecFlow evangelist I want to show how to use ScenarioOutline -#### Scenario Outline: Add two positive numbers with many examples +#### Scenario: Add two positive numbers with many examples > > **Given** I enter \ into the calculator > @@ -187,7 +187,7 @@ I want to show how to use ScenarioOutline > | 100 | 20 | 120 | > | 1000 | 20 | 1020 | > -#### Scenario Outline: Add two negative numbers with many examples +#### Scenario: Add two negative numbers with many examples > > **Given** I enter \ into the calculator > @@ -732,7 +732,7 @@ Including a picture: ![](./image.png) > *`@AddingATag`* -#### Scenario Outline: Sample Markdown Scenario Outline Example +#### Scenario: Sample Markdown Scenario Outline Example > > **Given** this: \ > diff --git a/Output/Markdown/inconclusive.png b/Output/Markdown/inconclusive.png index 951e767bc..babb6f040 100644 Binary files a/Output/Markdown/inconclusive.png and b/Output/Markdown/inconclusive.png differ diff --git a/Output/Markdown/pass.png b/Output/Markdown/pass.png index 753723a7a..7635df654 100644 Binary files a/Output/Markdown/pass.png and b/Output/Markdown/pass.png differ diff --git a/Output/Word/Pickles.docx b/Output/Word/Pickles.docx index 70fc77c2b..0746da218 100644 Binary files a/Output/Word/Pickles.docx and b/Output/Word/Pickles.docx differ diff --git a/Output/Word/features.docx b/Output/Word/features.docx deleted file mode 100644 index b3712d75d..000000000 Binary files a/Output/Word/features.docx and /dev/null differ diff --git a/README.md b/README.md index 723ade483..e1c600823 100644 --- a/README.md +++ b/README.md @@ -1,10 +1,3 @@ -Pickles will continue! -========================= - -After the great years of taking care of Pickles, I'm happy to announce that I found someone to take over the role of managing Pickles! We are in the process of handing over everything, and will make a detailed announcement when that is done. - -If you are I retested in contributing to the code - Pickles is widely used and in need of an update - create an issue where you mentioned that you want to contribute. Thanks! - Pickles ======= @@ -12,14 +5,11 @@ Pickles is an open source living documentation generator that works on feature f [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com) [![Join the chat at https://gitter.im/picklesdoc/pickles](https://badges.gitter.im/picklesdoc/pickles.svg)](https://gitter.im/picklesdoc/pickles?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge) -[![Build status](https://ci.appveyor.com/api/projects/status/rqt59hq1m2jt2a5v?svg=true)](https://ci.appveyor.com/project/dirkrombauts/pickles-715) | |Status | |-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------| | Docs |[![Documentation Status](https://readthedocs.org/projects/pickles/badge/?version=stable)](http://docs.picklesdoc.com/en/latest/) | | GitHub Release |[![GitHub release](https://img.shields.io/github/release/picklesdoc/pickles.svg)](https://github.com/picklesdoc/pickles/releases/latest) | -| Chocolatey (pickles) |[![Chocolatey](https://img.shields.io/chocolatey/v/pickles.svg)](https://chocolatey.org/packages/pickles) | -| Chocolatey (picklesui) |[![Chocolatey](https://img.shields.io/chocolatey/v/picklesui.svg)](https://chocolatey.org/packages/picklesui) | | NuGet (Pickles) |[![NuGet](https://img.shields.io/nuget/v/Pickles.svg)](https://www.nuget.org/packages/Pickles) | | NuGet (Pickles.CommandLine) |[![NuGet](https://img.shields.io/nuget/v/Pickles.CommandLine.svg)](https://www.nuget.org/packages/Pickles.CommandLine) | | NuGet (Pickles.MSBuild) |[![NuGet](https://img.shields.io/nuget/v/Pickles.MSBuild.svg)](https://www.nuget.org/packages/Pickles.MSBuild) | diff --git a/VERIFICATION.txt b/VERIFICATION.txt deleted file mode 100644 index 2119faf96..000000000 --- a/VERIFICATION.txt +++ /dev/null @@ -1,8 +0,0 @@ - -VERIFICATION -Verification is intended to assist the Chocolatey moderators and community -in verifying that this package's contents are trustworthy. - -This package is published by the Pickles project itself. The binaries are identical to other -package types published by the project, for example the nuget.org packages or the releases -on the GitHub project page. \ No newline at end of file diff --git a/build.bat b/build.bat deleted file mode 100644 index 7d91634d9..000000000 --- a/build.bat +++ /dev/null @@ -1,32 +0,0 @@ -@echo off -set "picklesVersion=2.3.3" - -cls - -rem "packages\nuget\NuGet.exe" "Install" "FAKE" "-OutputDirectory" "packages" "-ExcludeVersion" -"packages\nuget\NuGet.exe" "Install" "Chocolatey" "-OutputDirectory" "packages" "-ExcludeVersion" -rem "packages\nuget\NuGet.exe" "Install" "NUnit.ConsoleRunner" "-OutputDirectory" "packages" "-ExcludeVersion" -rem "packages\nuget\NuGet.exe" "Restore" "src\Pickles\Pickles.sln" - -rem "packages\FAKE\tools\Fake.exe" build.fsx --envvar version %picklesVersion% -rem "packages\FAKE\tools\Fake.exe" test.fsx --envvar version %picklesVersion% -rem if errorlevel 1 goto handleerror1orhigher -rem "packages\FAKE\tools\Fake.exe" nuget.fsx --envvar version %picklesVersion% -rem "packages\FAKE\tools\Fake.exe" chocolatey.fsx --envvar version %picklesVersion% - -rem call InstallPackages.cmd - -rem FOR %%A IN (testRunnerCmd testRunnerMsBuild testRunnerPowerShell) DO ( -rem call %%A.cmd %picklesVersion% -rem if errorlevel 1 goto handleerror1orhigher -rem ) - -@ECHO all fine -goto end - -:handleerror1orhigher - -@ECHO Something went wrong! -goto end - -:end diff --git a/build.cmd b/build.cmd old mode 100644 new mode 100755 index 95de4cac9..b08cc590f --- a/build.cmd +++ b/build.cmd @@ -1 +1,7 @@ -call build.bat \ No newline at end of file +:; set -eo pipefail +:; SCRIPT_DIR=$(cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd) +:; ${SCRIPT_DIR}/build.sh "$@" +:; exit $? + +@ECHO OFF +powershell -ExecutionPolicy ByPass -NoProfile -File "%~dp0build.ps1" %* diff --git a/build.fsx b/build.fsx deleted file mode 100644 index 92bb6d05b..000000000 --- a/build.fsx +++ /dev/null @@ -1,181 +0,0 @@ -// include Fake lib -#r @"packages\FAKE\tools\FakeLib.dll" -open Fake -open Fake.AssemblyInfoFile - -// Properties -let buildDir = "./build/" -let cmdDir = "./build/exe/" -let msBuildDir = "./build/msbuild/" -let powerShellDir = "./build/powershell/" -let guiDir = "./build/gui/" -let testDir = "./test/" -let deployDir = "./deploy/" - -// version info -let version = environVar "version" // or retrieve from CI server - - -// Targets -Target "Clean" (fun _ -> - CleanDirs [cmdDir; msBuildDir; powerShellDir; guiDir; buildDir; testDir; deployDir] -) - -Target "AssemblyInfo" (fun _ -> - CreateCSharpAssemblyInfo "./src/Pickles/VersionInfo.cs" - [Attribute.Product "Pickles" - Attribute.Company "Pickles" - Attribute.Copyright "Copyright (c) Jeffrey Cameron 2010-2012, PicklesDoc 2012-present" - Attribute.Trademark "" - Attribute.Culture "" - Attribute.ComVisible false - Attribute.Version version - Attribute.FileVersion version] -) - -Target "BuildCmd" (fun _ -> - !! "src/Pickles/Pickles.CommandLine/Pickles.CommandLine.csproj" - |> MSBuildRelease cmdDir "Build" - |> Log "AppBuild-Output: "; - - CopyFiles cmdDir [ "./LICENSE.txt"; ]; -) - -Target "BuildMsBuild" (fun _ -> - !! "src/Pickles/Pickles.MsBuild/Pickles.MsBuild.csproj" - |> MSBuildRelease msBuildDir "Build" - |> Log "AppBuild-Output: "; - - CopyFiles msBuildDir [ "./LICENSE.txt"; ]; -) - -Target "BuildPowerShell" (fun _ -> - !! "src/Pickles/Pickles.PowerShell/Pickles.PowerShell.csproj" - |> MSBuildRelease powerShellDir "Build" - |> Log "AppBuild-Output: "; - - CopyFiles powerShellDir [ "./LICENSE.txt"; ]; -) - -Target "BuildGui" (fun _ -> - !! "src/Pickles/Pickles.UserInterface/Pickles.UserInterface.csproj" - |> MSBuildRelease guiDir "Build" - |> Log "AppBuild-Output: "; - - CopyFiles guiDir [ "./LICENSE.txt"; ]; -) - -Target "BuildTest" (fun _ -> - !! "src/Pickles/Pickles.Test/Pickles.Test.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.TestFrameworks" (fun _ -> - !! "src/Pickles/Pickles.TestFrameworks.UnitTests/Pickles.TestFrameworks.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Cucumber" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Cucumber.UnitTests/Pickles.DocumentationBuilders.Cucumber.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Dhtml" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Dhtml.UnitTests/Pickles.DocumentationBuilders.Dhtml.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Excel" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Excel.UnitTests/Pickles.DocumentationBuilders.Excel.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Html" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Html.UnitTests/Pickles.DocumentationBuilders.Html.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Json" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Json.UnitTests/Pickles.DocumentationBuilders.Json.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Word" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Word.UnitTests/Pickles.DocumentationBuilders.Word.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Markdown.UnitTests" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Markdown.UnitTests/Pickles.DocumentationBuilders.Markdown.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.DocumentationBuilders.Markdown.AcceptanceTests" (fun _ -> - !! "src/Pickles/Pickles.DocumentationBuilders.Markdown.AcceptanceTests/Pickles.DocumentationBuilders.Markdown.AcceptanceTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.Runners.CommandLine" (fun _ -> - !! "src/Pickles/Pickles.CommandLine.UnitTests/Pickles.CommandLine.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -Target "BuildTest.Runners.UI" (fun _ -> - !! "src/Pickles/Pickles.UserInterface.UnitTests/Pickles.UserInterface.UnitTests.csproj" - |> MSBuildRelease testDir "Build" - |> Log "AppBuild-Output: " -) - -let createZip (packageType : string) = - !! (buildDir + "/" + packageType + "/*.*") -- "*.zip" - |> Zip (buildDir + packageType) (deployDir + "Pickles-" + packageType + "-" + version + ".zip") - -Target "Zip" (fun _ -> - createZip "exe" - createZip "gui" - createZip "msbuild" - createZip "powershell" -) - -Target "Default" (fun _ -> - trace ("Starting build of Pickles version " + version) -) - - -// Dependencies -"Clean" - ==> "AssemblyInfo" - ==> "BuildCmd" - ==> "BuildMsBuild" - ==> "BuildPowerShell" - ==> "BuildGui" - ==> "BuildTest" - ==> "BuildTest.TestFrameworks" - ==> "BuildTest.DocumentationBuilders.Cucumber" - ==> "BuildTest.DocumentationBuilders.Dhtml" - ==> "BuildTest.DocumentationBuilders.Excel" - ==> "BuildTest.DocumentationBuilders.Html" - ==> "BuildTest.DocumentationBuilders.Json" - ==> "BuildTest.DocumentationBuilders.Word" - ==> "BuildTest.DocumentationBuilders.Markdown.UnitTests" - ==> "BuildTest.DocumentationBuilders.Markdown.AcceptanceTests" - ==> "BuildTest.Runners.CommandLine" - ==> "BuildTest.Runners.UI" - ==> "Zip" - ==> "Default" - - -// start build -RunTargetOrDefault "Default" - diff --git a/build.ps1 b/build.ps1 new file mode 100644 index 000000000..1c774e525 --- /dev/null +++ b/build.ps1 @@ -0,0 +1,69 @@ +[CmdletBinding()] +Param( + [Parameter(Position=0,Mandatory=$false,ValueFromRemainingArguments=$true)] + [string[]]$BuildArguments +) + +Write-Output "PowerShell $($PSVersionTable.PSEdition) version $($PSVersionTable.PSVersion)" + +Set-StrictMode -Version 2.0; $ErrorActionPreference = "Stop"; $ConfirmPreference = "None"; trap { Write-Error $_ -ErrorAction Continue; exit 1 } +$PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent + +########################################################################### +# CONFIGURATION +########################################################################### + +$BuildProjectFile = "$PSScriptRoot\build\_build.csproj" +$TempDirectory = "$PSScriptRoot\\.nuke\temp" + +$DotNetGlobalFile = "$PSScriptRoot\\global.json" +$DotNetInstallUrl = "https://dot.net/v1/dotnet-install.ps1" +$DotNetChannel = "Current" + +$env:DOTNET_SKIP_FIRST_TIME_EXPERIENCE = 1 +$env:DOTNET_CLI_TELEMETRY_OPTOUT = 1 +$env:DOTNET_MULTILEVEL_LOOKUP = 0 + +########################################################################### +# EXECUTION +########################################################################### + +function ExecSafe([scriptblock] $cmd) { + & $cmd + if ($LASTEXITCODE) { exit $LASTEXITCODE } +} + +# If dotnet CLI is installed globally and it matches requested version, use for execution +if ($null -ne (Get-Command "dotnet" -ErrorAction SilentlyContinue) -and ` + $(dotnet --version) -and $LASTEXITCODE -eq 0) { + $env:DOTNET_EXE = (Get-Command "dotnet").Path +} +else { + # Download install script + $DotNetInstallFile = "$TempDirectory\dotnet-install.ps1" + New-Item -ItemType Directory -Path $TempDirectory -Force | Out-Null + [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 + (New-Object System.Net.WebClient).DownloadFile($DotNetInstallUrl, $DotNetInstallFile) + + # If global.json exists, load expected version + if (Test-Path $DotNetGlobalFile) { + $DotNetGlobal = $(Get-Content $DotNetGlobalFile | Out-String | ConvertFrom-Json) + if ($DotNetGlobal.PSObject.Properties["sdk"] -and $DotNetGlobal.sdk.PSObject.Properties["version"]) { + $DotNetVersion = $DotNetGlobal.sdk.version + } + } + + # Install by channel or version + $DotNetDirectory = "$TempDirectory\dotnet-win" + if (!(Test-Path variable:DotNetVersion)) { + ExecSafe { & powershell $DotNetInstallFile -InstallDir $DotNetDirectory -Channel $DotNetChannel -NoPath } + } else { + ExecSafe { & powershell $DotNetInstallFile -InstallDir $DotNetDirectory -Version $DotNetVersion -NoPath } + } + $env:DOTNET_EXE = "$DotNetDirectory\dotnet.exe" +} + +Write-Output "Microsoft (R) .NET Core SDK version $(& $env:DOTNET_EXE --version)" + +ExecSafe { & $env:DOTNET_EXE build $BuildProjectFile /nodeReuse:false /p:UseSharedCompilation=false -nologo -clp:NoSummary --verbosity quiet } +ExecSafe { & $env:DOTNET_EXE run --project $BuildProjectFile --no-build -- $BuildArguments } diff --git a/build.sh b/build.sh new file mode 100755 index 000000000..e8961f998 --- /dev/null +++ b/build.sh @@ -0,0 +1,62 @@ +#!/usr/bin/env bash + +bash --version 2>&1 | head -n 1 + +set -eo pipefail +SCRIPT_DIR=$(cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd) + +########################################################################### +# CONFIGURATION +########################################################################### + +BUILD_PROJECT_FILE="$SCRIPT_DIR/build/_build.csproj" +TEMP_DIRECTORY="$SCRIPT_DIR//.nuke/temp" + +DOTNET_GLOBAL_FILE="$SCRIPT_DIR//global.json" +DOTNET_INSTALL_URL="https://dot.net/v1/dotnet-install.sh" +DOTNET_CHANNEL="Current" + +export DOTNET_CLI_TELEMETRY_OPTOUT=1 +export DOTNET_SKIP_FIRST_TIME_EXPERIENCE=1 +export DOTNET_MULTILEVEL_LOOKUP=0 + +########################################################################### +# EXECUTION +########################################################################### + +function FirstJsonValue { + perl -nle 'print $1 if m{"'"$1"'": "([^"]+)",?}' <<< "${@:2}" +} + +# If dotnet CLI is installed globally and it matches requested version, use for execution +if [ -x "$(command -v dotnet)" ] && dotnet --version &>/dev/null; then + export DOTNET_EXE="$(command -v dotnet)" +else + # Download install script + DOTNET_INSTALL_FILE="$TEMP_DIRECTORY/dotnet-install.sh" + mkdir -p "$TEMP_DIRECTORY" + curl -Lsfo "$DOTNET_INSTALL_FILE" "$DOTNET_INSTALL_URL" + chmod +x "$DOTNET_INSTALL_FILE" + + # If global.json exists, load expected version + if [[ -f "$DOTNET_GLOBAL_FILE" ]]; then + DOTNET_VERSION=$(FirstJsonValue "version" "$(cat "$DOTNET_GLOBAL_FILE")") + if [[ "$DOTNET_VERSION" == "" ]]; then + unset DOTNET_VERSION + fi + fi + + # Install by channel or version + DOTNET_DIRECTORY="$TEMP_DIRECTORY/dotnet-unix" + if [[ -z ${DOTNET_VERSION+x} ]]; then + "$DOTNET_INSTALL_FILE" --install-dir "$DOTNET_DIRECTORY" --channel "$DOTNET_CHANNEL" --no-path + else + "$DOTNET_INSTALL_FILE" --install-dir "$DOTNET_DIRECTORY" --version "$DOTNET_VERSION" --no-path + fi + export DOTNET_EXE="$DOTNET_DIRECTORY/dotnet" +fi + +echo "Microsoft (R) .NET Core SDK version $("$DOTNET_EXE" --version)" + +"$DOTNET_EXE" build "$BUILD_PROJECT_FILE" /nodeReuse:false /p:UseSharedCompilation=false -nologo -clp:NoSummary --verbosity quiet +"$DOTNET_EXE" run --project "$BUILD_PROJECT_FILE" --no-build -- "$@" diff --git a/build.yml b/build.yml deleted file mode 100644 index 38e8281ce..000000000 --- a/build.yml +++ /dev/null @@ -1,5 +0,0 @@ -name: build-pickles -on: [push] -jobs: - run-bat: - runs-on: windows-latest diff --git a/build/.editorconfig b/build/.editorconfig new file mode 100644 index 000000000..31e43dcd8 --- /dev/null +++ b/build/.editorconfig @@ -0,0 +1,11 @@ +[*.cs] +dotnet_style_qualification_for_field = false:warning +dotnet_style_qualification_for_property = false:warning +dotnet_style_qualification_for_method = false:warning +dotnet_style_qualification_for_event = false:warning +dotnet_style_require_accessibility_modifiers = never:warning + +csharp_style_expression_bodied_methods = true:silent +csharp_style_expression_bodied_properties = true:warning +csharp_style_expression_bodied_indexers = true:warning +csharp_style_expression_bodied_accessors = true:warning diff --git a/build/Build.cs b/build/Build.cs new file mode 100644 index 000000000..5670296fe --- /dev/null +++ b/build/Build.cs @@ -0,0 +1,342 @@ +using System; +using System.Collections.Generic; +using System.Diagnostics; +using System.IO; +using System.IO.Compression; +using System.Linq; +using System.Runtime.InteropServices; +using Microsoft.Extensions.Configuration; +using Nuke.Common; +using Nuke.Common.CI; +using Nuke.Common.Execution; +using Nuke.Common.Git; +using Nuke.Common.IO; +using Nuke.Common.ProjectModel; +using Nuke.Common.Tooling; +using Nuke.Common.Tools.DotNet; +using Nuke.Common.Tools.NuGet; +using Nuke.Common.Utilities.Collections; +using static Nuke.Common.IO.FileSystemTasks; +using static Nuke.Common.Tools.DotNet.DotNetTasks; + +[CheckBuildProjectConfigurations] +[ShutdownDotNetAfterServerBuild] +class Build : NukeBuild +{ + public static int Main() + { + if (IsLocalBuild) + { + config = new ConfigurationBuilder() + .SetBasePath(AppDomain.CurrentDomain.BaseDirectory) + .AddUserSecrets() + .Build(); + } + + return Execute(x => x.PublishNuGet); + } + + [Parameter("Configuration to build - Default is 'Debug' (local) or 'Release' (server)")] + //readonly Configuration Configuration = IsLocalBuild ? Configuration.Debug : Configuration.Release; + readonly Configuration Configuration = Configuration.Release; + + static IConfiguration config; + [Solution] readonly Solution Solution; + + AbsolutePath SourceDirectory => RootDirectory / "src"; + AbsolutePath ArtifactsDirectory => RootDirectory / "artifacts"; + AbsolutePath PublishDirectory => ArtifactsDirectory / "publish"; + AbsolutePath CommandLineDirectory => PublishDirectory / "exe"; + AbsolutePath MsBuildDirectory => PublishDirectory / "msbuild"; + AbsolutePath PowerShellDirectory => PublishDirectory / "powershell"; + AbsolutePath DeployDirectory => ArtifactsDirectory / "deploy"; + + AbsolutePath OutputDirectory => RootDirectory / "Output"; + AbsolutePath DocsOutputDirectory => RootDirectory/ "docs" / "Output"; + + String AssemblyProduct = "Pickles"; + String AssemblyCompany = "Pickles"; + String Version = "3.0.1"; + String Copyright = "Copyright (c) Jeffrey Cameron 2010-2012, PicklesDoc 2012-present"; + String NuGetApiKey = ""; + + Target Clean => _ => _ + .Before(Test) + .Executes(() => + { + SourceDirectory.GlobDirectories("**/bin", "**/obj").ForEach(DeleteDirectory); + EnsureCleanDirectory(ArtifactsDirectory); + EnsureCleanDirectory(DeployDirectory); + EnsureCleanDirectory(DeployDirectory / "zip"); + EnsureCleanDirectory(DeployDirectory / "nuget"); + EnsureCleanDirectory(OutputDirectory); + EnsureCleanDirectory(DocsOutputDirectory); + }); + + Target Test => _ => _ + .DependsOn(Clean) + .Executes(() => + { + DotNetTest(s => s + .SetProjectFile(RootDirectory / "src" / "Pickles" / "Pickles.sln") + .SetLoggers("trx;LogFileName=TestResults.xml") + ); + }); + + Target Publish => _ => _ + .DependsOn(Test) + .Executes(() => + { + var publishCombinations = + from runtime in new[] {"win10-x86", "osx-x64", "linux-x64"} + select new {runtime}; + + DotNetPublish(p => p + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine") + .SetConfiguration(Configuration) + .SetVersion(Version) + .CombineWith(publishCombinations, (s, v) => s + .SetRuntime(v.runtime) + .SetOutput(CommandLineDirectory / v.runtime) + ) + ); + + DotNetPublish(p => p + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.MsBuild") + .SetConfiguration(Configuration) + .SetVersion(Version) + .CombineWith(publishCombinations, (s, v) => s + .SetRuntime(v.runtime) + .SetOutput(MsBuildDirectory / v.runtime) + ) + ); + + DotNetPublish(p => p + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.PowerShell") + .SetConfiguration(Configuration) + .SetVersion(Version) + .CombineWith(publishCombinations, (s, v) => s + .SetRuntime(v.runtime) + .SetOutput(PowerShellDirectory / v.runtime) + ) + ); + + foreach (var p in publishCombinations) + { + ZipFile.CreateFromDirectory(CommandLineDirectory / p.runtime, + DeployDirectory / "zip" / "Pickles-exe-" + p.runtime + "-" + Version + ".zip"); + ZipFile.CreateFromDirectory(MsBuildDirectory / p.runtime, + DeployDirectory / "zip" / "Pickles-msbuild-" + p.runtime + "-" + Version + ".zip"); + ZipFile.CreateFromDirectory(PowerShellDirectory / p.runtime, + DeployDirectory / "zip" / "Pickles-powershell-" + p.runtime + "-" + Version + ".zip"); + } + }); + + Target GenerateSampleOutput => _ => _ + .DependsOn(Publish) + .Executes(() => + { + string runtime = String.Empty; + var formats = new List {"Html", "Dhtml", "Word", "Excel", "JSON", "Cucumber", "Markdown"}; + string exampleSource = SourceDirectory / "Pickles" / "Examples"; + string outputFolder = string.Empty; + + bool isMac = RuntimeInformation.IsOSPlatform(OSPlatform.OSX); + bool isWindows = RuntimeInformation.IsOSPlatform(OSPlatform.Windows); + bool isLinux = RuntimeInformation.IsOSPlatform(OSPlatform.Linux); + + if (isMac) + { + runtime = "osx-x64"; + } + else if (isWindows) + { + runtime = "win10-x86"; + } + else if (isLinux) + { + runtime = "linux-x64"; + } + + foreach (var format in formats) + { + outputFolder = OutputDirectory / format; + + ProcessStartInfo processStartInfo = + new ProcessStartInfo(PublishDirectory / "exe" / runtime / "Pickles", + $"-f={exampleSource} -o={outputFolder} -df={format} --sn=Pickles --sv={Version}"); + + processStartInfo.CreateNoWindow = false; + processStartInfo.UseShellExecute = false; + Process p = Process.Start(processStartInfo); + p.WaitForExit(); + Console.WriteLine(p.ExitCode); + + //TODO Repeat with experimental features + //TODO Repeat with other runners + } + + //Copy sample output to docs folder + CopyFilesRecursively(new DirectoryInfo(RootDirectory / "Output"), + new DirectoryInfo(RootDirectory / "docs" / "Output")); + + //Update version in docs index + var index = File.ReadAllText(RootDirectory / "docs" / "index_template.html"); + index = index.Replace("VERSION_PLACEHOLDER", Version); + File.WriteAllText(RootDirectory / "docs" / "index.html", index); + }); + + public static void CopyFilesRecursively(DirectoryInfo source, DirectoryInfo target) + { + foreach (DirectoryInfo dir in source.GetDirectories()) + CopyFilesRecursively(dir, target.CreateSubdirectory(dir.Name)); + foreach (FileInfo file in source.GetFiles()) + file.CopyTo(Path.Combine(target.FullName, file.Name)); + } + + Target Pack => _ => _ + .DependsOn(GenerateSampleOutput) + .Executes(() => + { + var commandLineProject = File.ReadAllText(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / + "Pickles.CommandLine.csproj"); + + //Setting PackageId via the dotnet pack command sets the id for all referenced projects and + //throws the "ambiguous project name" error. Duplicating the project file is a temporary hack + //till this gets fixed. + var clPackage = commandLineProject.Replace("PACKAGE_ID", "Pickles.CommandLine"); + File.WriteAllText( + RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.cl.csproj", clPackage); + + DotNetPack(s => s + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / + "Pickles.CommandLine.cl.csproj") + .SetConfiguration(Configuration) + .SetProperty("Version", Version) + .SetRuntime("win10-x86") + .SetOutputDirectory(DeployDirectory / "nuget") + + //.SetCopyright(Copyright) + ); + + File.Delete(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.cl.csproj"); + + var winPackage = commandLineProject.Replace("PACKAGE_ID", "Pickles.CommandLine.win"); + File.WriteAllText( + RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.win.csproj", winPackage); + + DotNetPack(s => s + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / + "Pickles.CommandLine.win.csproj") + .SetConfiguration(Configuration) + .SetProperty("Version", Version) + //.SetProperty("NuspecFile", "") + .SetRuntime("win10-x86") + .SetOutputDirectory(DeployDirectory / "nuget") + //.SetCopyright(Copyright) + ); + + File.Delete(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.win.csproj"); + + var macPackage = commandLineProject.Replace("PACKAGE_ID", "Pickles.CommandLine.mac"); + File.WriteAllText( + RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.mac.csproj", macPackage); + + DotNetPack(s => s + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / + "Pickles.CommandLine.mac.csproj") + .SetConfiguration(Configuration) + .SetProperty("Version", Version) + .SetRuntime("osx-x64") + .SetOutputDirectory(DeployDirectory / "nuget") + + //.SetCopyright(Copyright) + ); + + File.Delete(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.mac.csproj"); + + var linuxPackage = commandLineProject.Replace("PACKAGE_ID", "Pickles.CommandLine.linux"); + File.WriteAllText( + RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.linux.csproj", linuxPackage); + + DotNetPack(s => s + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / + "Pickles.CommandLine.linux.csproj") + .SetConfiguration(Configuration) + .SetProperty("Version", Version) + .SetRuntime("linux-x64") + .SetOutputDirectory(DeployDirectory / "nuget") + + //.SetCopyright(Copyright) + ); + + File.Delete(RootDirectory / "src" / "Pickles" / "Pickles.CommandLine" / "Pickles.CommandLine.linux.csproj"); + + //TODO Create MsBuild nuget package + // DotNetPack(s => s + // .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.MsBuild" / "Pickles.MsBuild.csproj") + // .SetConfiguration(Configuration) + // .SetRuntime("win10-x86") + // .SetProperty("Version", Version) + // .SetOutputDirectory(DeployDirectory / "nuget") + // //.SetCopyright(Copyright) + // ); + + DotNetPack(s => s + .SetProject(RootDirectory / "src" / "Pickles" / "Pickles.PowerShell" / + "Pickles.PowerShell.csproj") + .SetConfiguration(Configuration) + .SetRuntime("win10-x86") + .SetProperty("Version", Version) + .SetOutputDirectory(DeployDirectory / "nuget") + //.SetCopyright(Copyright) + ); + }); + + Target PublishNuGet => _ => _ + .DependsOn(Pack) + .Executes(() => + { + if (IsLocalBuild) + { + NuGetApiKey = config["NugetApiKey"]; + } + + NuGetTasks.NuGetPush(s => s + .SetSource("https://www.nuget.org/api/v2/package") + .SetApiKey(NuGetApiKey) + .SetTargetPath(DeployDirectory / "nuget" / $"Pickles.{Version}.nupkg") + ); + + NuGetTasks.NuGetPush(s => s + .SetSource("https://www.nuget.org/api/v2/package") + .SetApiKey(NuGetApiKey) + .SetTargetPath(DeployDirectory / "nuget" / $"Pickles.CommandLine.{Version}.nupkg") + ); + + NuGetTasks.NuGetPush(s => s + .SetSource("https://www.nuget.org/api/v2/package") + .SetApiKey(NuGetApiKey) + .SetTargetPath(DeployDirectory / "nuget" / $"Pickles.CommandLine.win.{Version}.nupkg") + ); + + NuGetTasks.NuGetPush(s => s + .SetSource("https://www.nuget.org/api/v2/package") + .SetApiKey(NuGetApiKey) + .SetTargetPath(DeployDirectory / "nuget" / $"Pickles.CommandLine.mac.{Version}.nupkg") + ); + + NuGetTasks.NuGetPush(s => s + .SetSource("https://www.nuget.org/api/v2/package") + .SetApiKey(NuGetApiKey) + .SetTargetPath(DeployDirectory / "nuget" / $"Pickles.CommandLine.linux.{Version}.nupkg") + ); + + // NuGetTasks.NuGetPush(s => s + // .SetSource("https://www.nuget.org/api/v2/package") + // .SetApiKey(NuGetApiKey) + // .SetTargetPath(DeployDirectory / "nuget" / $"Pickles.MsBuild.{Version}.nupkg") + // ); + }); +} + diff --git a/build/Configuration.cs b/build/Configuration.cs new file mode 100644 index 000000000..9c08b1ae9 --- /dev/null +++ b/build/Configuration.cs @@ -0,0 +1,16 @@ +using System; +using System.ComponentModel; +using System.Linq; +using Nuke.Common.Tooling; + +[TypeConverter(typeof(TypeConverter))] +public class Configuration : Enumeration +{ + public static Configuration Debug = new Configuration { Value = nameof(Debug) }; + public static Configuration Release = new Configuration { Value = nameof(Release) }; + + public static implicit operator string(Configuration configuration) + { + return configuration.Value; + } +} diff --git a/build/Directory.Build.props b/build/Directory.Build.props new file mode 100644 index 000000000..e147d6352 --- /dev/null +++ b/build/Directory.Build.props @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/build/Directory.Build.targets b/build/Directory.Build.targets new file mode 100644 index 000000000..253260956 --- /dev/null +++ b/build/Directory.Build.targets @@ -0,0 +1,8 @@ + + + + + + + + diff --git a/build/_build.csproj b/build/_build.csproj new file mode 100644 index 000000000..a9a4ccf5b --- /dev/null +++ b/build/_build.csproj @@ -0,0 +1,26 @@ + + + + Exe + net5.0 + + CS0649;CS0169 + .. + .. + 1 + e07f83f3-1c7c-480c-9443-a8ad1bfc6b83 + + + + + + + + + + + + + + + diff --git a/build/_build.csproj.DotSettings b/build/_build.csproj.DotSettings new file mode 100644 index 000000000..7bc28484c --- /dev/null +++ b/build/_build.csproj.DotSettings @@ -0,0 +1,27 @@ + + DO_NOT_SHOW + DO_NOT_SHOW + DO_NOT_SHOW + DO_NOT_SHOW + Implicit + Implicit + ExpressionBody + 0 + NEXT_LINE + True + False + 120 + IF_OWNER_IS_SINGLE_LINE + WRAP_IF_LONG + False + <Policy Inspect="True" Prefix="" Suffix="" Style="AaBb" /> + <Policy Inspect="True" Prefix="" Suffix="" Style="AaBb" /> + True + True + True + True + True + True + True + True + True diff --git a/chocolatey.fsx b/chocolatey.fsx deleted file mode 100644 index 9e48166f5..000000000 --- a/chocolatey.fsx +++ /dev/null @@ -1,125 +0,0 @@ -// include Fake lib -#r @"packages\FAKE\tools\FakeLib.dll" -open Fake - -// Properties -let cmdDir = "./build/exe/" -let guiDir = "./build/gui/" -let deployDir = "./deploy/chocolatey/" -let packagingDir = "./packaging/" -let chocoDir = "./chocolatey/" - -// version info -let version = environVar "version" // or retrieve from CI server - -Target "Clean" (fun _ -> - CleanDirs [deployDir; packagingDir] -) - - -Target "CreatePackage CMD" (fun _ -> - CopyFiles packagingDir [ - cmdDir + "Autofac.dll"; - cmdDir + "ClosedXML.dll"; - cmdDir + "DocumentFormat.OpenXml.dll"; - cmdDir + "Gherkin.dll"; - cmdDir + "MarkdownDeep.dll"; - cmdDir + "NDesk.Options.dll"; - cmdDir + "Newtonsoft.Json.dll"; - cmdDir + "NLog.dll"; - cmdDir + "PicklesDoc.Pickles.Library.dll"; - cmdDir + "PicklesDoc.Pickles.ObjectModel.dll"; - cmdDir + "PicklesDoc.Pickles.TestFrameworks.dll"; - cmdDir + "PicklesDoc.Pickles.DocumentationBuilders.Cucumber.dll"; - cmdDir + "PicklesDoc.Pickles.DocumentationBuilders.Word.dll"; - cmdDir + "PicklesDoc.Pickles.DocumentationBuilders.Excel.dll"; - cmdDir + "PicklesDoc.Pickles.DocumentationBuilders.Json.dll"; - cmdDir + "PicklesDoc.Pickles.DocumentationBuilders.Html.dll"; - cmdDir + "PicklesDoc.Pickles.DocumentationBuilders.Dhtml.dll"; - cmdDir + "PicklesDoc.Pickles.DocumentationBuilders.Markdown.dll"; - cmdDir + "System.IO.Abstractions.dll"; - cmdDir + "FeatureSwitcher.dll"; - cmdDir + "Strike.Jint.dll"; - cmdDir + "Jint.dll"; - cmdDir + "pickles.exe"; - cmdDir + "NLog.config"; - "./LICENSE.txt"; - "./VERIFICATION.txt";] - - WriteFile (packagingDir + "version.ps1") [("$version = \"" + version + "\"")] - NuGet (fun p -> - {p with - OutputPath = deployDir - WorkingDir = packagingDir - Version = version - Publish = false }) - (chocoDir + "Pickles.nuspec") -) - - -Target "CreatePackage GUI" (fun _ -> - CopyFiles packagingDir [ - guiDir + "Autofac.dll"; - guiDir + "ClosedXML.dll"; - guiDir + "DocumentFormat.OpenXml.dll"; - guiDir + "GalaSoft.MvvmLight.dll"; - guiDir + "GalaSoft.MvvmLight.Extras.dll"; - guiDir + "GalaSoft.MvvmLight.Platform.dll"; - guiDir + "Gherkin.dll"; - guiDir + "MahApps.Metro.dll"; - guiDir + "MarkdownDeep.dll"; - guiDir + "CommonServiceLocator.dll"; - guiDir + "ControlzEx.dll"; - guiDir + "Newtonsoft.Json.dll"; - guiDir + "NLog.dll"; - guiDir + "NlogViewer.dll"; - guiDir + "Ookii.Dialogs.Wpf.dll"; - guiDir + "PicklesDoc.Pickles.Library.dll"; - guiDir + "PicklesDoc.Pickles.ObjectModel.dll"; - guiDir + "PicklesDoc.Pickles.TestFrameworks.dll"; - guiDir + "PicklesDoc.Pickles.DocumentationBuilders.Cucumber.dll"; - guiDir + "PicklesDoc.Pickles.DocumentationBuilders.Word.dll"; - guiDir + "PicklesDoc.Pickles.DocumentationBuilders.Excel.dll"; - guiDir + "PicklesDoc.Pickles.DocumentationBuilders.Json.dll"; - guiDir + "PicklesDoc.Pickles.DocumentationBuilders.Html.dll"; - guiDir + "PicklesDoc.Pickles.DocumentationBuilders.Dhtml.dll"; - guiDir + "PicklesDoc.Pickles.DocumentationBuilders.Markdown.dll"; - guiDir + "System.IO.Abstractions.dll"; - guiDir + "FeatureSwitcher.dll"; - guiDir + "Strike.Jint.dll"; - guiDir + "Jint.dll"; - guiDir + "System.Windows.Interactivity.dll"; - guiDir + "picklesui.exe"; - guiDir + "NLog.config"; - guiDir + "PicklesUI.exe.config"; - "./LICENSE.txt"; - "./VERIFICATION.txt";] - - WriteFile (packagingDir + "version.ps1") [("$version = \"" + version + "\"")] - WriteFile (packagingDir + "picklesui.exe.gui") [("")] - NuGet (fun p -> - {p with - OutputPath = deployDir - WorkingDir = packagingDir - Version = version - Publish = false }) - (chocoDir + "picklesui.nuspec") -) - - -Target "Default" (fun _ -> - trace ("Starting build of Pickles version " + version) - DeleteDir packagingDir -) - - -// Dependencies -"Clean" - ==> "CreatePackage CMD" - ==> "CreatePackage GUI" - ==> "Default" - - -// start build -RunTargetOrDefault "Default" - diff --git a/chocolatey/pickles.nuspec b/chocolatey/pickles.nuspec deleted file mode 100644 index 3dfd2798c..000000000 --- a/chocolatey/pickles.nuspec +++ /dev/null @@ -1,67 +0,0 @@ - - - - pickles - Pickles - The Open Source Living Documentation Generator - @build.number@ - PicklesDoc and contributors - Jeffrey Cameron, Dirk Rombauts - A documentation generator for features written in the Gherkin language - **Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. - -*Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. - -*Pickles* can produce output in different formats: - -- Static HTML: a set of HTML files with minimal JavaScript -- Dynamic HTML: a JavaScript-rich single page app with integrated search -- Word: Microsoft Word -- Excel: Microsoft Excel -- JSON: a custom JSON format -- Markdown: a simple output format - -Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - -- NUnit -- MSTest -- XUnit -- SpecRun -- Cucumber JSON - - http://www.picklesdoc.com/ - SpecificationByExample BDD SpecFlow Gherkin Cucumber SpecByEx LivingDocumentation Documentation - Copyright © 2010-2012 Jeffrey Cameron, Copyright © 2013-present PicklesDoc and contributors - http://apache.org/licenses/LICENSE-2.0.html - false - https://cdn.rawgit.com/picklesdoc/pickles/master/pickles.png - https://github.com/picklesdoc/pickles/blob/master/CHANGELOG.md - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/chocolatey/picklesui.nuspec b/chocolatey/picklesui.nuspec deleted file mode 100644 index 87733f5e1..000000000 --- a/chocolatey/picklesui.nuspec +++ /dev/null @@ -1,78 +0,0 @@ - - - - picklesui - Pickles UI - The Open Source Living Documentation Generator (GUI) - @build.number@ - PicklesDoc and contributors - Jeffrey Cameron, Dirk Rombauts - A documentation generator for features written in the Gherkin language - **Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. - -This GUI version of Pickles provides an easy way to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. - -*Pickles* can produce output in different formats: - -- Static HTML: a set of HTML files with minimal JavaScript -- Dynamic HTML: a JavaScript-rich single page app with integrated search -- Word: Microsoft Word -- Excel: Microsoft Excel -- JSON: a custom JSON format -- Markdown: a simple output format - -Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - -- NUnit -- MSTest -- XUnit -- SpecRun -- Cucumber JSON - - http://www.picklesdoc.com/ - SpecificationByExample BDD SpecFlow Gherkin Cucumber SpecByEx LivingDocumentation Documentation - Copyright © 2010-2012 Jeffrey Cameron, Copyright © 2013-present PicklesDoc and contributors - http://apache.org/licenses/LICENSE-2.0.html - false - https://cdn.rawgit.com/picklesdoc/pickles/master/pickles.png - https://github.com/picklesdoc/pickles/blob/master/CHANGELOG.md - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/Output/Cucumber/cucumberResult.json b/docs/Output/Cucumber/cucumberResult.json index 0ec000752..74bef325a 100644 --- a/docs/Output/Cucumber/cucumberResult.json +++ b/docs/Output/Cucumber/cucumberResult.json @@ -1,11 +1,14 @@ [ { + "id": "showing-basic-gherkin-syntax", "keyword": "Feature", "name": "Showing basic gherkin syntax", + "uri": "Features/00BasicGherkin/BasicGherkin.feature", "tags": [], "line": 1, "elements": [ { + "id": "showing-basic-gherkin-syntax;simple-gwt", "keyword": "Scenario", "name": "Simple GWT", "line": 8, @@ -16,8 +19,9 @@ "keyword": "Given", "name": "the initial state of the application is Running", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -25,8 +29,9 @@ "keyword": "When", "name": "I ask what the application state is", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -34,14 +39,16 @@ "keyword": "Then", "name": "I should see Running as the answer", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-basic-gherkin-syntax;using-and-and-but", "keyword": "Scenario", "name": "Using And and But", "line": 13, @@ -52,8 +59,9 @@ "keyword": "Given", "name": "the initial state of the application is Running", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -61,8 +69,9 @@ "keyword": "And", "name": "I have authorization to ask application state", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -70,8 +79,9 @@ "keyword": "When", "name": "I ask what the application state is", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -79,8 +89,9 @@ "keyword": "Then", "name": "I should see Running as the answer", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -88,8 +99,9 @@ "keyword": "And", "name": "I should see the time of the application", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -97,8 +109,9 @@ "keyword": "But", "name": "the state of the application should not be Stopped", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -107,12 +120,15 @@ ] }, { + "id": "the-test-runner-is-not-very-important", "keyword": "Feature", "name": "The test runner is not (very) important", + "uri": "Features/01TestRunner/TestRunnerIsNotImportant.feature", "tags": [], "line": 1, "elements": [ { + "id": "the-test-runner-is-not-very-important;a-couple-of-simple-steps", "keyword": "Scenario", "name": "A couple of simple steps", "line": 6, @@ -123,8 +139,9 @@ "keyword": "Given", "name": "I have step defintions in place", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -132,8 +149,9 @@ "keyword": "When", "name": "I call a step", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -141,8 +159,9 @@ "keyword": "Then", "name": "the step should have been called", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -151,12 +170,15 @@ ] }, { + "id": "addition", "keyword": "Feature", "name": "Addition", + "uri": "Features/02TagsAndHooks/Hooks.feature", "tags": [], "line": 1, "elements": [ { + "id": "addition;hooking-into-pre-conditions-for-test-runs-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Test Runs in SpecFlow", "line": 6, @@ -167,8 +189,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -176,14 +199,16 @@ "keyword": "Then", "name": "the BeforeTestRun hook should have been executed", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-features-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Features in SpecFlow", "line": 10, @@ -194,8 +219,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -203,14 +229,16 @@ "keyword": "Then", "name": "the BeforeFeature hook should have been executed", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-scenarios-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Scenarios in SpecFlow", "line": 14, @@ -221,8 +249,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -230,14 +259,16 @@ "keyword": "Then", "name": "the BeforeScenario hook should have been executed", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-scenarioblocks-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for ScenarioBlocks in SpecFlow", "line": 18, @@ -248,8 +279,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -257,14 +289,16 @@ "keyword": "Then", "name": "the BeforeScenarioBlock hook should have been executed", "line": 20, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "addition;hooking-into-pre-conditions-for-steps-in-specflow", "keyword": "Scenario", "name": "Hooking into pre conditions for Steps in SpecFlow", "line": 22, @@ -275,8 +309,9 @@ "keyword": "Given", "name": "the scenario is running", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -284,8 +319,9 @@ "keyword": "Then", "name": "the BeforeStep hook should have been executed", "line": 24, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -294,8 +330,10 @@ ] }, { + "id": "tag-demonstrator", "keyword": "Feature", "name": "Tag demonstrator", + "uri": "Features/02TagsAndHooks/TagDemo.feature", "tags": [ { "name": "@allAboutTags" @@ -307,6 +345,7 @@ "line": 1, "elements": [ { + "id": "tag-demonstrator;ignored-scenario", "keyword": "Scenario", "name": "Ignored scenario", "line": 8, @@ -321,8 +360,9 @@ "keyword": "Given", "name": "that my scenario has the @ignore tag", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -330,8 +370,9 @@ "keyword": "When", "name": "I run the scenario", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -339,8 +380,9 @@ "keyword": "Then", "name": "the scenario is ignored", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -348,14 +390,16 @@ "keyword": "And", "name": "the missing step definitions are not reported", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-without-tags", "keyword": "Scenario", "name": "A scenario without tags", "line": 14, @@ -366,8 +410,9 @@ "keyword": "Given", "name": "that my scenario has 0 tags", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -375,8 +420,9 @@ "keyword": "When", "name": "I run the scenario", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -384,14 +430,16 @@ "keyword": "Then", "name": "before scenario hook with '' is run", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-with-1-tag", "keyword": "Scenario", "name": "A scenario with 1 tag", "line": 20, @@ -406,8 +454,9 @@ "keyword": "Given", "name": "that my scenario has 1 tags", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -415,8 +464,9 @@ "keyword": "When", "name": "I run the scenario", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -424,14 +474,16 @@ "keyword": "Then", "name": "before scenario hook with 'testTag1' is run", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-with-3-tags", "keyword": "Scenario", "name": "A scenario with 3 tags", "line": 26, @@ -452,8 +504,9 @@ "keyword": "Given", "name": "that my scenario has 3 tags", "line": 27, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -461,8 +514,9 @@ "keyword": "When", "name": "I run the scenario", "line": 28, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -470,14 +524,16 @@ "keyword": "Then", "name": "before scenario hook with 'testTag1, testTag2, testTag3' is run", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "tag-demonstrator;a-scenario-with-2-tags", "keyword": "Scenario", "name": "A scenario with 2 tags", "line": 32, @@ -495,8 +551,9 @@ "keyword": "Given", "name": "that my scenario has 2 tags", "line": 33, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -504,8 +561,9 @@ "keyword": "When", "name": "I run the scenario", "line": 34, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -513,8 +571,9 @@ "keyword": "Then", "name": "before scenario hook with 'testTag1, testTag3' is run", "line": 35, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -523,24 +582,28 @@ ] }, { + "id": "scenario-outline", "keyword": "Feature", "name": "Scenario outline", + "uri": "Features/03ScenarioOutline/ScenarioOutline.feature", "tags": [], "line": 1, "elements": [ { - "keyword": "Scenario Outline", + "id": "scenario-outline;add-two-positive-numbers-with-many-examples", + "keyword": "Scenario", "name": "Add two positive numbers with many examples", "line": 8, - "type": "scenario_outline", + "type": "scenario", "tags": [], "steps": [ { "keyword": "Given", "name": "I enter into the calculator", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -548,8 +611,9 @@ "keyword": "And", "name": "I enter into the calculator", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -557,8 +621,9 @@ "keyword": "When", "name": "I perform add", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -566,26 +631,29 @@ "keyword": "Then", "name": "the result should be ", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { - "keyword": "Scenario Outline", + "id": "scenario-outline;add-two-negative-numbers-with-many-examples", + "keyword": "Scenario", "name": "Add two negative numbers with many examples", "line": 28, - "type": "scenario_outline", + "type": "scenario", "tags": [], "steps": [ { "keyword": "Given", "name": "I enter into the calculator", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -593,8 +661,9 @@ "keyword": "And", "name": "I enter into the calculator", "line": 30, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -602,8 +671,9 @@ "keyword": "When", "name": "I perform add", "line": 31, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -611,8 +681,9 @@ "keyword": "Then", "name": "the result should be ", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -621,12 +692,15 @@ ] }, { + "id": "scenario-context-features", "keyword": "Feature", "name": "Scenario Context features", + "uri": "Features/031ScenarioContext/ScenarioContext.feature", "tags": [], "line": 1, "elements": [ { + "id": "scenario-context-features;store-and-retrive-person-marcus-from-scenariocontext", "keyword": "Scenario", "name": "Store and retrive Person Marcus from ScenarioContext", "line": 6, @@ -637,8 +711,9 @@ "keyword": "When", "name": "I store a person called Marcus in the Current ScenarioContext", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -646,14 +721,16 @@ "keyword": "Then", "name": "a person called Marcus can easily be retrieved", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;showing-information-of-the-scenario", "keyword": "Scenario", "name": "Showing information of the scenario", "line": 11, @@ -671,8 +748,9 @@ "keyword": "When", "name": "I execute any scenario", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -680,14 +758,16 @@ "keyword": "Then", "name": "the ScenarioInfo contains the following information", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;show-the-type-of-step-were-currently-on", "keyword": "Scenario", "name": "Show the type of step we're currently on", "line": 18, @@ -698,8 +778,9 @@ "keyword": "Given", "name": "I have a Given step", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -707,8 +788,9 @@ "keyword": "And", "name": "I have another Given step", "line": 20, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -716,8 +798,9 @@ "keyword": "When", "name": "I have a When step", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -725,14 +808,16 @@ "keyword": "Then", "name": "I have a Then step", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;display-error-information-in-afterscenario", "keyword": "Scenario", "name": "Display error information in AfterScenario", "line": 27, @@ -750,14 +835,16 @@ "keyword": "When", "name": "an error occurs in a step", "line": 28, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "scenario-context-features;pending-step", "keyword": "Scenario", "name": "Pending step", "line": 30, @@ -768,8 +855,9 @@ "keyword": "When", "name": "I set the ScenarioContext.Current to pending", "line": 31, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -777,8 +865,9 @@ "keyword": "Then", "name": "this step will not even be executed", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -787,8 +876,10 @@ ] }, { + "id": "featurecontext-features", "keyword": "Feature", "name": "FeatureContext features", + "uri": "Features/032FeatureContext/FeatureContextFeatures.feature", "tags": [ { "name": "@showUpInScenarioInfo" @@ -800,6 +891,7 @@ "line": 1, "elements": [ { + "id": "featurecontext-features;store-and-retrive-person-marcus-from-featurecontext-current", "keyword": "Scenario", "name": "Store and retrive Person Marcus from FeatureContext Current", "line": 7, @@ -810,8 +902,9 @@ "keyword": "When", "name": "I store a person called Marcus in the current FeatureContext", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -819,14 +912,16 @@ "keyword": "Then", "name": "a person called Marcus can easily be retrieved from the current FeatureContext", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "featurecontext-features;showing-information-of-the-feature", "keyword": "Scenario", "name": "Showing information of the feature", "line": 11, @@ -837,8 +932,9 @@ "keyword": "When", "name": "I execute any scenario in the feature", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -846,8 +942,9 @@ "keyword": "Then", "name": "the FeatureInfo contains the following information", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -856,12 +953,15 @@ ] }, { + "id": "show-the-use-of-background", "keyword": "Feature", "name": "Show the use of background", + "uri": "Features/04Background/BackgroundFeature.feature", "tags": [], "line": 1, "elements": [ { + "id": "show-the-use-of-background;add-1-to-the-sum", "keyword": "Scenario", "name": "Add 1 to the sum", "line": 10, @@ -872,8 +972,9 @@ "keyword": "When", "name": "I add 1 to the Sum-variable", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -881,14 +982,16 @@ "keyword": "Then", "name": "the total sum should be 2", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "show-the-use-of-background;add-2-to-the-sum", "keyword": "Scenario", "name": "Add 2 to the sum", "line": 14, @@ -899,8 +1002,9 @@ "keyword": "When", "name": "I add 2 to the Sum-variable", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -908,8 +1012,9 @@ "keyword": "Then", "name": "the total sum should be 3", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -918,12 +1023,15 @@ ] }, { + "id": "showing-table-usage", "keyword": "Feature", "name": "Showing table usage", + "uri": "Features/05TablesAndAssist/TableScenario.feature", "tags": [], "line": 1, "elements": [ { + "id": "showing-table-usage;using-tables", "keyword": "Scenario", "name": "Using tables", "line": 6, @@ -934,8 +1042,9 @@ "keyword": "Given", "name": "I have the following persons", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -943,8 +1052,9 @@ "keyword": "When", "name": "I search for Jocke", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -952,14 +1062,16 @@ "keyword": "Then", "name": "the following person should be returned", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-table-usage;using-tables-with-specflow-assist", "keyword": "Scenario", "name": "Using tables with SpecFlow Assist", "line": 17, @@ -970,8 +1082,9 @@ "keyword": "Given", "name": "I have the following persons using assist", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -979,8 +1092,9 @@ "keyword": "When", "name": "I search for Jocke", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -988,14 +1102,16 @@ "keyword": "Then", "name": "the following person should be returned using assist", "line": 24, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-table-usage;creating-a-entity-from-field-value", "keyword": "Scenario", "name": "Creating a entity from field value", "line": 28, @@ -1006,8 +1122,9 @@ "keyword": "When", "name": "I fill out the form like this", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1015,14 +1132,16 @@ "keyword": "Then", "name": "the following person should be returned using assist", "line": 35, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "showing-table-usage;example-of-a-wide-table", "keyword": "Scenario", "name": "Example of a wide table", "line": 39, @@ -1033,8 +1152,9 @@ "keyword": "Given", "name": "this wide table", "line": 40, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1043,12 +1163,15 @@ ] }, { + "id": "show-the-compare-to-feature", "keyword": "Feature", "name": "Show the compare to feature", + "uri": "Features/06CompareToAssist/CompareTo.feature", "tags": [], "line": 1, "elements": [ { + "id": "show-the-compare-to-feature;comparetoinstance", "keyword": "Scenario", "name": "CompareToInstance", "line": 8, @@ -1059,8 +1182,9 @@ "keyword": "Given", "name": "I have the following person", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1068,8 +1192,9 @@ "keyword": "Then", "name": "CompareToInstance should match this guy", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1077,8 +1202,9 @@ "keyword": "And", "name": "CompareToInstance should match this guy", "line": 19, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1086,14 +1212,16 @@ "keyword": "But", "name": "CompareToInstance should not match this guy", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "show-the-compare-to-feature;comparetoset", "keyword": "Scenario", "name": "CompareToSet", "line": 31, @@ -1104,8 +1232,9 @@ "keyword": "Given", "name": "I have the following persons using assist", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1113,8 +1242,9 @@ "keyword": "Then", "name": "CompareToSet should match this", "line": 37, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1122,8 +1252,9 @@ "keyword": "But", "name": "CompareToSet should not match this", "line": 42, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1132,12 +1263,15 @@ ] }, { + "id": "svenska---summering", "keyword": "Feature", "name": "Svenska - Summering", + "uri": "Features/07Localization/Svenska.feature", "tags": [], "line": 1, "elements": [ { + "id": "svenska---summering;summera-5-och-7-ska-vara-12", "keyword": "Scenario", "name": "Summera 5 och 7 ska vara 12", "line": 9, @@ -1148,8 +1282,9 @@ "keyword": "Given", "name": "att jag har knappat in 5", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1157,8 +1292,9 @@ "keyword": "And", "name": "att jag har knappat in 7", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1166,8 +1302,9 @@ "keyword": "When", "name": "jag summerar", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1175,8 +1312,9 @@ "keyword": "Then", "name": "ska resultatet vara 12", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1185,12 +1323,15 @@ ] }, { + "id": "test-de-cultuur-in-het-vlaams", "keyword": "Feature", "name": "Test de Cultuur in het Vlaams", + "uri": "Features/07Localization/Vlaams.feature", "tags": [], "line": 1, "elements": [ { + "id": "test-de-cultuur-in-het-vlaams;het-scenario", "keyword": "Scenario", "name": "Het Scenario", "line": 4, @@ -1201,8 +1342,9 @@ "keyword": "Given", "name": "dat ik 50 ingeef", "line": 5, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1210,8 +1352,9 @@ "keyword": "And", "name": "dat ik 70 ingeef", "line": 6, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1219,8 +1362,9 @@ "keyword": "When", "name": "ik plus druk", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1228,8 +1372,9 @@ "keyword": "Then", "name": "moet het resultaat 120 zijn", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1238,12 +1383,15 @@ ] }, { + "id": "attribute-overloading", "keyword": "Feature", "name": "Attribute overloading", + "uri": "Features/08AttributeOverloading/AttributeOverloading.feature", "tags": [], "line": 1, "elements": [ { + "id": "attribute-overloading;checking-number-for-evenness", "keyword": "Scenario", "name": "Checking number for evenness", "line": 6, @@ -1254,8 +1402,9 @@ "keyword": "Given", "name": "I have this simple step", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1263,8 +1412,9 @@ "keyword": "And", "name": "this simple step", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1272,8 +1422,9 @@ "keyword": "And", "name": "also this step", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1281,8 +1432,9 @@ "keyword": "When", "name": "I do something", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1290,8 +1442,9 @@ "keyword": "Then", "name": "I could validate that the number 2 is even", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1299,8 +1452,9 @@ "keyword": "And", "name": "that the number 4 is even", "line": 12, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1308,8 +1462,9 @@ "keyword": "But", "name": "the number 3 is odd", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1318,12 +1473,15 @@ ] }, { + "id": "calling-steps-from-stepdefinitions", "keyword": "Feature", "name": "Calling Steps from StepDefinitions", + "uri": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", "tags": [], "line": 1, "elements": [ { + "id": "calling-steps-from-stepdefinitions;log-in", "keyword": "Scenario", "name": "Log in", "line": 6, @@ -1334,8 +1492,9 @@ "keyword": "Given", "name": "I am on the index page", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1343,8 +1502,9 @@ "keyword": "When", "name": "I enter my unsername nad password", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1352,8 +1512,9 @@ "keyword": "And", "name": "I click the login button", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1361,14 +1522,16 @@ "keyword": "Then", "name": "the welcome page should be displayed", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "calling-steps-from-stepdefinitions;do-something-meaningful", "keyword": "Scenario", "name": "Do something meaningful", "line": 12, @@ -1379,8 +1542,9 @@ "keyword": "Given", "name": "I am logged in", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1388,8 +1552,9 @@ "keyword": "When", "name": "I dosomething meaningful", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1397,8 +1562,9 @@ "keyword": "Then", "name": "I should get rewarded", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1407,12 +1573,15 @@ ] }, { + "id": "step-argument-transformations", "keyword": "Feature", "name": "Step Argument Transformations", + "uri": "Features/10StepTransformation/StepTransformation.feature", "tags": [], "line": 1, "elements": [ { + "id": "step-argument-transformations;steps-with-non-string-arguments", "keyword": "Scenario", "name": "Steps with non-string arguments", "line": 6, @@ -1423,8 +1592,9 @@ "keyword": "Given", "name": "Dan has been registered at date 2003/03/13", "line": 7, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1432,8 +1602,9 @@ "keyword": "And", "name": "Aslak has been registered at terminal 2", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1441,8 +1612,9 @@ "keyword": "Then", "name": "I should be able to see Aslak at terminal 2", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1451,12 +1623,15 @@ ] }, { + "id": "injecting-context-into-step-specifications", "keyword": "Feature", "name": "Injecting context into step specifications", + "uri": "Features/11ContextInjection/ContextInjection.feature", "tags": [], "line": 1, "elements": [ { + "id": "injecting-context-into-step-specifications;feature-with-no-context", "keyword": "Scenario", "name": "Feature with no context", "line": 8, @@ -1467,8 +1642,9 @@ "keyword": "Given", "name": "a feature which requires no context", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1476,14 +1652,16 @@ "keyword": "Then", "name": "everything is dandy", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-a-single-context", "keyword": "Scenario", "name": "Feature with a single context", "line": 12, @@ -1494,8 +1672,9 @@ "keyword": "Given", "name": "a feature which requires a single context", "line": 13, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1503,14 +1682,16 @@ "keyword": "Then", "name": "the context is set", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-multiple-contexts", "keyword": "Scenario", "name": "Feature with multiple contexts", "line": 16, @@ -1521,8 +1702,9 @@ "keyword": "Given", "name": "a feature which requires multiple contexts", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1530,14 +1712,16 @@ "keyword": "Then", "name": "the contexts are set", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-recursive-contexts", "keyword": "Scenario", "name": "Feature with recursive contexts", "line": 20, @@ -1548,8 +1732,9 @@ "keyword": "Given", "name": "a feature which requires a recursive context", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1557,8 +1742,9 @@ "keyword": "Then", "name": "the context is set", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1566,14 +1752,16 @@ "keyword": "And", "name": "its sub-context is set", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "injecting-context-into-step-specifications;feature-with-a-dependent-context", "keyword": "Scenario", "name": "Feature with a dependent context", "line": 25, @@ -1584,8 +1772,9 @@ "keyword": "Given", "name": "a feature which requires a single context", "line": 26, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1593,8 +1782,9 @@ "keyword": "Then", "name": "the context is set", "line": 27, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1602,8 +1792,9 @@ "keyword": "And", "name": "the context was created by the feature with a single context scenario", "line": 28, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1612,12 +1803,15 @@ ] }, { + "id": "nested-folder-example", "keyword": "Feature", "name": "Nested Folder Example", + "uri": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", "tags": [], "line": 1, "elements": [ { + "id": "nested-folder-example;nested---add-two-numbers", "keyword": "Scenario", "name": "Nested - Add two numbers", "line": 7, @@ -1632,8 +1826,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1641,8 +1836,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1650,8 +1846,9 @@ "keyword": "When", "name": "I press add", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1659,8 +1856,9 @@ "keyword": "Then", "name": "the result should be 120 on the screen", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1669,12 +1867,15 @@ ] }, { + "id": "multiline-feature-example", "keyword": "Feature", "name": "Multiline Feature Example", + "uri": "Features/13MultilineText/MultilineFeatureExample.feature", "tags": [], "line": 1, "elements": [ { + "id": "multiline-feature-example;mutliline-output", "keyword": "Scenario", "name": "Mutliline Output", "line": 7, @@ -1689,8 +1890,9 @@ "keyword": "Given", "name": "I have read in some text from the user", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1698,8 +1900,9 @@ "keyword": "When", "name": "I process this input", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1707,8 +1910,9 @@ "keyword": "Then", "name": "the result will be saved to the multiline text data store", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1717,12 +1921,15 @@ ] }, { + "id": "sample-markdown-feature", "keyword": "Feature", "name": "Sample Markdown Feature", + "uri": "Features/14MarkdownExample/MarkdownExamples.feature", "tags": [], "line": 1, "elements": [ { + "id": "sample-markdown-feature;sample-markdown-scenario-example", "keyword": "Scenario", "name": "Sample Markdown Scenario Example", "line": 44, @@ -1733,8 +1940,9 @@ "keyword": "Given", "name": "this", "line": 62, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1742,18 +1950,20 @@ "keyword": "Then", "name": "that", "line": 63, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { - "keyword": "Scenario Outline", + "id": "sample-markdown-feature;sample-markdown-scenario-outline-example", + "keyword": "Scenario", "name": "Sample Markdown Scenario Outline Example", "line": 66, - "type": "scenario_outline", + "type": "scenario", "tags": [ { "name": "@AddingATag" @@ -1764,8 +1974,9 @@ "keyword": "Given", "name": "this: ", "line": 72, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1773,8 +1984,9 @@ "keyword": "Then", "name": "that: ", "line": 73, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1783,12 +1995,15 @@ ] }, { + "id": "interactive-dhtml-view", "keyword": "Feature", "name": "Interactive DHTML View", + "uri": "Features/15Pickles/InteractiveDHTMLView.feature", "tags": [], "line": 1, "elements": [ { + "id": "interactive-dhtml-view;scenario-with-large-data-table", "keyword": "Scenario", "name": "Scenario with large data table", "line": 7, @@ -1799,8 +2014,9 @@ "keyword": "Given", "name": "a feature with a large table of data:", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1808,8 +2024,9 @@ "keyword": "When", "name": "I click on the table heading", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1817,8 +2034,9 @@ "keyword": "Then", "name": "the table body should collapse", "line": 33, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1827,12 +2045,15 @@ ] }, { + "id": "kinds-of-verification", "keyword": "Feature", "name": "Kinds of verification", + "uri": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "tags": [], "line": 1, "elements": [ { + "id": "kinds-of-verification;verified-automatically", "keyword": "Scenario", "name": "Verified automatically", "line": 8, @@ -1847,8 +2068,9 @@ "keyword": "Given", "name": "a feature that is verified automatically", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1856,8 +2078,9 @@ "keyword": "When", "name": "I run pickles", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1865,14 +2088,16 @@ "keyword": "Then", "name": "it appears in the @automated summary", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "kinds-of-verification;verified-manually", "keyword": "Scenario", "name": "Verified manually", "line": 14, @@ -1887,8 +2112,9 @@ "keyword": "Given", "name": "a feature that is verified manually", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1896,8 +2122,9 @@ "keyword": "When", "name": "I run pickles", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1905,14 +2132,16 @@ "keyword": "Then", "name": "it appears in the @manual summary", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "kinds-of-verification;verified-automatically", "keyword": "Scenario", "name": "Verified automatically", "line": 20, @@ -1927,8 +2156,9 @@ "keyword": "Given", "name": "a feature that is not verified", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1936,8 +2166,9 @@ "keyword": "When", "name": "I run pickles", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1945,8 +2176,9 @@ "keyword": "Then", "name": "it appears in the @notTested summary", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -1955,12 +2187,15 @@ ] }, { + "id": "arithmetic", "keyword": "Feature", "name": "Arithmetic", + "uri": "Features/Arithmetic.feature", "tags": [], "line": 1, "elements": [ { + "id": "arithmetic;add-two-numbers", "keyword": "Scenario", "name": "Add two numbers", "line": 10, @@ -1978,8 +2213,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1987,8 +2223,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -1996,8 +2233,9 @@ "keyword": "When", "name": "I press add", "line": 17, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2005,14 +2243,16 @@ "keyword": "Then", "name": "the result should be 120 on the screen", "line": 18, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "arithmetic;subtract-two-numbers", "keyword": "Scenario", "name": "Subtract two numbers", "line": 21, @@ -2030,8 +2270,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2039,8 +2280,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 23, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2048,8 +2290,9 @@ "keyword": "When", "name": "I press subtract", "line": 24, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2057,14 +2300,16 @@ "keyword": "Then", "name": "the result should be -20 on the screen", "line": 25, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "arithmetic;multiply-two-numbers", "keyword": "Scenario", "name": "Multiply two numbers", "line": 28, @@ -2082,8 +2327,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 29, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2091,8 +2337,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 30, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2100,8 +2347,9 @@ "keyword": "When", "name": "I press multiply", "line": 31, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2109,14 +2357,16 @@ "keyword": "Then", "name": "the result should be 3500 on the screen", "line": 32, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "arithmetic;divide-two-numbers", "keyword": "Scenario", "name": "Divide two numbers", "line": 35, @@ -2134,8 +2384,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 36, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2143,8 +2394,9 @@ "keyword": "And", "name": "I have entered 2 into the calculator", "line": 37, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2152,8 +2404,9 @@ "keyword": "When", "name": "I press divide", "line": 38, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2161,8 +2414,9 @@ "keyword": "Then", "name": "the result should be 25 on the screen", "line": 39, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -2171,12 +2425,15 @@ ] }, { + "id": "trigonometry", "keyword": "Feature", "name": "Trigonometry", + "uri": "Features/Trigonometry.feature", "tags": [], "line": 1, "elements": [ { + "id": "trigonometry;sine", "keyword": "Scenario", "name": "Sine", "line": 7, @@ -2194,8 +2451,9 @@ "keyword": "Given", "name": "I have entered 90 into the calculator", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2203,8 +2461,9 @@ "keyword": "When", "name": "I press sin", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2212,14 +2471,16 @@ "keyword": "Then", "name": "the result should be 1 on the screen", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "trigonometry;cosine", "keyword": "Scenario", "name": "Cosine", "line": 13, @@ -2237,8 +2498,9 @@ "keyword": "Given", "name": "I have entered 0 into the calculator", "line": 14, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2246,8 +2508,9 @@ "keyword": "When", "name": "I press cos", "line": 15, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2255,14 +2518,16 @@ "keyword": "Then", "name": "the result should be 1 on the screen", "line": 16, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } ] }, { + "id": "trigonometry;tangent", "keyword": "Scenario", "name": "Tangent", "line": 19, @@ -2280,8 +2545,9 @@ "keyword": "Given", "name": "I have entered 45 into the calculator", "line": 20, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2289,8 +2555,9 @@ "keyword": "When", "name": "I press tan", "line": 21, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2298,8 +2565,9 @@ "keyword": "Then", "name": "the result should be 1 on the screen", "line": 22, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } @@ -2308,12 +2576,15 @@ ] }, { + "id": "clearing-screen", "keyword": "Feature", "name": "Clearing Screen", + "uri": "Features/Workflow/ClearingScreen.feature", "tags": [], "line": 1, "elements": [ { + "id": "clearing-screen;clear-the-screen", "keyword": "Scenario", "name": "Clear the screen", "line": 7, @@ -2331,8 +2602,9 @@ "keyword": "Given", "name": "I have entered 50 into the calculator", "line": 8, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2340,8 +2612,9 @@ "keyword": "And", "name": "I have entered 70 into the calculator", "line": 9, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2349,8 +2622,9 @@ "keyword": "When", "name": "I press C", "line": 10, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } }, @@ -2358,8 +2632,9 @@ "keyword": "Then", "name": "the screen should be empty", "line": 11, + "hidden": false, "result": { - "status": "inconclusive", + "status": "Undefined", "duration": 1 } } diff --git a/docs/Output/Dhtml/Index.html b/docs/Output/Dhtml/Index.html index 6bc691b98..12d020a91 100644 --- a/docs/Output/Dhtml/Index.html +++ b/docs/Output/Dhtml/Index.html @@ -14,13 +14,7 @@ - - - + diff --git a/docs/Output/Dhtml/default.htm b/docs/Output/Dhtml/default.htm deleted file mode 100644 index 3e777c9dc..000000000 --- a/docs/Output/Dhtml/default.htm +++ /dev/null @@ -1,554 +0,0 @@ - - - - - - Features - - - - - - - - - - - - - - -
        - Loading... -
        - - - - - - - - - - - - -
        -
        -
        -
        -
        -
        -
        -
        - -
        - - -
        - -
        Generated on:
        -
        -
        -
        - -
        -
        -
        -
        - - - - -
        -

        -
        -
        - -
        -
        -
        -

        Background:

        -
        -
          -
          -
          - -
          -
          - - - - - -
          - -
          -
          - -
          -

          -
          -
          - -
          - -
            - -
              -
            • -
              - - - - - - -
              -
              - : -
              -
              -
              -
              • -
            - -
            - - - Get Link for Scenario - -
            -
            -
            - - -
            - - -
            -
            - - - -
            - - -
            -
            -
            -
            -
            - -
            - -
            -
            -

            Scenario Summary by Root Namespace

            - -
            -
            -

            Scenario Summary by Top 20 Tags

            - -
            -
            -

            @NotTested Scenario Summary by Root Namespace

            - -
            -
            -
            - -
            - - - - - - - - - - - - - - - - - - - - - - - diff --git a/docs/Output/Dhtml/img/glyphicons-halflings-white.png b/docs/Output/Dhtml/img/glyphicons-halflings-white.png index a001c35f8..776b00aef 100644 Binary files a/docs/Output/Dhtml/img/glyphicons-halflings-white.png and b/docs/Output/Dhtml/img/glyphicons-halflings-white.png differ diff --git a/docs/Output/Dhtml/img/glyphicons-halflings.png b/docs/Output/Dhtml/img/glyphicons-halflings.png index f15c257ee..39207652a 100644 Binary files a/docs/Output/Dhtml/img/glyphicons-halflings.png and b/docs/Output/Dhtml/img/glyphicons-halflings.png differ diff --git a/docs/Output/Dhtml/img/link.png b/docs/Output/Dhtml/img/link.png index 68fc43b7c..312176330 100644 Binary files a/docs/Output/Dhtml/img/link.png and b/docs/Output/Dhtml/img/link.png differ diff --git a/docs/Output/Dhtml/pickledFeatures.js b/docs/Output/Dhtml/pickledFeatures.js index 5219e541a..26b15eb4a 100644 --- a/docs/Output/Dhtml/pickledFeatures.js +++ b/docs/Output/Dhtml/pickledFeatures.js @@ -1,12 +1,13 @@ jsonPWrapper ({ "Features": [ { - "RelativeFolder": "Features\\00BasicGherkin\\BasicGherkin.feature", + "RelativeFolder": "Features/00BasicGherkin/BasicGherkin.feature", "Feature": { "Name": "Showing basic gherkin syntax", - "Description": "In order to see that gherkin is a very simple language \r\nAs a SpecFlow evangelist \r\nI want to show that basic syntax\r\n\r\n![Test Image](test.jpg)", + "Description": "In order to see that gherkin is a very simple language \nAs a SpecFlow evangelist \nI want to show that basic syntax\n\n![Test Image](test.jpg)", "FeatureElements": [ { + "Examples": [], "Name": "Simple GWT", "Slug": "simple-gwt", "Description": "", @@ -41,6 +42,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Using And and But", "Slug": "using-and-and-but", "Description": "", @@ -110,12 +112,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\01TestRunner\\TestRunnerIsNotImportant.feature", + "RelativeFolder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", "Feature": { "Name": "The test runner is not (very) important", - "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to be able to call my steps in the same manner inspite of the testrunner configured", + "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \nAs a SpecFlow evanglist \nI want to be able to call my steps in the same manner inspite of the testrunner configured", "FeatureElements": [ { + "Examples": [], "Name": "A couple of simple steps", "Slug": "a-couple-of-simple-steps", "Description": "", @@ -164,12 +167,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\Hooks.feature", + "RelativeFolder": "Features/02TagsAndHooks/Hooks.feature", "Feature": { "Name": "Addition", - "Description": "In order to explain the order in which hooks are run \r\nAs a SpecFlow evanglist \r\nI wan to be able to hook into pre and post conditions in SpecFlow", + "Description": "In order to explain the order in which hooks are run \nAs a SpecFlow evanglist \nI wan to be able to hook into pre and post conditions in SpecFlow", "FeatureElements": [ { + "Examples": [], "Name": "Hooking into pre conditions for Test Runs in SpecFlow", "Slug": "hooking-into-pre-conditions-for-test-runs-in-specflow", "Description": "", @@ -197,6 +201,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Features in SpecFlow", "Slug": "hooking-into-pre-conditions-for-features-in-specflow", "Description": "", @@ -224,6 +229,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Scenarios in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarios-in-specflow", "Description": "", @@ -251,6 +257,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for ScenarioBlocks in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarioblocks-in-specflow", "Description": "", @@ -278,6 +285,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Steps in SpecFlow", "Slug": "hooking-into-pre-conditions-for-steps-in-specflow", "Description": "", @@ -319,12 +327,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\TagDemo.feature", + "RelativeFolder": "Features/02TagsAndHooks/TagDemo.feature", "Feature": { "Name": "Tag demonstrator", - "Description": "In order to show the capabilities of tags in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to write scenarios that has tags and show their usage in code", + "Description": "In order to show the capabilities of tags in SpecFlow \nAs a SpecFlow evanglist \nI want to write scenarios that has tags and show their usage in code", "FeatureElements": [ { + "Examples": [], "Name": "Ignored scenario", "Slug": "ignored-scenario", "Description": "", @@ -368,6 +377,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario without tags", "Slug": "a-scenario-without-tags", "Description": "", @@ -402,6 +412,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario with 1 tag", "Slug": "a-scenario-with-1-tag", "Description": "", @@ -438,6 +449,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario with 3 tags", "Slug": "a-scenario-with-3-tags", "Description": "", @@ -476,6 +488,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "A scenario with 2 tags", "Slug": "a-scenario-with-2-tags", "Description": "", @@ -530,10 +543,10 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\03ScenarioOutline\\ScenarioOutline.feature", + "RelativeFolder": "Features/03ScenarioOutline/ScenarioOutline.feature", "Feature": { "Name": "Scenario outline", - "Description": "In order to not have to type the same scenario over and over \r\nAs a SpecFlow evangelist \r\nI want to show how to use ScenarioOutline", + "Description": "In order to not have to type the same scenario over and over \nAs a SpecFlow evangelist \nI want to show how to use ScenarioOutline", "FeatureElements": [ { "Examples": [ @@ -801,12 +814,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\031ScenarioContext\\ScenarioContext.feature", + "RelativeFolder": "Features/031ScenarioContext/ScenarioContext.feature", "Feature": { "Name": "Scenario Context features", - "Description": "In order to show how to use ScenarioContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in ScenarioContext", + "Description": "In order to show how to use ScenarioContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in ScenarioContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from ScenarioContext", "Slug": "store-and-retrive-person-marcus-from-scenariocontext", "Description": "", @@ -834,6 +848,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Showing information of the scenario", "Slug": "showing-information-of-the-scenario", "Description": "", @@ -880,6 +895,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Show the type of step we're currently on", "Slug": "show-the-type-of-step-were-currently-on", "Description": "", @@ -928,6 +944,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Display error information in AfterScenario", "Slug": "display-error-information-in-afterscenario", "Description": "", @@ -951,6 +968,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Pending step", "Slug": "pending-step", "Description": "", @@ -992,12 +1010,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\032FeatureContext\\FeatureContextFeatures.feature", + "RelativeFolder": "Features/032FeatureContext/FeatureContextFeatures.feature", "Feature": { "Name": "FeatureContext features", - "Description": "In order to show how to use FeatureContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in FeatureContext", + "Description": "In order to show how to use FeatureContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in FeatureContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from FeatureContext Current", "Slug": "store-and-retrive-person-marcus-from-featurecontext-current", "Description": "", @@ -1025,6 +1044,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Showing information of the feature", "Slug": "showing-information-of-the-feature", "Description": "", @@ -1097,12 +1117,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\04Background\\BackgroundFeature.feature", + "RelativeFolder": "Features/04Background/BackgroundFeature.feature", "Feature": { "Name": "Show the use of background", - "Description": "In order to show how to use the Background keyword of Gherkin \r\nAs a SpecFlow evanglist \r\nI want to show that background steps are called before any scenario step", + "Description": "In order to show how to use the Background keyword of Gherkin \nAs a SpecFlow evanglist \nI want to show that background steps are called before any scenario step", "FeatureElements": [ { + "Examples": [], "Name": "Add 1 to the sum", "Slug": "add-1-to-the-sum", "Description": "", @@ -1130,6 +1151,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Add 2 to the sum", "Slug": "add-2-to-the-sum", "Description": "", @@ -1158,6 +1180,7 @@ jsonPWrapper ({ } ], "Background": { + "Examples": [], "Name": "", "Description": "", "Steps": [ @@ -1197,12 +1220,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\05TablesAndAssist\\TableScenario.feature", + "RelativeFolder": "Features/05TablesAndAssist/TableScenario.feature", "Feature": { "Name": "Showing table usage", - "Description": "In order to show how to use tables \r\nAs a SpecFlow evanglist \r\nI want to write some simple scenarios that uses tables tables", + "Description": "In order to show how to use tables \nAs a SpecFlow evanglist \nI want to write some simple scenarios that uses tables tables", "FeatureElements": [ { + "Examples": [], "Name": "Using tables", "Slug": "using-tables", "Description": "", @@ -1281,6 +1305,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Using tables with SpecFlow Assist", "Slug": "using-tables-with-specflow-assist", "Description": "", @@ -1359,6 +1384,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Creating a entity from field value", "Slug": "creating-a-entity-from-field-value", "Description": "", @@ -1426,6 +1452,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Example of a wide table", "Slug": "example-of-a-wide-table", "Description": "", @@ -1532,12 +1559,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\06CompareToAssist\\CompareTo.feature", + "RelativeFolder": "Features/06CompareToAssist/CompareTo.feature", "Feature": { "Name": "Show the compare to feature", - "Description": "In order to show the compare to features of SpecFlow Assist \r\nAs a SpecFlow evanglist \r\nI want to show how the different versions of compareTo works", + "Description": "In order to show the compare to features of SpecFlow Assist \nAs a SpecFlow evanglist \nI want to show how the different versions of compareTo works", "FeatureElements": [ { + "Examples": [], "Name": "CompareToInstance", "Slug": "comparetoinstance", "Description": "", @@ -1662,6 +1690,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "CompareToSet", "Slug": "comparetoset", "Description": "", @@ -1777,12 +1806,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\07Localization\\Svenska.feature", + "RelativeFolder": "Features/07Localization/Svenska.feature", "Feature": { "Name": "Svenska - Summering", - "Description": "För att slippa att göra dumma fel \r\nSom räknare \r\nVill jag kunna lägga summera", + "Description": "För att slippa att göra dumma fel \nSom räknare \nVill jag kunna lägga summera", "FeatureElements": [ { + "Examples": [], "Name": "Summera 5 och 7 ska vara 12", "Slug": "summera-5-och-7-ska-vara-12", "Description": "", @@ -1838,12 +1868,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\07Localization\\Vlaams.feature", + "RelativeFolder": "Features/07Localization/Vlaams.feature", "Feature": { "Name": "Test de Cultuur in het Vlaams", "Description": "", "FeatureElements": [ { + "Examples": [], "Name": "Het Scenario", "Slug": "het-scenario", "Description": "", @@ -1899,12 +1930,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\08AttributeOverloading\\AttributeOverloading.feature", + "RelativeFolder": "Features/08AttributeOverloading/AttributeOverloading.feature", "Feature": { "Name": "Attribute overloading", - "Description": "In order to show that steps can be used with multiple attributes \r\nAs a SpecFlow Evangelist \r\nI want to show that similar attributes can be applied to the same step definition", + "Description": "In order to show that steps can be used with multiple attributes \nAs a SpecFlow Evangelist \nI want to show that similar attributes can be applied to the same step definition", "FeatureElements": [ { + "Examples": [], "Name": "Checking number for evenness", "Slug": "checking-number-for-evenness", "Description": "", @@ -1981,12 +2013,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\09CallingStepsFromSteps\\CallingStepsFromSteps.feature", + "RelativeFolder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", "Feature": { "Name": "Calling Steps from StepDefinitions", - "Description": "In order to create steps of a higher abstraction \r\nAs a SpecFlow evangelist \r\nI want reuse other steps in my step definitions", + "Description": "In order to create steps of a higher abstraction \nAs a SpecFlow evangelist \nI want reuse other steps in my step definitions", "FeatureElements": [ { + "Examples": [], "Name": "Log in", "Slug": "log-in", "Description": "", @@ -2028,6 +2061,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Do something meaningful", "Slug": "do-something-meaningful", "Description": "", @@ -2076,12 +2110,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\10StepTransformation\\StepTransformation.feature", + "RelativeFolder": "Features/10StepTransformation/StepTransformation.feature", "Feature": { "Name": "Step Argument Transformations", - "Description": "In order to reduce the amount of code and repetitive tasks in my steps \r\nAs a SpecFlow evanglist \r\nI want to define reusable transformations for my step arguments", + "Description": "In order to reduce the amount of code and repetitive tasks in my steps \nAs a SpecFlow evanglist \nI want to define reusable transformations for my step arguments", "FeatureElements": [ { + "Examples": [], "Name": "Steps with non-string arguments", "Slug": "steps-with-non-string-arguments", "Description": "", @@ -2130,12 +2165,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\11ContextInjection\\ContextInjection.feature", + "RelativeFolder": "Features/11ContextInjection/ContextInjection.feature", "Feature": { "Name": "Injecting context into step specifications", - "Description": "In order to don't have to rely on the global shared state\r\nand to be able to define the contexts required for each scenario. \r\nAs a SpecFlow Evanglist \r\nI would like to have the system automatically inject an instance of any class as\r\ndefined in the constructor of a step file", + "Description": "In order to don't have to rely on the global shared state\nand to be able to define the contexts required for each scenario. \nAs a SpecFlow Evanglist \nI would like to have the system automatically inject an instance of any class as\ndefined in the constructor of a step file", "FeatureElements": [ { + "Examples": [], "Name": "Feature with no context", "Slug": "feature-with-no-context", "Description": "", @@ -2163,6 +2199,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with a single context", "Slug": "feature-with-a-single-context", "Description": "", @@ -2190,6 +2227,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with multiple contexts", "Slug": "feature-with-multiple-contexts", "Description": "", @@ -2217,6 +2255,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with recursive contexts", "Slug": "feature-with-recursive-contexts", "Description": "", @@ -2251,6 +2290,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Feature with a dependent context", "Slug": "feature-with-a-dependent-context", "Description": "", @@ -2299,12 +2339,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\12NestedFolders\\ChildFolder\\ChildChildFolder\\NestedFolderExample.feature", + "RelativeFolder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", "Feature": { "Name": "Nested Folder Example", - "Description": "In order to test nested folder output \r\nAs a silly contributer \r\nI want to create an example of something several folders deep", + "Description": "In order to test nested folder output \nAs a silly contributer \nI want to create an example of something several folders deep", "FeatureElements": [ { + "Examples": [], "Name": "Nested - Add two numbers", "Slug": "nested---add-two-numbers", "Description": "", @@ -2362,12 +2403,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\13MultilineText\\MultilineFeatureExample.feature", + "RelativeFolder": "Features/13MultilineText/MultilineFeatureExample.feature", "Feature": { "Name": "Multiline Feature Example", - "Description": "In order capture this particular Gherkin feature \r\nAs a Pickles contributer \r\nI want to demonstrate an example of using multiline text in a Scenario", + "Description": "In order capture this particular Gherkin feature \nAs a Pickles contributer \nI want to demonstrate an example of using multiline text in a Scenario", "FeatureElements": [ { + "Examples": [], "Name": "Mutliline Output", "Slug": "mutliline-output", "Description": "", @@ -2376,7 +2418,7 @@ jsonPWrapper ({ "Keyword": "Given", "NativeKeyword": "Given ", "Name": "I have read in some text from the user", - "DocStringArgument": "This is line 1.\r\nThis is line 2!\r\nThis is line 3!!", + "DocStringArgument": "This is line 1.\nThis is line 2!\nThis is line 3!!", "StepComments": [], "AfterLastStepComments": [] }, @@ -2419,15 +2461,16 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\14MarkdownExample\\MarkdownExamples.feature", + "RelativeFolder": "Features/14MarkdownExample/MarkdownExamples.feature", "Feature": { "Name": "Sample Markdown Feature", - "Description": "# Header 1\r\n\r\n## Header 2\r\n\r\n### Header 3\r\n\r\n#### Header 4\r\n\r\n##### Header 5\r\n\r\n###### Header 6\r\n\r\nThis is a *significant* word\r\n\r\n1. Ordered #1\r\n2. Ordered #2\r\n3. Ordered #3\r\n\r\n- Unordered #1\r\n- Unordered #2\r\n- Unordered #3\r\n\r\nHorizontal Rule:\r\n- - -\r\n\r\nTable example:\r\n\r\n| First Header | Second Header |\r\n| ------------- | ------------- |\r\n| Content Cell | Content Cell |\r\n| Content Cell | Content Cell |\r\n\r\n- - -\r\n\r\nIncluding a picture: ![](./image.png)", + "Description": "# Header 1\n\n## Header 2\n\n### Header 3\n\n#### Header 4\n\n##### Header 5\n\n###### Header 6\n\nThis is a *significant* word\n\n1. Ordered #1\n2. Ordered #2\n3. Ordered #3\n\n- Unordered #1\n- Unordered #2\n- Unordered #3\n\nHorizontal Rule:\n- - -\n\nTable example:\n\n| First Header | Second Header |\n| ------------- | ------------- |\n| Content Cell | Content Cell |\n| Content Cell | Content Cell |\n\n- - -\n\nIncluding a picture: ![](./image.png)", "FeatureElements": [ { + "Examples": [], "Name": "Sample Markdown Scenario Example", "Slug": "sample-markdown-scenario-example", - "Description": "This is **important** text\r\n\r\nCode Block:\r\n\r\n```\r\nvar x = 2;\r\n```\r\n\r\nApple\r\n: Pomaceous fruit of plants of the genus Malus in\r\n the family Rosaceae.\r\n: An American computer company.\r\n\r\nOrange\r\n: The fruit of an evergreen tree of the genus Citrus.", + "Description": "This is **important** text\n\nCode Block:\n\n```\nvar x = 2;\n```\n\nApple\n: Pomaceous fruit of plants of the genus Malus in\n the family Rosaceae.\n: An American computer company.\n\nOrange\n: The fruit of an evergreen tree of the genus Citrus.", "Steps": [ { "Keyword": "Given", @@ -2479,7 +2522,7 @@ jsonPWrapper ({ ], "Name": "Sample Markdown Scenario Outline Example", "Slug": "sample-markdown-scenario-outline-example", - "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\r\n\r\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", + "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\n\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", "Steps": [ { "Keyword": "Given", @@ -2507,6 +2550,7 @@ jsonPWrapper ({ } ], "Background": { + "Examples": [], "Name": "", "Description": "This is the *coolest* background", "Steps": [ @@ -2546,12 +2590,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\15Pickles\\InteractiveDHTMLView.feature", + "RelativeFolder": "Features/15Pickles/InteractiveDHTMLView.feature", "Feature": { "Name": "Interactive DHTML View", - "Description": "In order to increase stakeholder engagement with pickled specs \r\nAs a SpecFlow evangelist \r\nI want to adjust the level of detail in the DHTML view to suite my audience \r\nSo that I do not overwhelm them.", + "Description": "In order to increase stakeholder engagement with pickled specs \nAs a SpecFlow evangelist \nI want to adjust the level of detail in the DHTML view to suite my audience \nSo that I do not overwhelm them.", "FeatureElements": [ { + "Examples": [], "Name": "Scenario with large data table", "Slug": "scenario-with-large-data-table", "Description": "", @@ -2696,12 +2741,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\15Pickles\\NotTestedAutomatedManualTags.feature", + "RelativeFolder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Feature": { "Name": "Kinds of verification", - "Description": "In order to increase stakeholder engagement with pickled specs\r\nAs a SpecFlow evangelist\r\nI want to make clear how many scenarios are automated, manually tested and not tested\r\nSo that the stakeholders have a better overview of progress", + "Description": "In order to increase stakeholder engagement with pickled specs\nAs a SpecFlow evangelist\nI want to make clear how many scenarios are automated, manually tested and not tested\nSo that the stakeholders have a better overview of progress", "FeatureElements": [ { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2738,6 +2784,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Verified manually", "Slug": "verified-manually", "Description": "", @@ -2774,6 +2821,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2824,12 +2872,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\Arithmetic.feature", + "RelativeFolder": "Features/Arithmetic.feature", "Feature": { "Name": "Arithmetic", - "Description": "In order to avoid silly mistakes \r\nAs a math idiot \r\nI want to be able to perform arithmetic on the calculator\r\n\r\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\r\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", + "Description": "In order to avoid silly mistakes \nAs a math idiot \nI want to be able to perform arithmetic on the calculator\n\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", "FeatureElements": [ { + "Examples": [], "Name": "Add two numbers", "Slug": "add-two-numbers", "Description": "$50 + 70 = 120$", @@ -2878,6 +2927,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Subtract two numbers", "Slug": "subtract-two-numbers", "Description": "", @@ -2922,6 +2972,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Multiply two numbers", "Slug": "multiply-two-numbers", "Description": "", @@ -2966,6 +3017,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Divide two numbers", "Slug": "divide-two-numbers", "Description": "", @@ -3024,12 +3076,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\Trigonometry.feature", + "RelativeFolder": "Features/Trigonometry.feature", "Feature": { "Name": "Trigonometry", - "Description": "In order to avoid perform more advanced calculations \r\nAs a math idiot \r\nI want to be able to use trigonometric functions", + "Description": "In order to avoid perform more advanced calculations \nAs a math idiot \nI want to be able to use trigonometric functions", "FeatureElements": [ { + "Examples": [], "Name": "Sine", "Slug": "sine", "Description": "", @@ -3067,6 +3120,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Cosine", "Slug": "cosine", "Description": "", @@ -3104,6 +3158,7 @@ jsonPWrapper ({ } }, { + "Examples": [], "Name": "Tangent", "Slug": "tangent", "Description": "", @@ -3155,12 +3210,13 @@ jsonPWrapper ({ } }, { - "RelativeFolder": "Features\\Workflow\\ClearingScreen.feature", + "RelativeFolder": "Features/Workflow/ClearingScreen.feature", "Feature": { "Name": "Clearing Screen", - "Description": "In order to restart a new set of calculations \r\nAs a math idiot \r\nI want to be able to clear the screen", + "Description": "In order to restart a new set of calculations \nAs a math idiot \nI want to be able to clear the screen", "FeatureElements": [ { + "Examples": [], "Name": "Clear the screen", "Slug": "clear-the-screen", "Description": "", @@ -3364,20 +3420,342 @@ jsonPWrapper ({ ], "Folders": [ { - "Folder": "Features", - "Total": 57, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, "Passing": 0, "Failing": 0, - "Inconclusive": 57 + "Inconclusive": 1 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 } ], "NotTestedFolders": [ { - "Folder": "Features", + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Total": 1, "Passing": 0, "Failing": 0, "Inconclusive": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 } ], "Scenarios": { @@ -3394,17 +3772,178 @@ jsonPWrapper ({ }, "FoldersWithTestKinds": [ { - "Folder": "Features", - "Total": 57, - "Automated": 55, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Automated": 1, "Manual": 1, "NotTested": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Automated": 3, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 } ] }, "Configuration": { "SutName": "Pickles", - "SutVersion": "2.3.3", - "GeneratedOn": "11 March 2021 17:02:53" + "SutVersion": "3.0.1", + "GeneratedOn": "4 October 2021 17:16:08" } }); \ No newline at end of file diff --git a/docs/Output/Excel/features.xlsx b/docs/Output/Excel/features.xlsx index 68f0ab9f2..e69397311 100644 Binary files a/docs/Output/Excel/features.xlsx and b/docs/Output/Excel/features.xlsx differ diff --git a/docs/Output/Html/Features/00BasicGherkin/BasicGherkin.html b/docs/Output/Html/Features/00BasicGherkin/BasicGherkin.html index 55d790e72..6f0b2c7d2 100644 --- a/docs/Output/Html/Features/00BasicGherkin/BasicGherkin.html +++ b/docs/Output/Html/Features/00BasicGherkin/BasicGherkin.html @@ -257,7 +257,9 @@

            Showing basic gherkin syntax

            -

            In order to see that gherkin is a very simple language
            As a SpecFlow evangelist
            I want to show that basic syntax

            +

            In order to see that gherkin is a very simple language
            +As a SpecFlow evangelist
            +I want to show that basic syntax

            Test Image

            @@ -308,9 +310,9 @@

            Using And and But

          diff --git a/docs/Output/Html/Features/00BasicGherkin/index.html b/docs/Output/Html/Features/00BasicGherkin/index.html index 5260e7fb4..eba16bd42 100644 --- a/docs/Output/Html/Features/00BasicGherkin/index.html +++ b/docs/Output/Html/Features/00BasicGherkin/index.html @@ -271,9 +271,9 @@

          00 Basic Gherkin

          diff --git a/docs/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html b/docs/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html index cc4d2c6b4..ac735d653 100644 --- a/docs/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html +++ b/docs/Output/Html/Features/01TestRunner/TestRunnerIsNotImportant.html @@ -257,7 +257,9 @@

          The test runner is not (very) important

          -

          In order to show that the test runner is just for the autogenerated stuff in SpecFlow
          As a SpecFlow evanglist
          I want to be able to call my steps in the same manner inspite of the testrunner configured

          +

          In order to show that the test runner is just for the autogenerated stuff in SpecFlow
          +As a SpecFlow evanglist
          +I want to be able to call my steps in the same manner inspite of the testrunner configured

          • @@ -281,9 +283,9 @@

            A couple of simple steps

          diff --git a/docs/Output/Html/Features/01TestRunner/index.html b/docs/Output/Html/Features/01TestRunner/index.html index 511029880..e6173d275 100644 --- a/docs/Output/Html/Features/01TestRunner/index.html +++ b/docs/Output/Html/Features/01TestRunner/index.html @@ -269,9 +269,9 @@

          01 Test Runner

          diff --git a/docs/Output/Html/Features/02TagsAndHooks/Hooks.html b/docs/Output/Html/Features/02TagsAndHooks/Hooks.html index 1d948078b..3e0293e76 100644 --- a/docs/Output/Html/Features/02TagsAndHooks/Hooks.html +++ b/docs/Output/Html/Features/02TagsAndHooks/Hooks.html @@ -257,7 +257,9 @@

          Addition

          -

          In order to explain the order in which hooks are run
          As a SpecFlow evanglist
          I wan to be able to hook into pre and post conditions in SpecFlow

          +

          In order to explain the order in which hooks are run
          +As a SpecFlow evanglist
          +I wan to be able to hook into pre and post conditions in SpecFlow

          • @@ -343,9 +345,9 @@

            Hooking into pre conditions for Steps in SpecFlow

          diff --git a/docs/Output/Html/Features/02TagsAndHooks/TagDemo.html b/docs/Output/Html/Features/02TagsAndHooks/TagDemo.html index e74c4c3ef..232fed700 100644 --- a/docs/Output/Html/Features/02TagsAndHooks/TagDemo.html +++ b/docs/Output/Html/Features/02TagsAndHooks/TagDemo.html @@ -258,7 +258,9 @@

          Tags: @allAboutTags, @important

          Tag demonstrator

          -

          In order to show the capabilities of tags in SpecFlow
          As a SpecFlow evanglist
          I want to write scenarios that has tags and show their usage in code

          +

          In order to show the capabilities of tags in SpecFlow
          +As a SpecFlow evanglist
          +I want to write scenarios that has tags and show their usage in code

          • @@ -361,9 +363,9 @@

            A scenario with 2 tags

          diff --git a/docs/Output/Html/Features/02TagsAndHooks/index.html b/docs/Output/Html/Features/02TagsAndHooks/index.html index 8895d244d..57afffe24 100644 --- a/docs/Output/Html/Features/02TagsAndHooks/index.html +++ b/docs/Output/Html/Features/02TagsAndHooks/index.html @@ -278,9 +278,9 @@

          02 Tags And Hooks

          diff --git a/docs/Output/Html/Features/031ScenarioContext/ScenarioContext.html b/docs/Output/Html/Features/031ScenarioContext/ScenarioContext.html index b8305a2b2..d99e2ede2 100644 --- a/docs/Output/Html/Features/031ScenarioContext/ScenarioContext.html +++ b/docs/Output/Html/Features/031ScenarioContext/ScenarioContext.html @@ -257,7 +257,9 @@

          Scenario Context features

          -

          In order to show how to use ScenarioContext
          As a SpecFlow evangelist
          I want to write some simple scenarios with data in ScenarioContext

          +

          In order to show how to use ScenarioContext
          +As a SpecFlow evangelist
          +I want to write some simple scenarios with data in ScenarioContext

          • @@ -347,9 +349,9 @@

            Pending step

          diff --git a/docs/Output/Html/Features/031ScenarioContext/index.html b/docs/Output/Html/Features/031ScenarioContext/index.html index a57b846ef..1865046a4 100644 --- a/docs/Output/Html/Features/031ScenarioContext/index.html +++ b/docs/Output/Html/Features/031ScenarioContext/index.html @@ -269,9 +269,9 @@

          031 Scenario Context

          diff --git a/docs/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html b/docs/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html index 929845e6d..639ab80fe 100644 --- a/docs/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html +++ b/docs/Output/Html/Features/032FeatureContext/FeatureContextFeatures.html @@ -258,7 +258,9 @@

          Tags: @andThisToo, @showUpInScenarioInfo

          FeatureContext features

          -

          In order to show how to use FeatureContext
          As a SpecFlow evangelist
          I want to write some simple scenarios with data in FeatureContext

          +

          In order to show how to use FeatureContext
          +As a SpecFlow evangelist
          +I want to write some simple scenarios with data in FeatureContext

          • @@ -298,9 +300,9 @@

            Showing information of the feature

          diff --git a/docs/Output/Html/Features/032FeatureContext/index.html b/docs/Output/Html/Features/032FeatureContext/index.html index 29f4e1f42..16d747f53 100644 --- a/docs/Output/Html/Features/032FeatureContext/index.html +++ b/docs/Output/Html/Features/032FeatureContext/index.html @@ -269,9 +269,9 @@

          032 Feature Context

          diff --git a/docs/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html b/docs/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html index 2617fa54c..580583bff 100644 --- a/docs/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html +++ b/docs/Output/Html/Features/03ScenarioOutline/ScenarioOutline.html @@ -257,7 +257,9 @@

          Scenario outline

          -

          In order to not have to type the same scenario over and over
          As a SpecFlow evangelist
          I want to show how to use ScenarioOutline

          +

          In order to not have to type the same scenario over and over
          +As a SpecFlow evangelist
          +I want to show how to use ScenarioOutline

          • @@ -433,9 +435,9 @@

            Examples: more than 100

          diff --git a/docs/Output/Html/Features/03ScenarioOutline/index.html b/docs/Output/Html/Features/03ScenarioOutline/index.html index a9fc1ee7a..97ce98022 100644 --- a/docs/Output/Html/Features/03ScenarioOutline/index.html +++ b/docs/Output/Html/Features/03ScenarioOutline/index.html @@ -269,9 +269,9 @@

          03 Scenario Outline

          diff --git a/docs/Output/Html/Features/04Background/BackgroundFeature.html b/docs/Output/Html/Features/04Background/BackgroundFeature.html index ea6696cfa..3d9bbe534 100644 --- a/docs/Output/Html/Features/04Background/BackgroundFeature.html +++ b/docs/Output/Html/Features/04Background/BackgroundFeature.html @@ -257,13 +257,12 @@

          Show the use of background

          -

          In order to show how to use the Background keyword of Gherkin
          As a SpecFlow evanglist
          I want to show that background steps are called before any scenario step

          +

          In order to show how to use the Background keyword of Gherkin
          +As a SpecFlow evanglist
          +I want to show that background steps are called before any scenario step

          • -
            -

            -
            • @@ -308,9 +307,9 @@

              Add 2 to the sum

          diff --git a/docs/Output/Html/Features/04Background/index.html b/docs/Output/Html/Features/04Background/index.html index 2342b2e21..9f8af10b9 100644 --- a/docs/Output/Html/Features/04Background/index.html +++ b/docs/Output/Html/Features/04Background/index.html @@ -269,9 +269,9 @@

          04 Background

          diff --git a/docs/Output/Html/Features/05TablesAndAssist/TableScenario.html b/docs/Output/Html/Features/05TablesAndAssist/TableScenario.html index ba3ae752e..bd9054386 100644 --- a/docs/Output/Html/Features/05TablesAndAssist/TableScenario.html +++ b/docs/Output/Html/Features/05TablesAndAssist/TableScenario.html @@ -257,7 +257,9 @@

          Showing table usage

          -

          In order to show how to use tables
          As a SpecFlow evanglist
          I want to write some simple scenarios that uses tables tables

          +

          In order to show how to use tables
          +As a SpecFlow evanglist
          +I want to write some simple scenarios that uses tables tables

          • @@ -329,9 +331,9 @@

            Example of a wide table

          diff --git a/docs/Output/Html/Features/05TablesAndAssist/index.html b/docs/Output/Html/Features/05TablesAndAssist/index.html index 73412c68a..2819484d9 100644 --- a/docs/Output/Html/Features/05TablesAndAssist/index.html +++ b/docs/Output/Html/Features/05TablesAndAssist/index.html @@ -269,9 +269,9 @@

          05 Tables And Assist

          diff --git a/docs/Output/Html/Features/06CompareToAssist/CompareTo.html b/docs/Output/Html/Features/06CompareToAssist/CompareTo.html index 8a79d6a53..9a03e7024 100644 --- a/docs/Output/Html/Features/06CompareToAssist/CompareTo.html +++ b/docs/Output/Html/Features/06CompareToAssist/CompareTo.html @@ -257,7 +257,9 @@

          Show the compare to feature

          -

          In order to show the compare to features of SpecFlow Assist
          As a SpecFlow evanglist
          I want to show how the different versions of compareTo works

          +

          In order to show the compare to features of SpecFlow Assist
          +As a SpecFlow evanglist
          +I want to show how the different versions of compareTo works

          • @@ -301,9 +303,9 @@

            CompareToSet

          diff --git a/docs/Output/Html/Features/06CompareToAssist/index.html b/docs/Output/Html/Features/06CompareToAssist/index.html index 8da9acf15..1f7139890 100644 --- a/docs/Output/Html/Features/06CompareToAssist/index.html +++ b/docs/Output/Html/Features/06CompareToAssist/index.html @@ -269,9 +269,9 @@

          06 Compare To Assist

          diff --git a/docs/Output/Html/Features/07Localization/Svenska.html b/docs/Output/Html/Features/07Localization/Svenska.html index 765d0c125..f9ca59dde 100644 --- a/docs/Output/Html/Features/07Localization/Svenska.html +++ b/docs/Output/Html/Features/07Localization/Svenska.html @@ -257,7 +257,9 @@

          Svenska - Summering

          -

          För att slippa att göra dumma fel
          Som räknare
          Vill jag kunna lägga summera

          +

          För att slippa att göra dumma fel
          +Som räknare
          +Vill jag kunna lägga summera

          • @@ -283,9 +285,9 @@

            Summera 5 och 7 ska vara 12

          diff --git a/docs/Output/Html/Features/07Localization/Vlaams.html b/docs/Output/Html/Features/07Localization/Vlaams.html index 1d8f16a71..de487e577 100644 --- a/docs/Output/Html/Features/07Localization/Vlaams.html +++ b/docs/Output/Html/Features/07Localization/Vlaams.html @@ -280,9 +280,9 @@

          Het Scenario

          diff --git a/docs/Output/Html/Features/07Localization/index.html b/docs/Output/Html/Features/07Localization/index.html index 7a2d93d0b..6c1276cb7 100644 --- a/docs/Output/Html/Features/07Localization/index.html +++ b/docs/Output/Html/Features/07Localization/index.html @@ -276,9 +276,9 @@

          07 Localization

          diff --git a/docs/Output/Html/Features/07Svenska/Svenska.html b/docs/Output/Html/Features/07Svenska/Svenska.html deleted file mode 100644 index f048cc883..000000000 --- a/docs/Output/Html/Features/07Svenska/Svenska.html +++ /dev/null @@ -1,291 +0,0 @@ - - - - - Summering - - - - - - - - -
          -
          - -
          -

          Summering

          -
          - 
          -            För att slippa att göra dumma fel
-Som räknare
-Vill jag kunna lägga summera
-
-
          -
          -
            -
          • -
            -

            Summera 5 och 7 ska vara 12

            -
            -
            -
              -
            • - Givet att jag har knappat in 5
              • -
            • - Och att jag har knappat in 7
              • -
            • - När jag summerar
              • -
            • - Så ska resultatet vara 12
              • -
            -
            - - - -
            • -
          -
          - -
          - - \ No newline at end of file diff --git a/docs/Output/Html/Features/07Svenska/index.html b/docs/Output/Html/Features/07Svenska/index.html deleted file mode 100644 index 7baaa912e..000000000 --- a/docs/Output/Html/Features/07Svenska/index.html +++ /dev/null @@ -1,272 +0,0 @@ - - - - - 07 Svenska - - - - - - - - -
          -
          - - - -
          - - \ No newline at end of file diff --git a/docs/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html b/docs/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html index b1dfa138a..f278f71be 100644 --- a/docs/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html +++ b/docs/Output/Html/Features/08AttributeOverloading/AttributeOverloading.html @@ -257,7 +257,9 @@

          Attribute overloading

          -

          In order to show that steps can be used with multiple attributes
          As a SpecFlow Evangelist
          I want to show that similar attributes can be applied to the same step definition

          +

          In order to show that steps can be used with multiple attributes
          +As a SpecFlow Evangelist
          +I want to show that similar attributes can be applied to the same step definition

          • @@ -289,9 +291,9 @@

            Checking number for evenness

          diff --git a/docs/Output/Html/Features/08AttributeOverloading/index.html b/docs/Output/Html/Features/08AttributeOverloading/index.html index 93bcccd3d..35cb28a88 100644 --- a/docs/Output/Html/Features/08AttributeOverloading/index.html +++ b/docs/Output/Html/Features/08AttributeOverloading/index.html @@ -269,9 +269,9 @@

          08 Attribute Overloading

          diff --git a/docs/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html b/docs/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html index c58a87aae..9edcb964f 100644 --- a/docs/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html +++ b/docs/Output/Html/Features/09CallingStepsFromSteps/CallingStepsFromSteps.html @@ -257,7 +257,9 @@

          Calling Steps from StepDefinitions

          -

          In order to create steps of a higher abstraction
          As a SpecFlow evangelist
          I want reuse other steps in my step definitions

          +

          In order to create steps of a higher abstraction
          +As a SpecFlow evangelist
          +I want reuse other steps in my step definitions

          • @@ -301,9 +303,9 @@

            Do something meaningful

          diff --git a/docs/Output/Html/Features/09CallingStepsFromSteps/index.html b/docs/Output/Html/Features/09CallingStepsFromSteps/index.html index 189592f00..2c52fbfa3 100644 --- a/docs/Output/Html/Features/09CallingStepsFromSteps/index.html +++ b/docs/Output/Html/Features/09CallingStepsFromSteps/index.html @@ -269,9 +269,9 @@

          09 Calling Steps From Steps

          diff --git a/docs/Output/Html/Features/10StepTransformation/StepTransformation.html b/docs/Output/Html/Features/10StepTransformation/StepTransformation.html index 3ff82cc5a..e693d6877 100644 --- a/docs/Output/Html/Features/10StepTransformation/StepTransformation.html +++ b/docs/Output/Html/Features/10StepTransformation/StepTransformation.html @@ -257,7 +257,9 @@

          Step Argument Transformations

          -

          In order to reduce the amount of code and repetitive tasks in my steps
          As a SpecFlow evanglist
          I want to define reusable transformations for my step arguments

          +

          In order to reduce the amount of code and repetitive tasks in my steps
          +As a SpecFlow evanglist
          +I want to define reusable transformations for my step arguments

          • @@ -281,9 +283,9 @@

            Steps with non-string arguments

          diff --git a/docs/Output/Html/Features/10StepTransformation/index.html b/docs/Output/Html/Features/10StepTransformation/index.html index 9e1e09ba6..0c844ae9b 100644 --- a/docs/Output/Html/Features/10StepTransformation/index.html +++ b/docs/Output/Html/Features/10StepTransformation/index.html @@ -269,9 +269,9 @@

          10 Step Transformation

          diff --git a/docs/Output/Html/Features/11ContextInjection/ContextInjection.html b/docs/Output/Html/Features/11ContextInjection/ContextInjection.html index bf3c84006..16cf5d0d7 100644 --- a/docs/Output/Html/Features/11ContextInjection/ContextInjection.html +++ b/docs/Output/Html/Features/11ContextInjection/ContextInjection.html @@ -258,7 +258,9 @@

          Injecting context into step specifications

          In order to don't have to rely on the global shared state -and to be able to define the contexts required for each scenario.
          As a SpecFlow Evanglist
          I would like to have the system automatically inject an instance of any class as +and to be able to define the contexts required for each scenario.
          +As a SpecFlow Evanglist
          +I would like to have the system automatically inject an instance of any class as defined in the constructor of a step file

            @@ -349,9 +351,9 @@

            Feature with a dependent context

          diff --git a/docs/Output/Html/Features/11ContextInjection/index.html b/docs/Output/Html/Features/11ContextInjection/index.html index fcc20fbe2..aa92ee7fa 100644 --- a/docs/Output/Html/Features/11ContextInjection/index.html +++ b/docs/Output/Html/Features/11ContextInjection/index.html @@ -271,9 +271,9 @@

          11 Context Injection

          diff --git a/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html b/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html index 8b34ffc05..9d0bbadb0 100644 --- a/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html +++ b/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.html @@ -257,7 +257,9 @@

          Nested Folder Example

          -

          In order to test nested folder output
          As a silly contributer
          I want to create an example of something several folders deep

          +

          In order to test nested folder output
          +As a silly contributer
          +I want to create an example of something several folders deep

          • @@ -284,9 +286,9 @@

            Nested - Add two numbers

          diff --git a/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html b/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html index 4a7d67fc0..3e4857ac0 100644 --- a/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html +++ b/docs/Output/Html/Features/12NestedFolders/ChildFolder/ChildChildFolder/index.html @@ -269,9 +269,9 @@

          Child Child Folder

          diff --git a/docs/Output/Html/Features/12NestedFolders/ChildFolder/index.html b/docs/Output/Html/Features/12NestedFolders/ChildFolder/index.html index aded3db1f..f185f0d95 100644 --- a/docs/Output/Html/Features/12NestedFolders/ChildFolder/index.html +++ b/docs/Output/Html/Features/12NestedFolders/ChildFolder/index.html @@ -259,9 +259,9 @@

          Child Folder

            diff --git a/docs/Output/Html/Features/12NestedFolders/index.html b/docs/Output/Html/Features/12NestedFolders/index.html index 3935a9575..b91d7c697 100644 --- a/docs/Output/Html/Features/12NestedFolders/index.html +++ b/docs/Output/Html/Features/12NestedFolders/index.html @@ -259,9 +259,9 @@

            12 Nested Folders

              diff --git a/docs/Output/Html/Features/13MultilineText/MultilineFeatureExample.html b/docs/Output/Html/Features/13MultilineText/MultilineFeatureExample.html index 034eb328e..0b51a0636 100644 --- a/docs/Output/Html/Features/13MultilineText/MultilineFeatureExample.html +++ b/docs/Output/Html/Features/13MultilineText/MultilineFeatureExample.html @@ -257,7 +257,9 @@

              Multiline Feature Example

              -

              In order capture this particular Gherkin feature
              As a Pickles contributer
              I want to demonstrate an example of using multiline text in a Scenario

              +

              In order capture this particular Gherkin feature
              +As a Pickles contributer
              +I want to demonstrate an example of using multiline text in a Scenario

              • @@ -284,9 +286,9 @@

                Mutliline Output

              diff --git a/docs/Output/Html/Features/13MultilineText/index.html b/docs/Output/Html/Features/13MultilineText/index.html index 4cfbc186a..ded1a85c5 100644 --- a/docs/Output/Html/Features/13MultilineText/index.html +++ b/docs/Output/Html/Features/13MultilineText/index.html @@ -269,9 +269,9 @@

              13 Multiline Text

            diff --git a/docs/Output/Html/Features/14MarkdownExample/MarkdownExamples.html b/docs/Output/Html/Features/14MarkdownExample/MarkdownExamples.html index 72d2a3730..ba0d9f487 100644 --- a/docs/Output/Html/Features/14MarkdownExample/MarkdownExamples.html +++ b/docs/Output/Html/Features/14MarkdownExample/MarkdownExamples.html @@ -257,23 +257,25 @@

            Sample Markdown Feature

            -

            Header 1

            -

            Header 2

            -

            Header 3

            -

            Header 4

            -
            Header 5
            -
            Header 6
            +

            Header 1

            +

            Header 2

            +

            Header 3

            +

            Header 4

            +
            Header 5
            +
            Header 6

            This is a significant word

            1. Ordered #1
            2. Ordered #2
              3. -
            3. Ordered #3
              4. -
            -
              -
            • Unordered #1
              • +
            • +

              Ordered #3

              +
              • +
            • +

              Unordered #1

              +
            • Unordered #2
            • Unordered #3
              • -
            +

            Horizontal Rule:

            Table example:

            @@ -296,16 +298,10 @@
            Header 6
            -

            Including a picture:

            +

            Including a picture:

            • -
              -

              -
              -

              This is the coolest background

              -
              -
              • @@ -325,12 +321,16 @@

                Sample Markdown Scenario Example

                var x = 2; -

                Apple -: Pomaceous fruit of plants of the genus Malus in - the family Rosaceae. -: An American computer company.

                -

                Orange -: The fruit of an evergreen tree of the genus Citrus.

                +
                +
                Apple
                +
                +

                Pomaceous fruit of plants of the genus Malus in +the family Rosaceae.

                +
                +
                An American computer company.
                +
                Orange
                +
                The fruit of an evergreen tree of the genus Citrus.
                +
            @@ -398,9 +398,9 @@

            Examples:

          diff --git a/docs/Output/Html/Features/14MarkdownExample/index.html b/docs/Output/Html/Features/14MarkdownExample/index.html index dd17317bc..205a941b8 100644 --- a/docs/Output/Html/Features/14MarkdownExample/index.html +++ b/docs/Output/Html/Features/14MarkdownExample/index.html @@ -301,9 +301,9 @@

          14 Markdown Example

          diff --git a/docs/Output/Html/Features/15Pickles/InteractiveDHTMLView.html b/docs/Output/Html/Features/15Pickles/InteractiveDHTMLView.html index b2d4d264e..84218ed32 100644 --- a/docs/Output/Html/Features/15Pickles/InteractiveDHTMLView.html +++ b/docs/Output/Html/Features/15Pickles/InteractiveDHTMLView.html @@ -257,7 +257,10 @@

          Interactive DHTML View

          -

          In order to increase stakeholder engagement with pickled specs
          As a SpecFlow evangelist
          I want to adjust the level of detail in the DHTML view to suite my audience
          So that I do not overwhelm them.

          +

          In order to increase stakeholder engagement with pickled specs
          +As a SpecFlow evangelist
          +I want to adjust the level of detail in the DHTML view to suite my audience
          +So that I do not overwhelm them.

          • @@ -281,9 +284,9 @@

            Scenario with large data table

          diff --git a/docs/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html b/docs/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html index 38585f475..4f08ce0ce 100644 --- a/docs/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html +++ b/docs/Output/Html/Features/15Pickles/NotTestedAutomatedManualTags.html @@ -323,9 +323,9 @@

          Verified automatically

          diff --git a/docs/Output/Html/Features/15Pickles/index.html b/docs/Output/Html/Features/15Pickles/index.html index 7e1eb9344..c82ef1bdd 100644 --- a/docs/Output/Html/Features/15Pickles/index.html +++ b/docs/Output/Html/Features/15Pickles/index.html @@ -280,9 +280,9 @@

          15 Pickles

          diff --git a/docs/Output/Html/Features/Arithmetic.html b/docs/Output/Html/Features/Arithmetic.html index fdb63e0b5..7ea9d57bf 100644 --- a/docs/Output/Html/Features/Arithmetic.html +++ b/docs/Output/Html/Features/Arithmetic.html @@ -257,7 +257,9 @@

          Arithmetic

          -

          In order to avoid silly mistakes
          As a math idiot
          I want to be able to perform arithmetic on the calculator

          +

          In order to avoid silly mistakes
          +As a math idiot
          +I want to be able to perform arithmetic on the calculator

          When $a \ne 0$, there are two solutions to $(ax^2 + bx + c = 0)$ and they are $$x = {-b \pm \sqrt{b^2-4ac} \over 2a}.$$

          @@ -353,9 +355,9 @@

          Divide two numbers

          diff --git a/docs/Output/Html/Features/Trigonometry.html b/docs/Output/Html/Features/Trigonometry.html index 5cb40794d..c657e3803 100644 --- a/docs/Output/Html/Features/Trigonometry.html +++ b/docs/Output/Html/Features/Trigonometry.html @@ -257,7 +257,9 @@

          Trigonometry

          -

          In order to avoid perform more advanced calculations
          As a math idiot
          I want to be able to use trigonometric functions

          +

          In order to avoid perform more advanced calculations
          +As a math idiot
          +I want to be able to use trigonometric functions

          • @@ -320,9 +322,9 @@

            Tangent

          diff --git a/docs/Output/Html/Features/Workflow/ClearingScreen.html b/docs/Output/Html/Features/Workflow/ClearingScreen.html index d41ba84f2..d1d7c369f 100644 --- a/docs/Output/Html/Features/Workflow/ClearingScreen.html +++ b/docs/Output/Html/Features/Workflow/ClearingScreen.html @@ -257,7 +257,9 @@

          Clearing Screen

          -

          In order to restart a new set of calculations
          As a math idiot
          I want to be able to clear the screen

          +

          In order to restart a new set of calculations
          +As a math idiot
          +I want to be able to clear the screen

          • @@ -284,9 +286,9 @@

            Clear the screen

          diff --git a/docs/Output/Html/Features/Workflow/index.html b/docs/Output/Html/Features/Workflow/index.html index 3906e4c4c..08418f2c6 100644 --- a/docs/Output/Html/Features/Workflow/index.html +++ b/docs/Output/Html/Features/Workflow/index.html @@ -269,9 +269,9 @@

          Workflow

          diff --git a/docs/Output/Html/Features/index.html b/docs/Output/Html/Features/index.html index 3618017a1..8aafdfc7e 100644 --- a/docs/Output/Html/Features/index.html +++ b/docs/Output/Html/Features/index.html @@ -281,9 +281,9 @@

          Features

          diff --git a/docs/Output/Html/img/failure.png b/docs/Output/Html/img/failure.png index b622cd135..03db140b9 100644 Binary files a/docs/Output/Html/img/failure.png and b/docs/Output/Html/img/failure.png differ diff --git a/docs/Output/Html/img/inconclusive.png b/docs/Output/Html/img/inconclusive.png index 0b3bf52e0..6bcceb509 100644 Binary files a/docs/Output/Html/img/inconclusive.png and b/docs/Output/Html/img/inconclusive.png differ diff --git a/docs/Output/Html/img/success.png b/docs/Output/Html/img/success.png index 2748ec6a7..6b888627e 100644 Binary files a/docs/Output/Html/img/success.png and b/docs/Output/Html/img/success.png differ diff --git a/docs/Output/Html/index.html b/docs/Output/Html/index.html index 5ac3eed20..f5a3f69f4 100644 --- a/docs/Output/Html/index.html +++ b/docs/Output/Html/index.html @@ -259,9 +259,9 @@

          Examples

            diff --git a/docs/Output/Html/readme.html b/docs/Output/Html/readme.html index 10adf9d99..7a5b90de2 100644 --- a/docs/Output/Html/readme.html +++ b/docs/Output/Html/readme.html @@ -258,9 +258,9 @@

            In the Features-folders you'll find quite a large population of .feature files that you can use to test out pickles on.

            diff --git a/docs/Output/JSON/pickledFeatures.json b/docs/Output/JSON/pickledFeatures.json index 014821554..57bd07582 100644 --- a/docs/Output/JSON/pickledFeatures.json +++ b/docs/Output/JSON/pickledFeatures.json @@ -1,12 +1,13 @@ { "Features": [ { - "RelativeFolder": "Features\\00BasicGherkin\\BasicGherkin.feature", + "RelativeFolder": "Features/00BasicGherkin/BasicGherkin.feature", "Feature": { "Name": "Showing basic gherkin syntax", - "Description": "In order to see that gherkin is a very simple language \r\nAs a SpecFlow evangelist \r\nI want to show that basic syntax\r\n\r\n![Test Image](test.jpg)", + "Description": "In order to see that gherkin is a very simple language \nAs a SpecFlow evangelist \nI want to show that basic syntax\n\n![Test Image](test.jpg)", "FeatureElements": [ { + "Examples": [], "Name": "Simple GWT", "Slug": "simple-gwt", "Description": "", @@ -41,6 +42,7 @@ } }, { + "Examples": [], "Name": "Using And and But", "Slug": "using-and-and-but", "Description": "", @@ -110,12 +112,13 @@ } }, { - "RelativeFolder": "Features\\01TestRunner\\TestRunnerIsNotImportant.feature", + "RelativeFolder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", "Feature": { "Name": "The test runner is not (very) important", - "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to be able to call my steps in the same manner inspite of the testrunner configured", + "Description": "In order to show that the test runner is just for the autogenerated stuff in SpecFlow \nAs a SpecFlow evanglist \nI want to be able to call my steps in the same manner inspite of the testrunner configured", "FeatureElements": [ { + "Examples": [], "Name": "A couple of simple steps", "Slug": "a-couple-of-simple-steps", "Description": "", @@ -164,12 +167,13 @@ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\Hooks.feature", + "RelativeFolder": "Features/02TagsAndHooks/Hooks.feature", "Feature": { "Name": "Addition", - "Description": "In order to explain the order in which hooks are run \r\nAs a SpecFlow evanglist \r\nI wan to be able to hook into pre and post conditions in SpecFlow", + "Description": "In order to explain the order in which hooks are run \nAs a SpecFlow evanglist \nI wan to be able to hook into pre and post conditions in SpecFlow", "FeatureElements": [ { + "Examples": [], "Name": "Hooking into pre conditions for Test Runs in SpecFlow", "Slug": "hooking-into-pre-conditions-for-test-runs-in-specflow", "Description": "", @@ -197,6 +201,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Features in SpecFlow", "Slug": "hooking-into-pre-conditions-for-features-in-specflow", "Description": "", @@ -224,6 +229,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Scenarios in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarios-in-specflow", "Description": "", @@ -251,6 +257,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for ScenarioBlocks in SpecFlow", "Slug": "hooking-into-pre-conditions-for-scenarioblocks-in-specflow", "Description": "", @@ -278,6 +285,7 @@ } }, { + "Examples": [], "Name": "Hooking into pre conditions for Steps in SpecFlow", "Slug": "hooking-into-pre-conditions-for-steps-in-specflow", "Description": "", @@ -319,12 +327,13 @@ } }, { - "RelativeFolder": "Features\\02TagsAndHooks\\TagDemo.feature", + "RelativeFolder": "Features/02TagsAndHooks/TagDemo.feature", "Feature": { "Name": "Tag demonstrator", - "Description": "In order to show the capabilities of tags in SpecFlow \r\nAs a SpecFlow evanglist \r\nI want to write scenarios that has tags and show their usage in code", + "Description": "In order to show the capabilities of tags in SpecFlow \nAs a SpecFlow evanglist \nI want to write scenarios that has tags and show their usage in code", "FeatureElements": [ { + "Examples": [], "Name": "Ignored scenario", "Slug": "ignored-scenario", "Description": "", @@ -368,6 +377,7 @@ } }, { + "Examples": [], "Name": "A scenario without tags", "Slug": "a-scenario-without-tags", "Description": "", @@ -402,6 +412,7 @@ } }, { + "Examples": [], "Name": "A scenario with 1 tag", "Slug": "a-scenario-with-1-tag", "Description": "", @@ -438,6 +449,7 @@ } }, { + "Examples": [], "Name": "A scenario with 3 tags", "Slug": "a-scenario-with-3-tags", "Description": "", @@ -476,6 +488,7 @@ } }, { + "Examples": [], "Name": "A scenario with 2 tags", "Slug": "a-scenario-with-2-tags", "Description": "", @@ -530,10 +543,10 @@ } }, { - "RelativeFolder": "Features\\03ScenarioOutline\\ScenarioOutline.feature", + "RelativeFolder": "Features/03ScenarioOutline/ScenarioOutline.feature", "Feature": { "Name": "Scenario outline", - "Description": "In order to not have to type the same scenario over and over \r\nAs a SpecFlow evangelist \r\nI want to show how to use ScenarioOutline", + "Description": "In order to not have to type the same scenario over and over \nAs a SpecFlow evangelist \nI want to show how to use ScenarioOutline", "FeatureElements": [ { "Examples": [ @@ -801,12 +814,13 @@ } }, { - "RelativeFolder": "Features\\031ScenarioContext\\ScenarioContext.feature", + "RelativeFolder": "Features/031ScenarioContext/ScenarioContext.feature", "Feature": { "Name": "Scenario Context features", - "Description": "In order to show how to use ScenarioContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in ScenarioContext", + "Description": "In order to show how to use ScenarioContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in ScenarioContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from ScenarioContext", "Slug": "store-and-retrive-person-marcus-from-scenariocontext", "Description": "", @@ -834,6 +848,7 @@ } }, { + "Examples": [], "Name": "Showing information of the scenario", "Slug": "showing-information-of-the-scenario", "Description": "", @@ -880,6 +895,7 @@ } }, { + "Examples": [], "Name": "Show the type of step we're currently on", "Slug": "show-the-type-of-step-were-currently-on", "Description": "", @@ -928,6 +944,7 @@ } }, { + "Examples": [], "Name": "Display error information in AfterScenario", "Slug": "display-error-information-in-afterscenario", "Description": "", @@ -951,6 +968,7 @@ } }, { + "Examples": [], "Name": "Pending step", "Slug": "pending-step", "Description": "", @@ -992,12 +1010,13 @@ } }, { - "RelativeFolder": "Features\\032FeatureContext\\FeatureContextFeatures.feature", + "RelativeFolder": "Features/032FeatureContext/FeatureContextFeatures.feature", "Feature": { "Name": "FeatureContext features", - "Description": "In order to show how to use FeatureContext \r\nAs a SpecFlow evangelist \r\nI want to write some simple scenarios with data in FeatureContext", + "Description": "In order to show how to use FeatureContext \nAs a SpecFlow evangelist \nI want to write some simple scenarios with data in FeatureContext", "FeatureElements": [ { + "Examples": [], "Name": "Store and retrive Person Marcus from FeatureContext Current", "Slug": "store-and-retrive-person-marcus-from-featurecontext-current", "Description": "", @@ -1025,6 +1044,7 @@ } }, { + "Examples": [], "Name": "Showing information of the feature", "Slug": "showing-information-of-the-feature", "Description": "", @@ -1097,12 +1117,13 @@ } }, { - "RelativeFolder": "Features\\04Background\\BackgroundFeature.feature", + "RelativeFolder": "Features/04Background/BackgroundFeature.feature", "Feature": { "Name": "Show the use of background", - "Description": "In order to show how to use the Background keyword of Gherkin \r\nAs a SpecFlow evanglist \r\nI want to show that background steps are called before any scenario step", + "Description": "In order to show how to use the Background keyword of Gherkin \nAs a SpecFlow evanglist \nI want to show that background steps are called before any scenario step", "FeatureElements": [ { + "Examples": [], "Name": "Add 1 to the sum", "Slug": "add-1-to-the-sum", "Description": "", @@ -1130,6 +1151,7 @@ } }, { + "Examples": [], "Name": "Add 2 to the sum", "Slug": "add-2-to-the-sum", "Description": "", @@ -1158,6 +1180,7 @@ } ], "Background": { + "Examples": [], "Name": "", "Description": "", "Steps": [ @@ -1197,12 +1220,13 @@ } }, { - "RelativeFolder": "Features\\05TablesAndAssist\\TableScenario.feature", + "RelativeFolder": "Features/05TablesAndAssist/TableScenario.feature", "Feature": { "Name": "Showing table usage", - "Description": "In order to show how to use tables \r\nAs a SpecFlow evanglist \r\nI want to write some simple scenarios that uses tables tables", + "Description": "In order to show how to use tables \nAs a SpecFlow evanglist \nI want to write some simple scenarios that uses tables tables", "FeatureElements": [ { + "Examples": [], "Name": "Using tables", "Slug": "using-tables", "Description": "", @@ -1281,6 +1305,7 @@ } }, { + "Examples": [], "Name": "Using tables with SpecFlow Assist", "Slug": "using-tables-with-specflow-assist", "Description": "", @@ -1359,6 +1384,7 @@ } }, { + "Examples": [], "Name": "Creating a entity from field value", "Slug": "creating-a-entity-from-field-value", "Description": "", @@ -1426,6 +1452,7 @@ } }, { + "Examples": [], "Name": "Example of a wide table", "Slug": "example-of-a-wide-table", "Description": "", @@ -1532,12 +1559,13 @@ } }, { - "RelativeFolder": "Features\\06CompareToAssist\\CompareTo.feature", + "RelativeFolder": "Features/06CompareToAssist/CompareTo.feature", "Feature": { "Name": "Show the compare to feature", - "Description": "In order to show the compare to features of SpecFlow Assist \r\nAs a SpecFlow evanglist \r\nI want to show how the different versions of compareTo works", + "Description": "In order to show the compare to features of SpecFlow Assist \nAs a SpecFlow evanglist \nI want to show how the different versions of compareTo works", "FeatureElements": [ { + "Examples": [], "Name": "CompareToInstance", "Slug": "comparetoinstance", "Description": "", @@ -1662,6 +1690,7 @@ } }, { + "Examples": [], "Name": "CompareToSet", "Slug": "comparetoset", "Description": "", @@ -1777,12 +1806,13 @@ } }, { - "RelativeFolder": "Features\\07Localization\\Svenska.feature", + "RelativeFolder": "Features/07Localization/Svenska.feature", "Feature": { "Name": "Svenska - Summering", - "Description": "För att slippa att göra dumma fel \r\nSom räknare \r\nVill jag kunna lägga summera", + "Description": "För att slippa att göra dumma fel \nSom räknare \nVill jag kunna lägga summera", "FeatureElements": [ { + "Examples": [], "Name": "Summera 5 och 7 ska vara 12", "Slug": "summera-5-och-7-ska-vara-12", "Description": "", @@ -1838,12 +1868,13 @@ } }, { - "RelativeFolder": "Features\\07Localization\\Vlaams.feature", + "RelativeFolder": "Features/07Localization/Vlaams.feature", "Feature": { "Name": "Test de Cultuur in het Vlaams", "Description": "", "FeatureElements": [ { + "Examples": [], "Name": "Het Scenario", "Slug": "het-scenario", "Description": "", @@ -1899,12 +1930,13 @@ } }, { - "RelativeFolder": "Features\\08AttributeOverloading\\AttributeOverloading.feature", + "RelativeFolder": "Features/08AttributeOverloading/AttributeOverloading.feature", "Feature": { "Name": "Attribute overloading", - "Description": "In order to show that steps can be used with multiple attributes \r\nAs a SpecFlow Evangelist \r\nI want to show that similar attributes can be applied to the same step definition", + "Description": "In order to show that steps can be used with multiple attributes \nAs a SpecFlow Evangelist \nI want to show that similar attributes can be applied to the same step definition", "FeatureElements": [ { + "Examples": [], "Name": "Checking number for evenness", "Slug": "checking-number-for-evenness", "Description": "", @@ -1981,12 +2013,13 @@ } }, { - "RelativeFolder": "Features\\09CallingStepsFromSteps\\CallingStepsFromSteps.feature", + "RelativeFolder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", "Feature": { "Name": "Calling Steps from StepDefinitions", - "Description": "In order to create steps of a higher abstraction \r\nAs a SpecFlow evangelist \r\nI want reuse other steps in my step definitions", + "Description": "In order to create steps of a higher abstraction \nAs a SpecFlow evangelist \nI want reuse other steps in my step definitions", "FeatureElements": [ { + "Examples": [], "Name": "Log in", "Slug": "log-in", "Description": "", @@ -2028,6 +2061,7 @@ } }, { + "Examples": [], "Name": "Do something meaningful", "Slug": "do-something-meaningful", "Description": "", @@ -2076,12 +2110,13 @@ } }, { - "RelativeFolder": "Features\\10StepTransformation\\StepTransformation.feature", + "RelativeFolder": "Features/10StepTransformation/StepTransformation.feature", "Feature": { "Name": "Step Argument Transformations", - "Description": "In order to reduce the amount of code and repetitive tasks in my steps \r\nAs a SpecFlow evanglist \r\nI want to define reusable transformations for my step arguments", + "Description": "In order to reduce the amount of code and repetitive tasks in my steps \nAs a SpecFlow evanglist \nI want to define reusable transformations for my step arguments", "FeatureElements": [ { + "Examples": [], "Name": "Steps with non-string arguments", "Slug": "steps-with-non-string-arguments", "Description": "", @@ -2130,12 +2165,13 @@ } }, { - "RelativeFolder": "Features\\11ContextInjection\\ContextInjection.feature", + "RelativeFolder": "Features/11ContextInjection/ContextInjection.feature", "Feature": { "Name": "Injecting context into step specifications", - "Description": "In order to don't have to rely on the global shared state\r\nand to be able to define the contexts required for each scenario. \r\nAs a SpecFlow Evanglist \r\nI would like to have the system automatically inject an instance of any class as\r\ndefined in the constructor of a step file", + "Description": "In order to don't have to rely on the global shared state\nand to be able to define the contexts required for each scenario. \nAs a SpecFlow Evanglist \nI would like to have the system automatically inject an instance of any class as\ndefined in the constructor of a step file", "FeatureElements": [ { + "Examples": [], "Name": "Feature with no context", "Slug": "feature-with-no-context", "Description": "", @@ -2163,6 +2199,7 @@ } }, { + "Examples": [], "Name": "Feature with a single context", "Slug": "feature-with-a-single-context", "Description": "", @@ -2190,6 +2227,7 @@ } }, { + "Examples": [], "Name": "Feature with multiple contexts", "Slug": "feature-with-multiple-contexts", "Description": "", @@ -2217,6 +2255,7 @@ } }, { + "Examples": [], "Name": "Feature with recursive contexts", "Slug": "feature-with-recursive-contexts", "Description": "", @@ -2251,6 +2290,7 @@ } }, { + "Examples": [], "Name": "Feature with a dependent context", "Slug": "feature-with-a-dependent-context", "Description": "", @@ -2299,12 +2339,13 @@ } }, { - "RelativeFolder": "Features\\12NestedFolders\\ChildFolder\\ChildChildFolder\\NestedFolderExample.feature", + "RelativeFolder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", "Feature": { "Name": "Nested Folder Example", - "Description": "In order to test nested folder output \r\nAs a silly contributer \r\nI want to create an example of something several folders deep", + "Description": "In order to test nested folder output \nAs a silly contributer \nI want to create an example of something several folders deep", "FeatureElements": [ { + "Examples": [], "Name": "Nested - Add two numbers", "Slug": "nested---add-two-numbers", "Description": "", @@ -2362,12 +2403,13 @@ } }, { - "RelativeFolder": "Features\\13MultilineText\\MultilineFeatureExample.feature", + "RelativeFolder": "Features/13MultilineText/MultilineFeatureExample.feature", "Feature": { "Name": "Multiline Feature Example", - "Description": "In order capture this particular Gherkin feature \r\nAs a Pickles contributer \r\nI want to demonstrate an example of using multiline text in a Scenario", + "Description": "In order capture this particular Gherkin feature \nAs a Pickles contributer \nI want to demonstrate an example of using multiline text in a Scenario", "FeatureElements": [ { + "Examples": [], "Name": "Mutliline Output", "Slug": "mutliline-output", "Description": "", @@ -2376,7 +2418,7 @@ "Keyword": "Given", "NativeKeyword": "Given ", "Name": "I have read in some text from the user", - "DocStringArgument": "This is line 1.\r\nThis is line 2!\r\nThis is line 3!!", + "DocStringArgument": "This is line 1.\nThis is line 2!\nThis is line 3!!", "StepComments": [], "AfterLastStepComments": [] }, @@ -2419,15 +2461,16 @@ } }, { - "RelativeFolder": "Features\\14MarkdownExample\\MarkdownExamples.feature", + "RelativeFolder": "Features/14MarkdownExample/MarkdownExamples.feature", "Feature": { "Name": "Sample Markdown Feature", - "Description": "# Header 1\r\n\r\n## Header 2\r\n\r\n### Header 3\r\n\r\n#### Header 4\r\n\r\n##### Header 5\r\n\r\n###### Header 6\r\n\r\nThis is a *significant* word\r\n\r\n1. Ordered #1\r\n2. Ordered #2\r\n3. Ordered #3\r\n\r\n- Unordered #1\r\n- Unordered #2\r\n- Unordered #3\r\n\r\nHorizontal Rule:\r\n- - -\r\n\r\nTable example:\r\n\r\n| First Header | Second Header |\r\n| ------------- | ------------- |\r\n| Content Cell | Content Cell |\r\n| Content Cell | Content Cell |\r\n\r\n- - -\r\n\r\nIncluding a picture: ![](./image.png)", + "Description": "# Header 1\n\n## Header 2\n\n### Header 3\n\n#### Header 4\n\n##### Header 5\n\n###### Header 6\n\nThis is a *significant* word\n\n1. Ordered #1\n2. Ordered #2\n3. Ordered #3\n\n- Unordered #1\n- Unordered #2\n- Unordered #3\n\nHorizontal Rule:\n- - -\n\nTable example:\n\n| First Header | Second Header |\n| ------------- | ------------- |\n| Content Cell | Content Cell |\n| Content Cell | Content Cell |\n\n- - -\n\nIncluding a picture: ![](./image.png)", "FeatureElements": [ { + "Examples": [], "Name": "Sample Markdown Scenario Example", "Slug": "sample-markdown-scenario-example", - "Description": "This is **important** text\r\n\r\nCode Block:\r\n\r\n```\r\nvar x = 2;\r\n```\r\n\r\nApple\r\n: Pomaceous fruit of plants of the genus Malus in\r\n the family Rosaceae.\r\n: An American computer company.\r\n\r\nOrange\r\n: The fruit of an evergreen tree of the genus Citrus.", + "Description": "This is **important** text\n\nCode Block:\n\n```\nvar x = 2;\n```\n\nApple\n: Pomaceous fruit of plants of the genus Malus in\n the family Rosaceae.\n: An American computer company.\n\nOrange\n: The fruit of an evergreen tree of the genus Citrus.", "Steps": [ { "Keyword": "Given", @@ -2479,7 +2522,7 @@ ], "Name": "Sample Markdown Scenario Outline Example", "Slug": "sample-markdown-scenario-outline-example", - "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\r\n\r\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", + "Description": "This is [an example link to pickles](https://github.com/picklesdoc/pickles/wiki \"Pickles\") inline link.\n\n[This link to pickles](https://github.com/picklesdoc/pickles/wiki) has no title attribute.", "Steps": [ { "Keyword": "Given", @@ -2507,6 +2550,7 @@ } ], "Background": { + "Examples": [], "Name": "", "Description": "This is the *coolest* background", "Steps": [ @@ -2546,12 +2590,13 @@ } }, { - "RelativeFolder": "Features\\15Pickles\\InteractiveDHTMLView.feature", + "RelativeFolder": "Features/15Pickles/InteractiveDHTMLView.feature", "Feature": { "Name": "Interactive DHTML View", - "Description": "In order to increase stakeholder engagement with pickled specs \r\nAs a SpecFlow evangelist \r\nI want to adjust the level of detail in the DHTML view to suite my audience \r\nSo that I do not overwhelm them.", + "Description": "In order to increase stakeholder engagement with pickled specs \nAs a SpecFlow evangelist \nI want to adjust the level of detail in the DHTML view to suite my audience \nSo that I do not overwhelm them.", "FeatureElements": [ { + "Examples": [], "Name": "Scenario with large data table", "Slug": "scenario-with-large-data-table", "Description": "", @@ -2696,12 +2741,13 @@ } }, { - "RelativeFolder": "Features\\15Pickles\\NotTestedAutomatedManualTags.feature", + "RelativeFolder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Feature": { "Name": "Kinds of verification", - "Description": "In order to increase stakeholder engagement with pickled specs\r\nAs a SpecFlow evangelist\r\nI want to make clear how many scenarios are automated, manually tested and not tested\r\nSo that the stakeholders have a better overview of progress", + "Description": "In order to increase stakeholder engagement with pickled specs\nAs a SpecFlow evangelist\nI want to make clear how many scenarios are automated, manually tested and not tested\nSo that the stakeholders have a better overview of progress", "FeatureElements": [ { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2738,6 +2784,7 @@ } }, { + "Examples": [], "Name": "Verified manually", "Slug": "verified-manually", "Description": "", @@ -2774,6 +2821,7 @@ } }, { + "Examples": [], "Name": "Verified automatically", "Slug": "verified-automatically", "Description": "", @@ -2824,12 +2872,13 @@ } }, { - "RelativeFolder": "Features\\Arithmetic.feature", + "RelativeFolder": "Features/Arithmetic.feature", "Feature": { "Name": "Arithmetic", - "Description": "In order to avoid silly mistakes \r\nAs a math idiot \r\nI want to be able to perform arithmetic on the calculator\r\n\r\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\r\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", + "Description": "In order to avoid silly mistakes \nAs a math idiot \nI want to be able to perform arithmetic on the calculator\n\nWhen $a \\ne 0$, there are two solutions to $\\(ax^2 + bx + c = 0\\)$ and they are\n$$x = {-b \\pm \\sqrt{b^2-4ac} \\over 2a}.$$", "FeatureElements": [ { + "Examples": [], "Name": "Add two numbers", "Slug": "add-two-numbers", "Description": "$50 + 70 = 120$", @@ -2878,6 +2927,7 @@ } }, { + "Examples": [], "Name": "Subtract two numbers", "Slug": "subtract-two-numbers", "Description": "", @@ -2922,6 +2972,7 @@ } }, { + "Examples": [], "Name": "Multiply two numbers", "Slug": "multiply-two-numbers", "Description": "", @@ -2966,6 +3017,7 @@ } }, { + "Examples": [], "Name": "Divide two numbers", "Slug": "divide-two-numbers", "Description": "", @@ -3024,12 +3076,13 @@ } }, { - "RelativeFolder": "Features\\Trigonometry.feature", + "RelativeFolder": "Features/Trigonometry.feature", "Feature": { "Name": "Trigonometry", - "Description": "In order to avoid perform more advanced calculations \r\nAs a math idiot \r\nI want to be able to use trigonometric functions", + "Description": "In order to avoid perform more advanced calculations \nAs a math idiot \nI want to be able to use trigonometric functions", "FeatureElements": [ { + "Examples": [], "Name": "Sine", "Slug": "sine", "Description": "", @@ -3067,6 +3120,7 @@ } }, { + "Examples": [], "Name": "Cosine", "Slug": "cosine", "Description": "", @@ -3104,6 +3158,7 @@ } }, { + "Examples": [], "Name": "Tangent", "Slug": "tangent", "Description": "", @@ -3155,12 +3210,13 @@ } }, { - "RelativeFolder": "Features\\Workflow\\ClearingScreen.feature", + "RelativeFolder": "Features/Workflow/ClearingScreen.feature", "Feature": { "Name": "Clearing Screen", - "Description": "In order to restart a new set of calculations \r\nAs a math idiot \r\nI want to be able to clear the screen", + "Description": "In order to restart a new set of calculations \nAs a math idiot \nI want to be able to clear the screen", "FeatureElements": [ { + "Examples": [], "Name": "Clear the screen", "Slug": "clear-the-screen", "Description": "", @@ -3364,20 +3420,342 @@ ], "Folders": [ { - "Folder": "Features", - "Total": 57, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, "Passing": 0, "Failing": 0, - "Inconclusive": 57 + "Inconclusive": 1 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Passing": 0, + "Failing": 0, + "Inconclusive": 5 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Passing": 0, + "Failing": 0, + "Inconclusive": 2 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Passing": 0, + "Failing": 0, + "Inconclusive": 4 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Passing": 0, + "Failing": 0, + "Inconclusive": 3 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Passing": 0, + "Failing": 0, + "Inconclusive": 1 } ], "NotTestedFolders": [ { - "Folder": "Features", + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", "Total": 1, "Passing": 0, "Failing": 0, "Inconclusive": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 0, + "Passing": 0, + "Failing": 0, + "Inconclusive": 0 } ], "Scenarios": { @@ -3394,17 +3772,178 @@ }, "FoldersWithTestKinds": [ { - "Folder": "Features", - "Total": 57, - "Automated": 55, + "Folder": "Features/00BasicGherkin/BasicGherkin.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/01TestRunner/TestRunnerIsNotImportant.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/Hooks.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/02TagsAndHooks/TagDemo.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/03ScenarioOutline/ScenarioOutline.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/031ScenarioContext/ScenarioContext.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/032FeatureContext/FeatureContextFeatures.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/04Background/BackgroundFeature.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/05TablesAndAssist/TableScenario.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/06CompareToAssist/CompareTo.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Svenska.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/07Localization/Vlaams.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/08AttributeOverloading/AttributeOverloading.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/09CallingStepsFromSteps/CallingStepsFromSteps.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/10StepTransformation/StepTransformation.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/11ContextInjection/ContextInjection.feature", + "Total": 5, + "Automated": 5, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/12NestedFolders/ChildFolder/ChildChildFolder/NestedFolderExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/13MultilineText/MultilineFeatureExample.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/14MarkdownExample/MarkdownExamples.feature", + "Total": 2, + "Automated": 2, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/InteractiveDHTMLView.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/15Pickles/NotTestedAutomatedManualTags.feature", + "Total": 3, + "Automated": 1, "Manual": 1, "NotTested": 1 + }, + { + "Folder": "Features/Arithmetic.feature", + "Total": 4, + "Automated": 4, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Trigonometry.feature", + "Total": 3, + "Automated": 3, + "Manual": 0, + "NotTested": 0 + }, + { + "Folder": "Features/Workflow/ClearingScreen.feature", + "Total": 1, + "Automated": 1, + "Manual": 0, + "NotTested": 0 } ] }, "Configuration": { "SutName": "Pickles", - "SutVersion": "2.3.3", - "GeneratedOn": "11 March 2021 17:02:55" + "SutVersion": "3.0.1", + "GeneratedOn": "4 October 2021 17:16:11" } } \ No newline at end of file diff --git a/docs/Output/Markdown/fail.png b/docs/Output/Markdown/fail.png index 0e749af87..a5fcbf8f0 100644 Binary files a/docs/Output/Markdown/fail.png and b/docs/Output/Markdown/fail.png differ diff --git a/docs/Output/Markdown/features.md b/docs/Output/Markdown/features.md index f5d1061f3..f28062580 100644 --- a/docs/Output/Markdown/features.md +++ b/docs/Output/Markdown/features.md @@ -1,6 +1,6 @@ # Features -Generated on: 11 March 2021 at 17:02:55 +Generated on: 04 October 2021 at 17:16:12 ### Showing basic gherkin syntax @@ -162,7 +162,7 @@ As a SpecFlow evangelist I want to show how to use ScenarioOutline -#### Scenario Outline: Add two positive numbers with many examples +#### Scenario: Add two positive numbers with many examples > > **Given** I enter \ into the calculator > @@ -187,7 +187,7 @@ I want to show how to use ScenarioOutline > | 100 | 20 | 120 | > | 1000 | 20 | 1020 | > -#### Scenario Outline: Add two negative numbers with many examples +#### Scenario: Add two negative numbers with many examples > > **Given** I enter \ into the calculator > @@ -732,7 +732,7 @@ Including a picture: ![](./image.png) > *`@AddingATag`* -#### Scenario Outline: Sample Markdown Scenario Outline Example +#### Scenario: Sample Markdown Scenario Outline Example > > **Given** this: \ > diff --git a/docs/Output/Markdown/inconclusive.png b/docs/Output/Markdown/inconclusive.png index 951e767bc..babb6f040 100644 Binary files a/docs/Output/Markdown/inconclusive.png and b/docs/Output/Markdown/inconclusive.png differ diff --git a/docs/Output/Markdown/pass.png b/docs/Output/Markdown/pass.png index 753723a7a..7635df654 100644 Binary files a/docs/Output/Markdown/pass.png and b/docs/Output/Markdown/pass.png differ diff --git a/docs/Output/Word/Pickles.docx b/docs/Output/Word/Pickles.docx index 70fc77c2b..0746da218 100644 Binary files a/docs/Output/Word/Pickles.docx and b/docs/Output/Word/Pickles.docx differ diff --git a/docs/Output/Word/features.docx b/docs/Output/Word/features.docx deleted file mode 100644 index b3712d75d..000000000 Binary files a/docs/Output/Word/features.docx and /dev/null differ diff --git a/docs/index.html b/docs/index.html index 3d4f0bbee..32b12ffb0 100644 --- a/docs/index.html +++ b/docs/index.html @@ -159,7 +159,7 @@

            Download

          - If you prefer to download the .zip files, you can so from the Github release page. + If you prefer to download the .zip files, you can so from the Github release page.

          - - diff --git a/test-harness/AutomationLayer/AutomationLayer.csproj b/test-harness/AutomationLayer/AutomationLayer.csproj deleted file mode 100644 index 5b5403876..000000000 --- a/test-harness/AutomationLayer/AutomationLayer.csproj +++ /dev/null @@ -1,72 +0,0 @@ - - - - - Debug - AnyCPU - {073862DE-D599-4941-9716-03206CF1CFA2} - Library - Properties - AutomationLayer - AutomationLayer - v4.5 - 512 - ..\ - true - - - - true - full - false - bin\Debug\ - DEBUG;TRACE - prompt - 4 - false - - - pdbonly - true - bin\Release\ - TRACE - prompt - 4 - false - - - - ..\packages\NFluent.1.3.1.0\lib\net40\NFluent.dll - True - - - - - - - - - - ..\packages\SpecFlow.1.9.0\lib\net35\TechTalk.SpecFlow.dll - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/AutomationLayer/MarkTestAs.cs b/test-harness/AutomationLayer/MarkTestAs.cs deleted file mode 100644 index e1362542a..000000000 --- a/test-harness/AutomationLayer/MarkTestAs.cs +++ /dev/null @@ -1,23 +0,0 @@ -using NFluent; -using TechTalk.SpecFlow; - -namespace AutomationLayer -{ - public static class MarkTestAs - { - internal static void Inconclusive() - { - ScenarioContext.Current.Pending(); - } - - internal static void Failing() - { - Check.That(true).IsEqualTo(false); - } - - internal static void Passing() - { - // nothing to be done - } - } -} \ No newline at end of file diff --git a/test-harness/AutomationLayer/MinimalFeatures/MinimalSteps.cs b/test-harness/AutomationLayer/MinimalFeatures/MinimalSteps.cs deleted file mode 100644 index a06608c03..000000000 --- a/test-harness/AutomationLayer/MinimalFeatures/MinimalSteps.cs +++ /dev/null @@ -1,27 +0,0 @@ -using System; -using TechTalk.SpecFlow; - -namespace AutomationLayer.MinimalFeatures -{ - [Binding] - public class MinimalSteps - { - [Then(@"passing step")] - public void ThenPassingStep() - { - MarkTestAs.Passing(); - } - - [Then(@"inconclusive step")] - public void ThenInconclusiveStep() - { - MarkTestAs.Inconclusive(); - } - - [Then(@"failing step")] - public void ThenFailingStep() - { - MarkTestAs.Failing(); - } - } -} diff --git a/test-harness/AutomationLayer/Properties/AssemblyInfo.cs b/test-harness/AutomationLayer/Properties/AssemblyInfo.cs deleted file mode 100644 index 72c946d96..000000000 --- a/test-harness/AutomationLayer/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,36 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("AutomationLayer")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("AIM Software")] -[assembly: AssemblyProduct("AutomationLayer")] -[assembly: AssemblyCopyright("Copyright © AIM Software 2013")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM components. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("f91ae381-e0a7-4360-85ea-ff5ee05745a7")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Build and Revision Numbers -// by using the '*' as shown below: -// [assembly: AssemblyVersion("1.0.*")] -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/test-harness/AutomationLayer/ScenarioOutlineSteps.cs b/test-harness/AutomationLayer/ScenarioOutlineSteps.cs deleted file mode 100644 index 02f5fa669..000000000 --- a/test-harness/AutomationLayer/ScenarioOutlineSteps.cs +++ /dev/null @@ -1,51 +0,0 @@ -using System; - -using TechTalk.SpecFlow; - -namespace AutomationLayer -{ - [Binding] - public class ScenarioOutlineSteps - { - [Then(@"the scenario will '(.*)'")] - public void ThenTheScenarioWill(string result) - { - if (result.ToUpperInvariant().StartsWith("PASS")) - { - MarkTestAs.Passing(); - } - else if (result.ToUpperInvariant().StartsWith("FAIL")) - { - MarkTestAs.Failing(); - } - else - { - MarkTestAs.Inconclusive(); - } - } - - [When(@"I have special characters for regexes in the value, for example a '(.*)'")] - public void WhenIHaveSpecialCharactersForRegexesInTheValueForExampleARegex(string regex) - { - // nothing to be done - } - - [When(@"I have backslashes in the value, for example a '(.*)'")] - public void WhenIHaveBackslashesInTheValueForExampleAFilePath(string filePath) - { - // nothing to be done - } - - [When(@"I have parenthesis in the value, for example an '(.*)'")] - public void WhenIHaveParenthesisInTheValueForExampleAnOverlyDescriptiveField(string description) - { - // nothing to be done - test case requires pass - } - - [When(@"I have a field with value '(.*)'")] - public void WhenIHaveAFieldWithValue(string value) - { - // nothing to be done - test case requires pass - } - } -} diff --git a/test-harness/AutomationLayer/packages.config b/test-harness/AutomationLayer/packages.config deleted file mode 100644 index 80d6da8c6..000000000 --- a/test-harness/AutomationLayer/packages.config +++ /dev/null @@ -1,5 +0,0 @@ - - - - - \ No newline at end of file diff --git a/test-harness/Cucumber/features/Addition.feature b/test-harness/Cucumber/features/Addition.feature deleted file mode 100644 index b1aee1f37..000000000 --- a/test-harness/Cucumber/features/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/Cucumber/features/FailingBackground.feature b/test-harness/Cucumber/features/FailingBackground.feature deleted file mode 100644 index 99c245fdc..000000000 --- a/test-harness/Cucumber/features/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/Cucumber/features/Minimal Features/Failing.feature b/test-harness/Cucumber/features/Minimal Features/Failing.feature deleted file mode 100644 index cfea2ed25..000000000 --- a/test-harness/Cucumber/features/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step diff --git a/test-harness/Cucumber/features/Minimal Features/Inconclusive.feature b/test-harness/Cucumber/features/Minimal Features/Inconclusive.feature deleted file mode 100644 index ee594c98b..000000000 --- a/test-harness/Cucumber/features/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step diff --git a/test-harness/Cucumber/features/Minimal Features/Passing.feature b/test-harness/Cucumber/features/Minimal Features/Passing.feature deleted file mode 100644 index 0aa8f7625..000000000 --- a/test-harness/Cucumber/features/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/Cucumber/features/NotAutomatedAtAll.feature b/test-harness/Cucumber/features/NotAutomatedAtAll.feature deleted file mode 100644 index 2e0911aa6..000000000 --- a/test-harness/Cucumber/features/NotAutomatedAtAll.feature +++ /dev/null @@ -1,19 +0,0 @@ -Feature: Not Automated At All - -Background: - Given unimplemented step - -Scenario: Not automated scenario 1 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 2 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 3 - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/Cucumber/features/ScenarioOutlines.feature b/test-harness/Cucumber/features/ScenarioOutlines.feature deleted file mode 100644 index 978703172..000000000 --- a/test-harness/Cucumber/features/ScenarioOutlines.feature +++ /dev/null @@ -1,143 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - -Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - And I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - - Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - - Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - - Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - - Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | diff --git a/test-harness/Cucumber/features/ScenariosWithSpecialCharacters.feature b/test-harness/Cucumber/features/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index 07807bd7e..000000000 --- a/test-harness/Cucumber/features/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,53 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'pass_1' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This is a scenario outline with ampersand & - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step diff --git a/test-harness/Cucumber/features/step_definitions/AdditionSteps.rb b/test-harness/Cucumber/features/step_definitions/AdditionSteps.rb deleted file mode 100644 index 6de34b066..000000000 --- a/test-harness/Cucumber/features/step_definitions/AdditionSteps.rb +++ /dev/null @@ -1,30 +0,0 @@ -Given(/^the calculator has clean memory$/) do - @result = 0 - @numbersList = [] -end - -Given(/^I have entered (\d+) into the calculator$/) do |arg1| - @numbersList << arg1.to_i -end - -Given(/^I have entered (\d+)\.(\d+) into the calculator$/) do |arg1, arg2| - expect("this is a hacky way of making the scenario with a non-integer number").to eql("fail") -end - -When(/^I press add$/) do - @numbersList.each do |number| - @result = @result + number - end -end - -Then(/^the result should be (\d+) on the screen$/) do |arg1| - expect(@result).to eql(arg1.to_i) -end - -Then(/^the result should be (\d+)\.(\d+) on the screen$/) do |arg1, arg2| - expect("this is a hacky way of making the scenario with a non-integer number").to eql("fail") -end - -Given(/^the background step fails$/) do - expect("true").to eql("false") -end diff --git a/test-harness/Cucumber/features/step_definitions/MinimalSteps.rb b/test-harness/Cucumber/features/step_definitions/MinimalSteps.rb deleted file mode 100644 index 29693dfa4..000000000 --- a/test-harness/Cucumber/features/step_definitions/MinimalSteps.rb +++ /dev/null @@ -1,11 +0,0 @@ -Then(/^passing step$/) do - # Nothing to be done here -end - -Then(/^inconclusive step$/) do - pending # We want pending here -end - -Then(/^failing step$/) do - expect("true").to eql("false") -end diff --git a/test-harness/Cucumber/features/step_definitions/ScenarioOutlineSteps.rb b/test-harness/Cucumber/features/step_definitions/ScenarioOutlineSteps.rb deleted file mode 100644 index 36ccc28d8..000000000 --- a/test-harness/Cucumber/features/step_definitions/ScenarioOutlineSteps.rb +++ /dev/null @@ -1,39 +0,0 @@ -Then(/^the scenario will 'pass_(\d+)'$/) do |arg1| - # Nothing to be done here -end - -Then(/^the scenario will 'inconclusive_(\d+)'$/) do |arg1| - pending # We want pending here -end - -Then(/^the scenario will 'fail_(\d+)'$/) do |arg1| - expect("true").to eql("false") -end - -Then(/^the scenario will 'pass'$/) do - # Nothing to be done here -end - -Then(/^the scenario will 'inconclusive'$/) do - pending # We want pending here -end - -Then(/^the scenario will 'fail'$/) do - expect("true").to eql("false") -end - -When(/^I have backslashes in the value, for example a 'c:\\Temp\\'$/) do - # Nothing to be done here -end - -When(/^I have parenthesis in the value, for example an '(.*)'$/) do |arg1| - #Nothing to be done here -end - -When(/^I have special characters for regexes in the value, for example a '(.*)'$/) do |arg1| - #Nothing to be done here -end - -When(/^I have a field with value '(.*)'$/) do |arg1| - #Nothing to be done here -end diff --git a/test-harness/Cucumber/features/support/env.rb b/test-harness/Cucumber/features/support/env.rb deleted file mode 100644 index ac66ee5f3..000000000 --- a/test-harness/Cucumber/features/support/env.rb +++ /dev/null @@ -1 +0,0 @@ -require 'rspec/expectations' diff --git a/test-harness/CucumberJS/features/Addition.feature b/test-harness/CucumberJS/features/Addition.feature deleted file mode 100644 index b1aee1f37..000000000 --- a/test-harness/CucumberJS/features/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/CucumberJS/features/FailingBackground.feature b/test-harness/CucumberJS/features/FailingBackground.feature deleted file mode 100644 index 99c245fdc..000000000 --- a/test-harness/CucumberJS/features/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/CucumberJS/features/Minimal Features/Failing.feature b/test-harness/CucumberJS/features/Minimal Features/Failing.feature deleted file mode 100644 index cfea2ed25..000000000 --- a/test-harness/CucumberJS/features/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step diff --git a/test-harness/CucumberJS/features/Minimal Features/Inconclusive.feature b/test-harness/CucumberJS/features/Minimal Features/Inconclusive.feature deleted file mode 100644 index ee594c98b..000000000 --- a/test-harness/CucumberJS/features/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step diff --git a/test-harness/CucumberJS/features/Minimal Features/Passing.feature b/test-harness/CucumberJS/features/Minimal Features/Passing.feature deleted file mode 100644 index 0aa8f7625..000000000 --- a/test-harness/CucumberJS/features/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/CucumberJS/features/NotAutomatedAtAll.feature b/test-harness/CucumberJS/features/NotAutomatedAtAll.feature deleted file mode 100644 index 2e0911aa6..000000000 --- a/test-harness/CucumberJS/features/NotAutomatedAtAll.feature +++ /dev/null @@ -1,19 +0,0 @@ -Feature: Not Automated At All - -Background: - Given unimplemented step - -Scenario: Not automated scenario 1 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 2 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 3 - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/CucumberJS/features/ScenarioOutlines.feature b/test-harness/CucumberJS/features/ScenarioOutlines.feature deleted file mode 100644 index 978703172..000000000 --- a/test-harness/CucumberJS/features/ScenarioOutlines.feature +++ /dev/null @@ -1,143 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - -Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - And I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - - Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - - Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - - Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - - Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | diff --git a/test-harness/CucumberJS/features/ScenariosWithSpecialCharacters.feature b/test-harness/CucumberJS/features/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index 07807bd7e..000000000 --- a/test-harness/CucumberJS/features/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,53 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'pass_1' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This is a scenario outline with ampersand & - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step diff --git a/test-harness/CucumberJS/features/stepdefinitions/AdditionSteps.js b/test-harness/CucumberJS/features/stepdefinitions/AdditionSteps.js deleted file mode 100644 index 49e22cc0d..000000000 --- a/test-harness/CucumberJS/features/stepdefinitions/AdditionSteps.js +++ /dev/null @@ -1,39 +0,0 @@ -'use strict'; - -var Calculator = require(process.cwd() + '/script/model/calculator'); -var assert = require('assert'); -var {defineSupportCode} = require('cucumber'); - -defineSupportCode(function({Given, When, Then}) { - var myCalculator; - - Given(/^the calculator has clean memory$/, function (callback) { - myCalculator = Calculator.create(); - callback(); - }); - - Given(/^I have entered (.*) into the calculator$/, function (firstNumber, callback) { - myCalculator.enter(firstNumber); - callback(); - }); - - Given(/^I have entered (\d+)\.(\d+) into the calculator$/, function (firstNumber, secondNumber, callback) { - assert.equal("this is a hacky way of making the scenario with a non-integer number", "fail"); - callback(); - }); - - When(/^I press add$/, function (callback) { - myCalculator.add(); - callback(); - }); - - Then(/^the result should be (.*) on the screen$/, function (arg1, callback) { - assert.equal(myCalculator.result, parseInt(arg1)); - callback(); - }); - - Given(/^the background step fails$/, function (callback) { - assert.equal("true", "false"); - callback(); - }); -}); diff --git a/test-harness/CucumberJS/features/stepdefinitions/MinimalSteps.js b/test-harness/CucumberJS/features/stepdefinitions/MinimalSteps.js deleted file mode 100644 index 2205b3bd9..000000000 --- a/test-harness/CucumberJS/features/stepdefinitions/MinimalSteps.js +++ /dev/null @@ -1,25 +0,0 @@ -'use strict'; - -var assert = require('assert'); -var {defineSupportCode} = require('cucumber'); - -defineSupportCode(function({Then}) { - - Then(/^passing step$/, - function(callback) { - // nothing to be done here - callback(); - }); - - Then(/^inconclusive step$/, - function(callback) { - // we want pending here - callback(null, 'pending'); - }); - - Then(/^failing step$/, - function(callback) { - assert.equal("true", "false"); - callback(); - }); -}); diff --git a/test-harness/CucumberJS/features/stepdefinitions/ScenarioOutlineSteps.js b/test-harness/CucumberJS/features/stepdefinitions/ScenarioOutlineSteps.js deleted file mode 100644 index 952de564b..000000000 --- a/test-harness/CucumberJS/features/stepdefinitions/ScenarioOutlineSteps.js +++ /dev/null @@ -1,57 +0,0 @@ -'use strict'; - -var assert = require('assert'); -var {defineSupportCode} = require('cucumber'); - -defineSupportCode(function({Then, When}) { - - Then(/^the scenario will 'pass_(\d+)'$/, function (result, callback) { - // nothing to be done here - callback(); - }); - - Then(/^the scenario will 'inconclusive_(\d+)'$/, function (result, callback) { - // we want pending here - callback(null, 'pending'); - }); - - Then(/^the scenario will 'fail_(\d+)'$/, function (result, callback) { - assert.equal("true", "false"); - callback(); - }); - - Then(/^the scenario will 'pass'$/, function (callback) { - // nothing to be done here - callback(); - }); - - Then(/^the scenario will 'inconclusive'$/, function (callback) { - // we want pending here - callback(null, 'pending'); - }); - - Then(/^the scenario will 'fail'$/, function (callback) { - assert.equal("true", "false"); - callback(); - }); - - When(/^I have backslashes in the value, for example a '(.*)'$/, function (filePath, callback) { - // nothing to be done here - callback(); - }); - - When(/^I have parenthesis in the value, for example an '(.*)'$/, function (description, callback) { - // nothing to be done here - callback(); - }); - - When(/^I have special characters for regexes in the value, for example a '(.*)'$/, function (description, callback) { - // nothing to be done here - callback(); - }); - - When(/^I have a field with value '(.*)'$/, function name(value, callback) { - // nothing to be done here - callback(); - }); -}); diff --git a/test-harness/CucumberJS/script/model/calculator.js b/test-harness/CucumberJS/script/model/calculator.js deleted file mode 100644 index 060abaaca..000000000 --- a/test-harness/CucumberJS/script/model/calculator.js +++ /dev/null @@ -1,26 +0,0 @@ -'use strict'; - -var calculator = { - enter: function(item) { - this.list.push(parseInt(item)); - }, - add: function() { - var index; - for (index = 0; index < this.list.length; index++) { - this.result = this.result + this.list[index]; - } - }, -}; - -module.exports = { - create: function() { - return Object.create(calculator, { - 'list': { - value: [], - writable: false, - enumerable: true - }, - 'result': { value: 0, writable: true } - }); - } -}; diff --git a/test-harness/MsTest/Addition.feature b/test-harness/MsTest/Addition.feature deleted file mode 100644 index 238e261e9..000000000 --- a/test-harness/MsTest/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/MsTest/Addition.feature.cs b/test-harness/MsTest/Addition.feature.cs deleted file mode 100644 index b5aed87e7..000000000 --- a/test-harness/MsTest/Addition.feature.cs +++ /dev/null @@ -1,229 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class AdditionFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Addition.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Addition", "In order to avoid silly mistakes\r\nAs a math idiot\r\nI want to be told the sum of t" + - "wo numbers", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Addition"))) - { - Pickles.TestHarness.MsTest.AdditionFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 6 -#line 7 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - string[] @__tags = new string[] { - "tag2"}; - if ((exampleTags != null)) - { - @__tags = System.Linq.Enumerable.ToArray(System.Linq.Enumerable.Concat(@__tags, exampleTags)); - } - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", @__tags); -#line 10 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 11 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 12 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 13 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 14 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 15 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Adding several numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Addition")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCategoryAttribute("tag2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "60")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:first number", "60")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:second number", "70")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:third number", "130")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "260")] - public virtual void AddingSeveralNumbers_60() - { - this.AddingSeveralNumbers("60", "70", "130", "260", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Adding several numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Addition")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCategoryAttribute("tag2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "40")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:first number", "40")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:second number", "50")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:third number", "90")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "180")] - public virtual void AddingSeveralNumbers_40() - { - this.AddingSeveralNumbers("40", "50", "90", "180", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Add two numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Addition")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCategoryAttribute("tag1")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", new string[] { - "tag1"}); -#line 23 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 24 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 25 - testRunner.And("I have entered 2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 26 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 27 - testRunner.Then("the result should be 3 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Fail to add two numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Addition")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCategoryAttribute("tag1")] - public virtual void FailToAddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Fail to add two numbers", new string[] { - "tag1"}); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 31 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 32 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 33 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 34 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Ignored adding two numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Addition")] - [Microsoft.VisualStudio.TestTools.UnitTesting.IgnoreAttribute()] - public virtual void IgnoredAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Ignored adding two numbers", new string[] { - "ignore"}); -#line 37 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 38 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 39 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 40 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 41 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Not automated adding two numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Addition")] - public virtual void NotAutomatedAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated adding two numbers", ((string[])(null))); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 44 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 45 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 46 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/App.config b/test-harness/MsTest/App.config deleted file mode 100644 index a44d679c3..000000000 --- a/test-harness/MsTest/App.config +++ /dev/null @@ -1,13 +0,0 @@ - - - -
          - - - - - - - - - diff --git a/test-harness/MsTest/FailingBackground.feature b/test-harness/MsTest/FailingBackground.feature deleted file mode 100644 index 83a70483a..000000000 --- a/test-harness/MsTest/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/MsTest/FailingBackground.feature.cs b/test-harness/MsTest/FailingBackground.feature.cs deleted file mode 100644 index b8dd97c5a..000000000 --- a/test-harness/MsTest/FailingBackground.feature.cs +++ /dev/null @@ -1,152 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class FailingBackgroundFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "FailingBackground.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing Background", "This feature has a failing background.", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Failing Background"))) - { - Pickles.TestHarness.MsTest.FailingBackgroundFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the background step fails", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 6 - testRunner.And("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line hidden - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Add two numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Failing Background")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", ((string[])(null))); -#line 8 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 9 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 10 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 11 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 12 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 16 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 17 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 18 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Adding several numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Failing Background")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "60")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:first number", "60")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:second number", "70")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:third number", "130")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "260")] - public virtual void AddingSeveralNumbers_60() - { - this.AddingSeveralNumbers("60", "70", "130", "260", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Adding several numbers")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Failing Background")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "40")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:first number", "40")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:second number", "50")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:third number", "90")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "180")] - public virtual void AddingSeveralNumbers_40() - { - this.AddingSeveralNumbers("40", "50", "90", "180", ((string[])(null))); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/Minimal Features/Failing.feature b/test-harness/MsTest/Minimal Features/Failing.feature deleted file mode 100644 index d7c5b7f53..000000000 --- a/test-harness/MsTest/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step \ No newline at end of file diff --git a/test-harness/MsTest/Minimal Features/Failing.feature.cs b/test-harness/MsTest/Minimal Features/Failing.feature.cs deleted file mode 100644 index 2184a702a..000000000 --- a/test-harness/MsTest/Minimal Features/Failing.feature.cs +++ /dev/null @@ -1,115 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class FailingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Failing.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Failing"))) - { - Pickles.TestHarness.MsTest.MinimalFeatures.FailingFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Failing Feature Passing Scenario")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Failing")] - public virtual void FailingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Failing Feature Inconclusive Scenario")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Failing")] - public virtual void FailingFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Failing Feature Failing Scenario")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Failing")] - public virtual void FailingFeatureFailingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Failing Scenario", ((string[])(null))); -#line 9 -this.ScenarioSetup(scenarioInfo); -#line 10 - testRunner.Then("failing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/Minimal Features/Inconclusive.feature b/test-harness/MsTest/Minimal Features/Inconclusive.feature deleted file mode 100644 index 7ce63f2d5..000000000 --- a/test-harness/MsTest/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step \ No newline at end of file diff --git a/test-harness/MsTest/Minimal Features/Inconclusive.feature.cs b/test-harness/MsTest/Minimal Features/Inconclusive.feature.cs deleted file mode 100644 index 5d211b93b..000000000 --- a/test-harness/MsTest/Minimal Features/Inconclusive.feature.cs +++ /dev/null @@ -1,101 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class InconclusiveFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Inconclusive.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Inconclusive", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Inconclusive"))) - { - Pickles.TestHarness.MsTest.MinimalFeatures.InconclusiveFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Inconclusive Feature Passing Scenario")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Inconclusive")] - public virtual void InconclusiveFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Inconclusive Feature Inconclusive Scenario")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Inconclusive")] - public virtual void InconclusiveFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/Minimal Features/Passing.feature b/test-harness/MsTest/Minimal Features/Passing.feature deleted file mode 100644 index 14bf35e22..000000000 --- a/test-harness/MsTest/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/MsTest/Minimal Features/Passing.feature.cs b/test-harness/MsTest/Minimal Features/Passing.feature.cs deleted file mode 100644 index c1bcb807e..000000000 --- a/test-harness/MsTest/Minimal Features/Passing.feature.cs +++ /dev/null @@ -1,87 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class PassingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Passing.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Passing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Passing"))) - { - Pickles.TestHarness.MsTest.MinimalFeatures.PassingFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Passing Feature Passing Scenario")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Passing")] - public virtual void PassingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Passing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/MsTest.csproj b/test-harness/MsTest/MsTest.csproj deleted file mode 100644 index c2d14aadb..000000000 --- a/test-harness/MsTest/MsTest.csproj +++ /dev/null @@ -1,172 +0,0 @@ - - - - Debug - AnyCPU - {0DBA6FCA-5D66-4187-932D-64B55D67E287} - Library - Properties - Pickles.TestHarness.MsTest - MsTestHarness - v4.5 - 512 - {3AC096D0-A1C2-E12C-1390-A8335801FDAB};{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC} - 10.0 - $(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v$(VisualStudioVersion) - $(ProgramFiles)\Common Files\microsoft shared\VSTT\$(VisualStudioVersion)\UITestExtensionPackages - False - UnitTest - ..\ - true - - - true - full - false - bin\Debug\ - DEBUG;TRACE - prompt - 4 - - - pdbonly - true - bin\Release\ - TRACE - prompt - 4 - - - - - ..\packages\SpecFlow.1.9.0\lib\net35\TechTalk.SpecFlow.dll - - - - - - - - - - - - - - - - - Addition.feature - True - True - - - True - True - FailingBackground.feature - - - True - True - Failing.feature - - - True - True - Inconclusive.feature - - - NotAutomatedAtAll.feature - True - True - - - True - True - Passing.feature - - - - ScenarioOutlines.feature - True - True - - - - True - True - ScenariosWithSpecialCharacters.feature - - - - - SpecFlowSingleFileGenerator - Addition.feature.cs - - - - SpecFlowSingleFileGenerator - FailingBackground.feature.cs - - - SpecFlowSingleFileGenerator - Failing.feature.cs - - - SpecFlowSingleFileGenerator - Inconclusive.feature.cs - - - SpecFlowSingleFileGenerator - NotAutomatedAtAll.feature.cs - - - Designer - - - SpecFlowSingleFileGenerator - Passing.feature.cs - - - SpecFlowSingleFileGenerator - ScenarioOutlines.feature.cs - - - SpecFlowSingleFileGenerator - ScenariosWithSpecialCharacters.feature.cs - - - - - {073862de-d599-4941-9716-03206cf1cfa2} - AutomationLayer - - - - - - - False - - - False - - - False - - - False - - - - - - - - \ No newline at end of file diff --git a/test-harness/MsTest/NotAutomatedAtAll.feature b/test-harness/MsTest/NotAutomatedAtAll.feature deleted file mode 100644 index 3bbfcb669..000000000 --- a/test-harness/MsTest/NotAutomatedAtAll.feature +++ /dev/null @@ -1,19 +0,0 @@ -Feature: Not Automated At All - -Background: - Given unimplemented step - -Scenario: Not automated scenario 1 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 2 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 3 - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/MsTest/NotAutomatedAtAll.feature.cs b/test-harness/MsTest/NotAutomatedAtAll.feature.cs deleted file mode 100644 index 1822045fa..000000000 --- a/test-harness/MsTest/NotAutomatedAtAll.feature.cs +++ /dev/null @@ -1,141 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class NotAutomatedAtAllFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "NotAutomatedAtAll.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Not Automated At All", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Not Automated At All"))) - { - Pickles.TestHarness.MsTest.NotAutomatedAtAllFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 3 -#line 4 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Not automated scenario 1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Not Automated At All")] - public virtual void NotAutomatedScenario1() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 1", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 7 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 8 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 9 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Not automated scenario 2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Not Automated At All")] - public virtual void NotAutomatedScenario2() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 2", ((string[])(null))); -#line 11 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 12 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 13 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 14 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Not automated scenario 3")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Not Automated At All")] - public virtual void NotAutomatedScenario3() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 3", ((string[])(null))); -#line 16 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 17 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 18 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/OrdinaryUnitTest.cs b/test-harness/MsTest/OrdinaryUnitTest.cs deleted file mode 100644 index 21af4d8b1..000000000 --- a/test-harness/MsTest/OrdinaryUnitTest.cs +++ /dev/null @@ -1,20 +0,0 @@ -using Microsoft.VisualStudio.TestTools.UnitTesting; - -namespace Pickles.TestHarness.MsTest -{ - /// - /// The ordinary unit test. - /// - [TestClass] - public class OrdinaryUnitTest - { - /// - /// The test method that tests something related to Addition feature. - /// - [TestMethod] - [TestProperty("FeatureTitle", "Addition")] - public void TestMethod() - { - } - } -} diff --git a/test-harness/MsTest/Properties/AssemblyInfo.cs b/test-harness/MsTest/Properties/AssemblyInfo.cs deleted file mode 100644 index d800f8ed2..000000000 --- a/test-harness/MsTest/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,36 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("MsTest")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("")] -[assembly: AssemblyProduct("MsTest")] -[assembly: AssemblyCopyright("Copyright © 2013")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM components. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("e72eb554-9284-4846-ad46-49bc14fc43ce")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Build and Revision Numbers -// by using the '*' as shown below: -// [assembly: AssemblyVersion("1.0.*")] -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/test-harness/MsTest/ScenarioOutlines.feature b/test-harness/MsTest/ScenarioOutlines.feature deleted file mode 100644 index 83b9ba106..000000000 --- a/test-harness/MsTest/ScenarioOutlines.feature +++ /dev/null @@ -1,142 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - -Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - And I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - -Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - -Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - -Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - -Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | \ No newline at end of file diff --git a/test-harness/MsTest/ScenarioOutlines.feature.cs b/test-harness/MsTest/ScenarioOutlines.feature.cs deleted file mode 100644 index 7d25ba657..000000000 --- a/test-harness/MsTest/ScenarioOutlines.feature.cs +++ /dev/null @@ -1,609 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class ScenarioOutlinesFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenarioOutlines.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenario Outlines", "Here we demonstrate how we deal with scenario outlines", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Scenario Outlines"))) - { - Pickles.TestHarness.MsTest.ScenarioOutlinesFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where all scenarios pass", exampleTags); -#line 4 -this.ScenarioSetup(scenarioInfo); -#line 8 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where all scenarios pass")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_1")] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass_Pass_1() - { - this.ThisIsAScenarioOutlineWhereAllScenariosPass("pass_1", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where all scenarios pass")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_2")] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass_Pass_2() - { - this.ThisIsAScenarioOutlineWhereAllScenariosPass("pass_2", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where all scenarios pass")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_3")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_3")] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass_Pass_3() - { - this.ThisIsAScenarioOutlineWhereAllScenariosPass("pass_3", ((string[])(null))); - } - - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario is inconclusive", exampleTags); -#line 17 -this.ScenarioSetup(scenarioInfo); -#line 21 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where one scenario is inconclusive")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_1")] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive_Pass_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive("pass_1", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where one scenario is inconclusive")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_2")] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive_Pass_2() - { - this.ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive("pass_2", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where one scenario is inconclusive")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "inconclusive_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "inconclusive_1")] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive_Inconclusive_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive("inconclusive_1", ((string[])(null))); - } - - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario fails", exampleTags); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 34 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where one scenario fails")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_1")] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails_Pass_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioFails("pass_1", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where one scenario fails")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_2")] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails_Pass_2() - { - this.ThisIsAScenarioOutlineWhereOneScenarioFails("pass_2", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline where one scenario fails")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "fail_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail_1")] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails_Fail_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioFails("fail_1", ((string[])(null))); - } - - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections_(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("And we can go totally bonkers with multiple example sections.", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 45 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_1")] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet0_Pass_1() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("pass_1", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_2")] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet0_Pass_2() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("pass_2", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "inconclusive_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "inconclusive_1")] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet1_Inconclusive_1() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("inconclusive_1", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "inconclusive_2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "inconclusive_2")] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet1_Inconclusive_2() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("inconclusive_2", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "fail_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail_1")] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet2_Fail_1() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("fail_1", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "fail_2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail_2")] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet2_Fail_2() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("fail_2", ((string[])(null))); - } - - public virtual void DealCorrectlyWithBackslashesInTheExamples(string filePath, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with backslashes in the examples", exampleTags); -#line 62 -this.ScenarioSetup(scenarioInfo); -#line 64 - testRunner.When(string.Format("I have backslashes in the value, for example a \'{0}\'", filePath), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal correctly with backslashes in the examples")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "c:\\Temp\\")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:file path", "c:\\Temp\\")] - public virtual void DealCorrectlyWithBackslashesInTheExamples_CTemp() - { - this.DealCorrectlyWithBackslashesInTheExamples("c:\\Temp\\", ((string[])(null))); - } - - public virtual void DealCorrectlyWithParenthesisInTheExamples(string overlyDescriptiveField, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with parenthesis in the examples", exampleTags); -#line 71 -this.ScenarioSetup(scenarioInfo); -#line 73 - testRunner.When(string.Format("I have parenthesis in the value, for example an \'{0}\'", overlyDescriptiveField), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal correctly with parenthesis in the examples")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "This is a description (and more)")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:overly descriptive field", "This is a description (and more)")] - public virtual void DealCorrectlyWithParenthesisInTheExamples_ThisIsADescriptionAndMore() - { - this.DealCorrectlyWithParenthesisInTheExamples("This is a description (and more)", ((string[])(null))); - } - - public virtual void DealCorrectlyWithOverlongExampleValues(string value1, string value2, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with overlong example values", exampleTags); -#line 79 -this.ScenarioSetup(scenarioInfo); -#line 81 - testRunner.When(string.Format("I have a field with value \'{0}\'", value1), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 82 - testRunner.And(string.Format("I have a field with value \'{0}\'", value2), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 83 - testRunner.Then("the scenario will \'pass_1\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal correctly with overlong example values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Please enter a valid two letter country code (e.g. DE)!")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:value1", "Please enter a valid two letter country code (e.g. DE)!")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:value2", "This is just a very very very veery long error message!")] - public virtual void DealCorrectlyWithOverlongExampleValues_PleaseEnterAValidTwoLetterCountryCodeE_G_DE() - { - this.DealCorrectlyWithOverlongExampleValues("Please enter a valid two letter country code (e.g. DE)!", "This is just a very very very veery long error message!", ((string[])(null))); - } - - public virtual void DealWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with duplicate values", exampleTags); -#line 89 -this.ScenarioSetup(scenarioInfo); -#line 90 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 0")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithDuplicateValues_Variant0() - { - this.DealWithDuplicateValues("pass", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithDuplicateValues_Variant1() - { - this.DealWithDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "inconclusive")] - public virtual void DealWithDuplicateValues_Variant2() - { - this.DealWithDuplicateValues("inconclusive", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 3")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithDuplicateValues_Variant3() - { - this.DealWithDuplicateValues("pass", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 4")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithDuplicateValues_Variant4() - { - this.DealWithDuplicateValues("fail", ((string[])(null))); - } - - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple example sections with duplicate values", exampleTags); -#line 100 -this.ScenarioSetup(scenarioInfo); -#line 101 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 0")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet0_Variant0() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet0_Variant1() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet0_Variant2() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 0")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant0() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "inconclusive")] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant1() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("inconclusive", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant2() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 3")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant3() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections without duplicate values", exampleTags); -#line 116 -this.ScenarioSetup(scenarioInfo); -#line 117 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections without duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "First set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues_FirstSet_Pass() - { - this.DealWithMultipleNamedExampleSectionsWithoutDuplicateValues("pass", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections without duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "First set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "fail")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues_FirstSet_Fail() - { - this.DealWithMultipleNamedExampleSectionsWithoutDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections without duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "Second set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "inconclusive")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "inconclusive")] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues_SecondSet_Inconclusive() - { - this.DealWithMultipleNamedExampleSectionsWithoutDuplicateValues("inconclusive", ((string[])(null))); - } - - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections with duplicate values", exampleTags); -#line 128 -this.ScenarioSetup(scenarioInfo); -#line 129 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "First set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 0")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_FirstSet_Variant0() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "First set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_FirstSet_Variant1() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "First set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_FirstSet_Variant2() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "Second set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 0")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant0() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "Second set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "inconclusive")] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant1() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("inconclusive", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "Second set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "fail")] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant2() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenario Outlines")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("ExampleSetName", "Second set")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 3")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass")] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant3() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/ScenariosWithSpecialCharacters.feature b/test-harness/MsTest/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index c4bbe7971..000000000 --- a/test-harness/MsTest/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,53 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'PASS' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This is a scenario outline with ampersand & - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step diff --git a/test-harness/MsTest/ScenariosWithSpecialCharacters.feature.cs b/test-harness/MsTest/ScenariosWithSpecialCharacters.feature.cs deleted file mode 100644 index 827ea7047..000000000 --- a/test-harness/MsTest/ScenariosWithSpecialCharacters.feature.cs +++ /dev/null @@ -1,289 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.MsTest -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestClassAttribute()] - public partial class ScenariosWithSpecialCharactersFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenariosWithSpecialCharacters.feature" -#line hidden - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassInitializeAttribute()] - public static void FeatureSetup(Microsoft.VisualStudio.TestTools.UnitTesting.TestContext testContext) - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenarios With Special Characters", "Here we demonstrate usage of special characters in scenario names", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.ClassCleanupAttribute()] - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestInitializeAttribute()] - public virtual void TestInitialize() - { - if (((TechTalk.SpecFlow.FeatureContext.Current != null) - && (TechTalk.SpecFlow.FeatureContext.Current.FeatureInfo.Title != "Scenarios With Special Characters"))) - { - Pickles.TestHarness.MsTest.ScenariosWithSpecialCharactersFeature.FeatureSetup(null); - } - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestCleanupAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - public virtual void ThisIsAScenarioWithParenthesesHyphenAndComma10_2030_40() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)", ((string[])(null))); -#line 7 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 8 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 9 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 10 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 11 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_1")] - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40_Pass_1() - { - this.ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40("pass_1", ((string[])(null))); - } - - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters(string regex, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This scenario contains examples with Regex-special characters", exampleTags); -#line 21 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 22 - testRunner.When(string.Format("I have special characters for regexes in the value, for example a \'{0}\'", regex), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 23 - testRunner.Then("the scenario will \'PASS\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 0")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:regex", "**")] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant0() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("**", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:regex", "++")] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant1() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("++", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 2")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:regex", ".*")] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant2() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters(".*", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 3")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:regex", "[]")] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant3() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("[]", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 4")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:regex", "{}")] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant4() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("{}", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 5")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:regex", "()")] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant5() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("()", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "Variant 6")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:regex", "^.*(?BAR)\\s[^0-9]{3,4}A+$")] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant6() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("^.*(?BAR)\\s[^0-9]{3,4}A+$", ((string[])(null))); - } - - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with german umlauts äöüß ÄÖÜ", exampleTags); -#line 35 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 36 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline with german umlauts äöüß ÄÖÜ")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_1")] - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU_Pass_1() - { - this.ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU("pass_1", ((string[])(null))); - } - - public virtual void ThisIsAScenarioOutlineWithAmpersand(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with ampersand &", exampleTags); -#line 42 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 43 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario outline with ampersand &")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("VariantName", "pass_1")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("Parameter:result", "pass_1")] - public virtual void ThisIsAScenarioOutlineWithAmpersand_Pass_1() - { - this.ThisIsAScenarioOutlineWithAmpersand("pass_1", ((string[])(null))); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario with danish characters æøå ÆØÅ")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - public virtual void ThisIsAScenarioWithDanishCharactersAEoaAEOA() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with danish characters æøå ÆØÅ", ((string[])(null))); -#line 49 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 50 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Microsoft.VisualStudio.TestTools.UnitTesting.TestMethodAttribute()] - [Microsoft.VisualStudio.TestTools.UnitTesting.DescriptionAttribute("This is a scenario with spanish characters ñáéíóú")] - [Microsoft.VisualStudio.TestTools.UnitTesting.TestPropertyAttribute("FeatureTitle", "Scenarios With Special Characters")] - public virtual void ThisIsAScenarioWithSpanishCharactersNaeiou() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with spanish characters ñáéíóú", ((string[])(null))); -#line 52 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 53 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/MsTest/packages.config b/test-harness/MsTest/packages.config deleted file mode 100644 index c6658054d..000000000 --- a/test-harness/MsTest/packages.config +++ /dev/null @@ -1,4 +0,0 @@ - - - - \ No newline at end of file diff --git a/test-harness/SpecRun/Addition.feature b/test-harness/SpecRun/Addition.feature deleted file mode 100644 index 238e261e9..000000000 --- a/test-harness/SpecRun/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/SpecRun/Addition.feature.cs b/test-harness/SpecRun/Addition.feature.cs deleted file mode 100644 index 7b3669e78..000000000 --- a/test-harness/SpecRun/Addition.feature.cs +++ /dev/null @@ -1,208 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18052 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Addition", Description="In order to avoid silly mistakes\r\nAs a math idiot\r\nI want to be told the sum of t" + - "wo numbers")] - public partial class AdditionFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Addition.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Addition", "In order to avoid silly mistakes\r\nAs a math idiot\r\nI want to be told the sum of t" + - "wo numbers", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 6 -#line 7 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - string[] @__tags = new string[] { - "tag2"}; - if ((exampleTags != null)) - { - @__tags = System.Linq.Enumerable.ToArray(System.Linq.Enumerable.Concat(@__tags, exampleTags)); - } - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", @__tags); -#line 10 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 11 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 12 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 13 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 14 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 15 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Adding several numbers, 60", new string[] { - "tag2"})] - public virtual void AddingSeveralNumbers_60() - { - this.AddingSeveralNumbers("60", "70", "130", "260", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Adding several numbers, 40", new string[] { - "tag2"})] - public virtual void AddingSeveralNumbers_40() - { - this.AddingSeveralNumbers("40", "50", "90", "180", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Add two numbers", new string[] { - "tag1"})] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", new string[] { - "tag1"}); -#line 23 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 24 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 25 - testRunner.And("I have entered 2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 26 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 27 - testRunner.Then("the result should be 3 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Fail to add two numbers", new string[] { - "tag1"})] - public virtual void FailToAddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Fail to add two numbers", new string[] { - "tag1"}); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 31 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 32 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 33 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 34 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Ignored adding two numbers")] - [TechTalk.SpecRun.IgnoreAttribute()] - public virtual void IgnoredAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Ignored adding two numbers", new string[] { - "ignore"}); -#line 37 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 38 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 39 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 40 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 41 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Not automated adding two numbers")] - public virtual void NotAutomatedAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated adding two numbers", ((string[])(null))); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 44 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 45 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 46 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/App.config b/test-harness/SpecRun/App.config deleted file mode 100644 index 81f33d36a..000000000 --- a/test-harness/SpecRun/App.config +++ /dev/null @@ -1,24 +0,0 @@ - - - -
          - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/SpecRun/CustomReportTemplate.cshtml b/test-harness/SpecRun/CustomReportTemplate.cshtml deleted file mode 100644 index 69ae56f5a..000000000 --- a/test-harness/SpecRun/CustomReportTemplate.cshtml +++ /dev/null @@ -1,49 +0,0 @@ - -@using System.Linq -@using System.Globalization -@using TechTalk.SpecRun.Framework -@using TechTalk.SpecRun.Framework.Results -@using TechTalk.SpecRun.Framework.TestSuiteStructure - -@helper GetResultForPickles(TestNode testNode) -{ - var summary = GetSummary(testNode); - - if (summary.Succeeded > 0) - {Passed} - else if (summary.TotalFailure > 0) - {Failed} - else if (summary.Ignored > 0) - {Ignored} - else if (summary.Pending > 0) - {Pending} - else - {Inconclusive} -} - - - - - - - - - \ No newline at end of file diff --git a/test-harness/SpecRun/Default.srprofile b/test-harness/SpecRun/Default.srprofile deleted file mode 100644 index 463a1f910..000000000 --- a/test-harness/SpecRun/Default.srprofile +++ /dev/null @@ -1,29 +0,0 @@ - - - - - - - SpecRun.dll - - - - - - - - diff --git a/test-harness/SpecRun/FailingBackground.feature b/test-harness/SpecRun/FailingBackground.feature deleted file mode 100644 index 83a70483a..000000000 --- a/test-harness/SpecRun/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/SpecRun/FailingBackground.feature.cs b/test-harness/SpecRun/FailingBackground.feature.cs deleted file mode 100644 index dacc7da88..000000000 --- a/test-harness/SpecRun/FailingBackground.feature.cs +++ /dev/null @@ -1,136 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Failing Background", Description="This feature has a failing background.", SourceFile="FailingBackground.feature", SourceLine=0)] - public partial class FailingBackgroundFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "FailingBackground.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing Background", "This feature has a failing background.", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the background step fails", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 6 - testRunner.And("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line hidden - } - - [TechTalk.SpecRun.ScenarioAttribute("Add two numbers", SourceLine=7)] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", ((string[])(null))); -#line 8 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 9 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 10 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 11 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 12 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 16 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 17 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 18 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Adding several numbers, 60", SourceLine=22)] - public virtual void AddingSeveralNumbers_60() - { - this.AddingSeveralNumbers("60", "70", "130", "260", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Adding several numbers, 40", SourceLine=23)] - public virtual void AddingSeveralNumbers_40() - { - this.AddingSeveralNumbers("40", "50", "90", "180", ((string[])(null))); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/Minimal Features/Failing.feature b/test-harness/SpecRun/Minimal Features/Failing.feature deleted file mode 100644 index d7c5b7f53..000000000 --- a/test-harness/SpecRun/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step \ No newline at end of file diff --git a/test-harness/SpecRun/Minimal Features/Failing.feature.cs b/test-harness/SpecRun/Minimal Features/Failing.feature.cs deleted file mode 100644 index 917b07d45..000000000 --- a/test-harness/SpecRun/Minimal Features/Failing.feature.cs +++ /dev/null @@ -1,109 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18052 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Failing")] - public partial class FailingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Failing.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Failing Feature Passing Scenario")] - public virtual void FailingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Failing Feature Inconclusive Scenario")] - public virtual void FailingFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Failing Feature Failing Scenario")] - public virtual void FailingFeatureFailingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Failing Scenario", ((string[])(null))); -#line 9 -this.ScenarioSetup(scenarioInfo); -#line 10 - testRunner.Then("failing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/Minimal Features/Inconclusive.feature b/test-harness/SpecRun/Minimal Features/Inconclusive.feature deleted file mode 100644 index 7ce63f2d5..000000000 --- a/test-harness/SpecRun/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step \ No newline at end of file diff --git a/test-harness/SpecRun/Minimal Features/Inconclusive.feature.cs b/test-harness/SpecRun/Minimal Features/Inconclusive.feature.cs deleted file mode 100644 index 17b47e12e..000000000 --- a/test-harness/SpecRun/Minimal Features/Inconclusive.feature.cs +++ /dev/null @@ -1,97 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18052 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Inconclusive")] - public partial class InconclusiveFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Inconclusive.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Inconclusive", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Inconclusive Feature Passing Scenario")] - public virtual void InconclusiveFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Inconclusive Feature Inconclusive Scenario")] - public virtual void InconclusiveFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/Minimal Features/Passing.feature b/test-harness/SpecRun/Minimal Features/Passing.feature deleted file mode 100644 index 14bf35e22..000000000 --- a/test-harness/SpecRun/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/SpecRun/Minimal Features/Passing.feature.cs b/test-harness/SpecRun/Minimal Features/Passing.feature.cs deleted file mode 100644 index 1526b08ba..000000000 --- a/test-harness/SpecRun/Minimal Features/Passing.feature.cs +++ /dev/null @@ -1,85 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18052 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Passing")] - public partial class PassingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Passing.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Passing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Passing Feature Passing Scenario")] - public virtual void PassingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Passing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/NotAutomatedAtAll.feature b/test-harness/SpecRun/NotAutomatedAtAll.feature deleted file mode 100644 index 3bbfcb669..000000000 --- a/test-harness/SpecRun/NotAutomatedAtAll.feature +++ /dev/null @@ -1,19 +0,0 @@ -Feature: Not Automated At All - -Background: - Given unimplemented step - -Scenario: Not automated scenario 1 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 2 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 3 - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/SpecRun/NotAutomatedAtAll.feature.cs b/test-harness/SpecRun/NotAutomatedAtAll.feature.cs deleted file mode 100644 index 623e4f0e5..000000000 --- a/test-harness/SpecRun/NotAutomatedAtAll.feature.cs +++ /dev/null @@ -1,135 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18052 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Not Automated At All")] - public partial class NotAutomatedAtAllFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "NotAutomatedAtAll.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Not Automated At All", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 3 -#line 4 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [TechTalk.SpecRun.ScenarioAttribute("Not automated scenario 1")] - public virtual void NotAutomatedScenario1() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 1", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 7 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 8 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 9 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Not automated scenario 2")] - public virtual void NotAutomatedScenario2() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 2", ((string[])(null))); -#line 11 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 12 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 13 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 14 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Not automated scenario 3")] - public virtual void NotAutomatedScenario3() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 3", ((string[])(null))); -#line 16 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 17 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 18 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/Properties/AssemblyInfo.cs b/test-harness/SpecRun/Properties/AssemblyInfo.cs deleted file mode 100644 index b64ebba26..000000000 --- a/test-harness/SpecRun/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,36 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("SpecRun")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("AIM Software")] -[assembly: AssemblyProduct("SpecRun")] -[assembly: AssemblyCopyright("Copyright © AIM Software 2013")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM components. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("ca37f04b-0bfb-452b-aba0-8b183088ac45")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Build and Revision Numbers -// by using the '*' as shown below: -// [assembly: AssemblyVersion("1.0.*")] -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/test-harness/SpecRun/ScenarioOutlines.feature b/test-harness/SpecRun/ScenarioOutlines.feature deleted file mode 100644 index 67d3c9e8c..000000000 --- a/test-harness/SpecRun/ScenarioOutlines.feature +++ /dev/null @@ -1,142 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - - Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - -Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - -Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - -Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - -Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | \ No newline at end of file diff --git a/test-harness/SpecRun/ScenarioOutlines.feature.cs b/test-harness/SpecRun/ScenarioOutlines.feature.cs deleted file mode 100644 index 6dc82d378..000000000 --- a/test-harness/SpecRun/ScenarioOutlines.feature.cs +++ /dev/null @@ -1,454 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Scenario Outlines", Description="Here we demonstrate how we deal with scenario outlines", SourceFile="ScenarioOutlines.feature", SourceLine=0)] - public partial class ScenarioOutlinesFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenarioOutlines.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenario Outlines", "Here we demonstrate how we deal with scenario outlines", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where all scenarios pass", exampleTags); -#line 4 -this.ScenarioSetup(scenarioInfo); -#line 8 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where all scenarios pass, pass_1", Description="\r\nThis means the entire scenario outline passes.", SourceLine=11)] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass_Pass_1() - { - this.ThisIsAScenarioOutlineWhereAllScenariosPass("pass_1", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where all scenarios pass, pass_2", Description="\r\nThis means the entire scenario outline passes.", SourceLine=12)] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass_Pass_2() - { - this.ThisIsAScenarioOutlineWhereAllScenariosPass("pass_2", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where all scenarios pass, pass_3", Description="\r\nThis means the entire scenario outline passes.", SourceLine=13)] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass_Pass_3() - { - this.ThisIsAScenarioOutlineWhereAllScenariosPass("pass_3", ((string[])(null))); - } - - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario is inconclusive", exampleTags); -#line 17 -this.ScenarioSetup(scenarioInfo); -#line 21 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where one scenario is inconclusive, pass_1", Description="\r\nThis means the entire scenario outline is inconclusive.", SourceLine=24)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive_Pass_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive("pass_1", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where one scenario is inconclusive, pass_2", Description="\r\nThis means the entire scenario outline is inconclusive.", SourceLine=25)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive_Pass_2() - { - this.ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive("pass_2", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where one scenario is inconclusive, inconclusive_1", Description="\r\nThis means the entire scenario outline is inconclusive.", SourceLine=26)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive_Inconclusive_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive("inconclusive_1", ((string[])(null))); - } - - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario fails", exampleTags); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 34 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where one scenario fails, pass_1", Description="\r\nThis means the entire scenario outline fails.", SourceLine=37)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails_Pass_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioFails("pass_1", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where one scenario fails, pass_2", Description="\r\nThis means the entire scenario outline fails.", SourceLine=38)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails_Pass_2() - { - this.ThisIsAScenarioOutlineWhereOneScenarioFails("pass_2", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline where one scenario fails, fail_1", Description="\r\nThis means the entire scenario outline fails.", SourceLine=39)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails_Fail_1() - { - this.ThisIsAScenarioOutlineWhereOneScenarioFails("fail_1", ((string[])(null))); - } - - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections_(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("And we can go totally bonkers with multiple example sections.", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 45 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("And we can go totally bonkers with multiple example sections., Examples 1, pass_1" + - "", SourceLine=48)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet0_Pass_1() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("pass_1", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("And we can go totally bonkers with multiple example sections., Examples 1, pass_2" + - "", SourceLine=49)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet0_Pass_2() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("pass_2", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("And we can go totally bonkers with multiple example sections., Examples 2, inconc" + - "lusive_1", SourceLine=53)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet1_Inconclusive_1() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("inconclusive_1", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("And we can go totally bonkers with multiple example sections., Examples 2, inconc" + - "lusive_2", SourceLine=54)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet1_Inconclusive_2() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("inconclusive_2", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("And we can go totally bonkers with multiple example sections., Examples 3, fail_1" + - "", SourceLine=58)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet2_Fail_1() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("fail_1", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("And we can go totally bonkers with multiple example sections., Examples 3, fail_2" + - "", SourceLine=59)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections__ExampleSet2_Fail_2() - { - this.AndWeCanGoTotallyBonkersWithMultipleExampleSections_("fail_2", ((string[])(null))); - } - - public virtual void DealCorrectlyWithBackslashesInTheExamples(string filePath, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with backslashes in the examples", exampleTags); -#line 63 -this.ScenarioSetup(scenarioInfo); -#line 65 - testRunner.When(string.Format("I have backslashes in the value, for example a \'{0}\'", filePath), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal correctly with backslashes in the examples, c:\\Temp\\", SourceLine=68)] - public virtual void DealCorrectlyWithBackslashesInTheExamples_CTemp() - { - this.DealCorrectlyWithBackslashesInTheExamples("c:\\Temp\\", ((string[])(null))); - } - - public virtual void DealCorrectlyWithParenthesisInTheExamples(string overlyDescriptiveField, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with parenthesis in the examples", exampleTags); -#line 72 -this.ScenarioSetup(scenarioInfo); -#line 74 - testRunner.When(string.Format("I have parenthesis in the value, for example an \'{0}\'", overlyDescriptiveField), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal correctly with parenthesis in the examples, This is a description (and more)" + - "", SourceLine=77)] - public virtual void DealCorrectlyWithParenthesisInTheExamples_ThisIsADescriptionAndMore() - { - this.DealCorrectlyWithParenthesisInTheExamples("This is a description (and more)", ((string[])(null))); - } - - public virtual void DealCorrectlyWithOverlongExampleValues(string value1, string value2, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with overlong example values", exampleTags); -#line 80 - this.ScenarioSetup(scenarioInfo); -#line 82 - testRunner.When("I have a field with value \'\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 83 - testRunner.Then("the scenario will \'pass_1\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal correctly with overlong example values, Please enter a valid two letter coun" + - "try code (e.g. DE)!", SourceLine=86)] - public virtual void DealCorrectlyWithOverlongExampleValues_PleaseEnterAValidTwoLetterCountryCodeE_G_DE() - { - this.DealCorrectlyWithOverlongExampleValues("Please enter a valid two letter country code (e.g. DE)!", "This is just a very very very veery long error message!", ((string[])(null))); - } - - public virtual void DealWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with duplicate values", exampleTags); -#line 89 -this.ScenarioSetup(scenarioInfo); -#line 90 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with duplicate values, Variant 0", SourceLine=93)] - public virtual void DealWithDuplicateValues_Variant0() - { - this.DealWithDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with duplicate values, Variant 1", SourceLine=94)] - public virtual void DealWithDuplicateValues_Variant1() - { - this.DealWithDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with duplicate values, Variant 2", SourceLine=95)] - public virtual void DealWithDuplicateValues_Variant2() - { - this.DealWithDuplicateValues("inconclusive", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with duplicate values, Variant 3", SourceLine=96)] - public virtual void DealWithDuplicateValues_Variant3() - { - this.DealWithDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with duplicate values, Variant 4", SourceLine=97)] - public virtual void DealWithDuplicateValues_Variant4() - { - this.DealWithDuplicateValues("fail", ((string[])(null))); - } - - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple example sections with duplicate values", exampleTags); -#line 100 -this.ScenarioSetup(scenarioInfo); -#line 101 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple example sections with duplicate values, Examples 1, Variant 0", SourceLine=104)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet0_Variant0() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple example sections with duplicate values, Examples 1, Variant 1", SourceLine=105)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet0_Variant1() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple example sections with duplicate values, Examples 1, Variant 2", SourceLine=106)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet0_Variant2() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple example sections with duplicate values, Examples 2, Variant 0", SourceLine=110)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant0() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple example sections with duplicate values, Examples 2, Variant 1", SourceLine=111)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant1() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("inconclusive", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple example sections with duplicate values, Examples 2, Variant 2", SourceLine=112)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant2() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple example sections with duplicate values, Examples 2, Variant 3", SourceLine=113)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues_ExampleSet1_Variant3() - { - this.DealWithMultipleExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections without duplicate values", exampleTags); -#line 116 -this.ScenarioSetup(scenarioInfo); -#line 117 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections without duplicate values, First set, pa" + - "ss", SourceLine=120)] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues_FirstSet_Pass() - { - this.DealWithMultipleNamedExampleSectionsWithoutDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections without duplicate values, First set, fa" + - "il", SourceLine=121)] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues_FirstSet_Fail() - { - this.DealWithMultipleNamedExampleSectionsWithoutDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections without duplicate values, Second set, i" + - "nconclusive", SourceLine=125)] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues_SecondSet_Inconclusive() - { - this.DealWithMultipleNamedExampleSectionsWithoutDuplicateValues("inconclusive", ((string[])(null))); - } - - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections with duplicate values", exampleTags); -#line 128 -this.ScenarioSetup(scenarioInfo); -#line 129 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections with duplicate values, First set, Varia" + - "nt 0", SourceLine=132)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_FirstSet_Variant0() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections with duplicate values, First set, Varia" + - "nt 1", SourceLine=133)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_FirstSet_Variant1() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections with duplicate values, First set, Varia" + - "nt 2", SourceLine=134)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_FirstSet_Variant2() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections with duplicate values, Second set, Vari" + - "ant 0", SourceLine=138)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant0() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections with duplicate values, Second set, Vari" + - "ant 1", SourceLine=139)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant1() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("inconclusive", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections with duplicate values, Second set, Vari" + - "ant 2", SourceLine=140)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant2() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("fail", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("Deal with multiple named example sections with duplicate values, Second set, Vari" + - "ant 3", SourceLine=141)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues_SecondSet_Variant3() - { - this.DealWithMultipleNamedExampleSectionsWithDuplicateValues("pass", ((string[])(null))); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/ScenariosWithSpecialCharacters.feature b/test-harness/SpecRun/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index e8a7ff0dc..000000000 --- a/test-harness/SpecRun/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,54 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'PASS' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -#Excluding this test, because & is not properly encoded in the result so that xml-parsing fails -#Scenario Outline: This is a scenario outline with ampersand & -# Then the scenario will '' -# -# Examples: -# | result | -# | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step \ No newline at end of file diff --git a/test-harness/SpecRun/ScenariosWithSpecialCharacters.feature.cs b/test-harness/SpecRun/ScenariosWithSpecialCharacters.feature.cs deleted file mode 100644 index 2310ef47d..000000000 --- a/test-harness/SpecRun/ScenariosWithSpecialCharacters.feature.cs +++ /dev/null @@ -1,225 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace SpecRun -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [TechTalk.SpecRun.FeatureAttribute("Scenarios With Special Characters", Description="Here we demonstrate usage of special characters in scenario names", SourceFile="ScenariosWithSpecialCharacters.feature", SourceLine=0)] - public partial class ScenariosWithSpecialCharactersFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenariosWithSpecialCharacters.feature" -#line hidden - - [TechTalk.SpecRun.FeatureInitialize()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenarios With Special Characters", "Here we demonstrate usage of special characters in scenario names", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [TechTalk.SpecRun.FeatureCleanup()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - [TechTalk.SpecRun.ScenarioCleanup()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)", SourceLine=6)] - public virtual void ThisIsAScenarioWithParenthesesHyphenAndComma10_2030_40() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)", ((string[])(null))); -#line 7 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 8 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 9 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 10 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 11 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40), pas" + - "s_1", SourceLine=18)] - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40_Pass_1() - { - this.ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40("pass_1", ((string[])(null))); - } - - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters(string regex, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This scenario contains examples with Regex-special characters", exampleTags); -#line 21 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 22 - testRunner.When(string.Format("I have special characters for regexes in the value, for example a \'{0}\'", regex), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 23 - testRunner.Then("the scenario will \'PASS\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("This scenario contains examples with Regex-special characters, Variant 0", SourceLine=26)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant0() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("**", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This scenario contains examples with Regex-special characters, Variant 1", SourceLine=27)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant1() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("++", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This scenario contains examples with Regex-special characters, Variant 2", SourceLine=28)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant2() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters(".*", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This scenario contains examples with Regex-special characters, Variant 3", SourceLine=29)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant3() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("[]", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This scenario contains examples with Regex-special characters, Variant 4", SourceLine=30)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant4() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("{}", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This scenario contains examples with Regex-special characters, Variant 5", SourceLine=31)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant5() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("()", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This scenario contains examples with Regex-special characters, Variant 6", SourceLine=32)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters_Variant6() - { - this.ThisScenarioContainsExamplesWithRegex_SpecialCharacters("^.*(?BAR)\\s[^0-9]{3,4}A+$", ((string[])(null))); - } - - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with german umlauts äöüß ÄÖÜ", exampleTags); -#line 35 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 36 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario outline with german umlauts äöüß ÄÖÜ, pass_1", SourceLine=39)] - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU_Pass_1() - { - this.ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU("pass_1", ((string[])(null))); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario with danish characters æøå ÆØÅ", SourceLine=49)] - public virtual void ThisIsAScenarioWithDanishCharactersAEoaAEOA() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with danish characters æøå ÆØÅ", ((string[])(null))); -#line 50 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 51 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.ScenarioAttribute("This is a scenario with spanish characters ñáéíóú", SourceLine=52)] - public virtual void ThisIsAScenarioWithSpanishCharactersNaeiou() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with spanish characters ñáéíóú", ((string[])(null))); -#line 53 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 54 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [TechTalk.SpecRun.TestRunCleanup()] - public virtual void TestRunCleanup() - { -TechTalk.SpecFlow.TestRunnerManager.GetTestRunner().OnTestRunEnd(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/SpecRun/SpecRun.csproj b/test-harness/SpecRun/SpecRun.csproj deleted file mode 100644 index 35f76b21d..000000000 --- a/test-harness/SpecRun/SpecRun.csproj +++ /dev/null @@ -1,164 +0,0 @@ - - - - - Debug - AnyCPU - {15DD6AA3-525E-4F4A-BC68-07542ECC4159} - Library - Properties - SpecRun - SpecRun - v4.5 - 512 - - ..\ - true - - - true - full - false - bin\Debug\ - DEBUG;TRACE - prompt - 4 - false - - - pdbonly - true - bin\Release\ - TRACE - prompt - 4 - false - - - - False - ..\packages\SpecRun.SpecFlow.1.2.0\lib\net35\SpecRun.SpecFlowPlugin.dll - - - - - - - - - - ..\packages\SpecFlow.1.9.0\lib\net35\TechTalk.SpecFlow.dll - - - False - ..\packages\SpecRun.SpecFlow.1.2.0\lib\net35\TechTalk.SpecRun.dll - - - - - Addition.feature - True - True - - - FailingBackground.feature - True - True - - - Failing.feature - True - True - - - Inconclusive.feature - True - True - - - Passing.feature - True - True - - - NotAutomatedAtAll.feature - True - True - - - - ScenarioOutlines.feature - True - True - - - True - True - ScenariosWithSpecialCharacters.feature - - - - - SpecFlowSingleFileGenerator - Addition.feature.cs - - - - PreserveNewest - Designer - - - SpecFlowSingleFileGenerator - FailingBackground.feature.cs - - - SpecFlowSingleFileGenerator - Failing.feature.cs - - - SpecFlowSingleFileGenerator - Inconclusive.feature.cs - - - SpecFlowSingleFileGenerator - Passing.feature.cs - - - SpecFlowSingleFileGenerator - NotAutomatedAtAll.feature.cs - - - - PreserveNewest - - - - SpecFlowSingleFileGenerator - ScenarioOutlines.feature.cs - - - SpecFlowSingleFileGenerator - ScenariosWithSpecialCharacters.feature.cs - - - Designer - - - - - {073862de-d599-4941-9716-03206cf1cfa2} - AutomationLayer - - - - - - - - \ No newline at end of file diff --git a/test-harness/SpecRun/SpecRunTestProfile.xsd b/test-harness/SpecRun/SpecRunTestProfile.xsd deleted file mode 100644 index 8b4fdb2d4..000000000 --- a/test-harness/SpecRun/SpecRunTestProfile.xsd +++ /dev/null @@ -1,194 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/test-harness/SpecRun/packages.config b/test-harness/SpecRun/packages.config deleted file mode 100644 index 10cb35333..000000000 --- a/test-harness/SpecRun/packages.config +++ /dev/null @@ -1,6 +0,0 @@ - - - - - - \ No newline at end of file diff --git a/test-harness/SpecRun/runtests.cmd b/test-harness/SpecRun/runtests.cmd deleted file mode 100644 index 716cb0425..000000000 --- a/test-harness/SpecRun/runtests.cmd +++ /dev/null @@ -1,17 +0,0 @@ -@pushd %~dp0 - -%windir%\Microsoft.NET\Framework\v4.0.30319\MSBuild.exe "SpecRun.csproj" - -@if ERRORLEVEL 1 goto end - -@cd ..\packages\SpecRun.Runner.*\tools - -@set profile=%1 -@if "%profile%" == "" set profile=Default - -SpecRun.exe run %profile%.srprofile "/baseFolder:%~dp0\bin\Debug" /log:specrun.log %2 %3 %4 %5 - -:end - -@popd - diff --git a/test-harness/TestHarness.sln b/test-harness/TestHarness.sln deleted file mode 100644 index e99a84a17..000000000 --- a/test-harness/TestHarness.sln +++ /dev/null @@ -1,63 +0,0 @@ - -Microsoft Visual Studio Solution File, Format Version 12.00 -# Visual Studio 14 -VisualStudioVersion = 14.0.23107.0 -MinimumVisualStudioVersion = 10.0.40219.1 -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "MsTest", "MsTest\MsTest.csproj", "{0DBA6FCA-5D66-4187-932D-64B55D67E287}" -EndProject -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "nunit", "nunit\nunit.csproj", "{C13BF896-768D-47BC-86A0-99BC53CC54E6}" -EndProject -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "xunit", "xunit\xunit.csproj", "{F4AB7229-9022-4FFC-86EC-570ADF2A682C}" -EndProject -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "AutomationLayer", "AutomationLayer\AutomationLayer.csproj", "{073862DE-D599-4941-9716-03206CF1CFA2}" -EndProject -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "SpecRun", "SpecRun\SpecRun.csproj", "{15DD6AA3-525E-4F4A-BC68-07542ECC4159}" -EndProject -Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{5249183C-E96B-490B-A2C4-90D003A60CB3}" - ProjectSection(SolutionItems) = preProject - TestSettings.testsettings = TestSettings.testsettings - EndProjectSection -EndProject -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "nunit3", "nunit3\nunit3.csproj", "{C5E91AEE-8234-443A-A327-6A6581E49D4B}" -EndProject -Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "xunit2", "xunit2\xunit2.csproj", "{E5B28DB5-295E-4E33-A9E3-D84A49265BAF}" -EndProject -Global - GlobalSection(SolutionConfigurationPlatforms) = preSolution - Debug|Any CPU = Debug|Any CPU - Release|Any CPU = Release|Any CPU - EndGlobalSection - GlobalSection(ProjectConfigurationPlatforms) = postSolution - {0DBA6FCA-5D66-4187-932D-64B55D67E287}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {0DBA6FCA-5D66-4187-932D-64B55D67E287}.Debug|Any CPU.Build.0 = Debug|Any CPU - {0DBA6FCA-5D66-4187-932D-64B55D67E287}.Release|Any CPU.ActiveCfg = Release|Any CPU - {0DBA6FCA-5D66-4187-932D-64B55D67E287}.Release|Any CPU.Build.0 = Release|Any CPU - {C13BF896-768D-47BC-86A0-99BC53CC54E6}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {C13BF896-768D-47BC-86A0-99BC53CC54E6}.Debug|Any CPU.Build.0 = Debug|Any CPU - {C13BF896-768D-47BC-86A0-99BC53CC54E6}.Release|Any CPU.ActiveCfg = Release|Any CPU - {C13BF896-768D-47BC-86A0-99BC53CC54E6}.Release|Any CPU.Build.0 = Release|Any CPU - {F4AB7229-9022-4FFC-86EC-570ADF2A682C}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {F4AB7229-9022-4FFC-86EC-570ADF2A682C}.Debug|Any CPU.Build.0 = Debug|Any CPU - {F4AB7229-9022-4FFC-86EC-570ADF2A682C}.Release|Any CPU.ActiveCfg = Release|Any CPU - {F4AB7229-9022-4FFC-86EC-570ADF2A682C}.Release|Any CPU.Build.0 = Release|Any CPU - {073862DE-D599-4941-9716-03206CF1CFA2}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {073862DE-D599-4941-9716-03206CF1CFA2}.Debug|Any CPU.Build.0 = Debug|Any CPU - {073862DE-D599-4941-9716-03206CF1CFA2}.Release|Any CPU.ActiveCfg = Release|Any CPU - {073862DE-D599-4941-9716-03206CF1CFA2}.Release|Any CPU.Build.0 = Release|Any CPU - {15DD6AA3-525E-4F4A-BC68-07542ECC4159}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {15DD6AA3-525E-4F4A-BC68-07542ECC4159}.Debug|Any CPU.Build.0 = Debug|Any CPU - {15DD6AA3-525E-4F4A-BC68-07542ECC4159}.Release|Any CPU.ActiveCfg = Release|Any CPU - {15DD6AA3-525E-4F4A-BC68-07542ECC4159}.Release|Any CPU.Build.0 = Release|Any CPU - {C5E91AEE-8234-443A-A327-6A6581E49D4B}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {C5E91AEE-8234-443A-A327-6A6581E49D4B}.Debug|Any CPU.Build.0 = Debug|Any CPU - {C5E91AEE-8234-443A-A327-6A6581E49D4B}.Release|Any CPU.ActiveCfg = Release|Any CPU - {C5E91AEE-8234-443A-A327-6A6581E49D4B}.Release|Any CPU.Build.0 = Release|Any CPU - {E5B28DB5-295E-4E33-A9E3-D84A49265BAF}.Debug|Any CPU.ActiveCfg = Debug|Any CPU - {E5B28DB5-295E-4E33-A9E3-D84A49265BAF}.Debug|Any CPU.Build.0 = Debug|Any CPU - {E5B28DB5-295E-4E33-A9E3-D84A49265BAF}.Release|Any CPU.ActiveCfg = Release|Any CPU - {E5B28DB5-295E-4E33-A9E3-D84A49265BAF}.Release|Any CPU.Build.0 = Release|Any CPU - EndGlobalSection - GlobalSection(SolutionProperties) = preSolution - HideSolutionNode = FALSE - EndGlobalSection -EndGlobal diff --git a/test-harness/TestHarness.sln.GhostDoc.xml b/test-harness/TestHarness.sln.GhostDoc.xml deleted file mode 100644 index 79f5bebe1..000000000 --- a/test-harness/TestHarness.sln.GhostDoc.xml +++ /dev/null @@ -1,57 +0,0 @@ - - - *.min.js - jquery*.js - - - - - - - - - - - - .\Help - true - TestHarness - MemberName - - - - true - false - false - false - - - true - false - false - false - true - true - false - - - - - - true - true - true - - true - - - - - - - - - - - - diff --git a/test-harness/TestSettings.testsettings b/test-harness/TestSettings.testsettings deleted file mode 100644 index 1c25c1c1d..000000000 --- a/test-harness/TestSettings.testsettings +++ /dev/null @@ -1,9 +0,0 @@ - - - These are default test settings for a local test run. - - diff --git a/test-harness/nunit/Addition.feature b/test-harness/nunit/Addition.feature deleted file mode 100644 index 238e261e9..000000000 --- a/test-harness/nunit/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/nunit/Addition.feature.cs b/test-harness/nunit/Addition.feature.cs deleted file mode 100644 index c6f1ae68d..000000000 --- a/test-harness/nunit/Addition.feature.cs +++ /dev/null @@ -1,198 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Addition")] - public partial class AdditionFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Addition.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Addition", "In order to avoid silly mistakes\r\nAs a math idiot\r\nI want to be told the sum of t" + - "wo numbers", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 6 -#line 7 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Adding several numbers")] - [NUnit.Framework.CategoryAttribute("tag2")] - [NUnit.Framework.TestCaseAttribute("60", "70", "130", "260", null)] - [NUnit.Framework.TestCaseAttribute("40", "50", "90", "180", null)] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - string[] @__tags = new string[] { - "tag2"}; - if ((exampleTags != null)) - { - @__tags = System.Linq.Enumerable.ToArray(System.Linq.Enumerable.Concat(@__tags, exampleTags)); - } - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", @__tags); -#line 10 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 11 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 12 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 13 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 14 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 15 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Add two numbers")] - [NUnit.Framework.CategoryAttribute("tag1")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", new string[] { - "tag1"}); -#line 23 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 24 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 25 - testRunner.And("I have entered 2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 26 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 27 - testRunner.Then("the result should be 3 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Fail to add two numbers")] - [NUnit.Framework.CategoryAttribute("tag1")] - public virtual void FailToAddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Fail to add two numbers", new string[] { - "tag1"}); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 31 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 32 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 33 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 34 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Ignored adding two numbers")] - [NUnit.Framework.IgnoreAttribute()] - public virtual void IgnoredAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Ignored adding two numbers", new string[] { - "ignore"}); -#line 37 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 38 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 39 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 40 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 41 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Not automated adding two numbers")] - public virtual void NotAutomatedAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated adding two numbers", ((string[])(null))); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 44 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 45 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 46 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/App.config b/test-harness/nunit/App.config deleted file mode 100644 index b2982b130..000000000 --- a/test-harness/nunit/App.config +++ /dev/null @@ -1,13 +0,0 @@ - - - -
          - - - - - - - - - \ No newline at end of file diff --git a/test-harness/nunit/FailingBackground.feature b/test-harness/nunit/FailingBackground.feature deleted file mode 100644 index 83a70483a..000000000 --- a/test-harness/nunit/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/nunit/FailingBackground.feature.cs b/test-harness/nunit/FailingBackground.feature.cs deleted file mode 100644 index 22eccc05b..000000000 --- a/test-harness/nunit/FailingBackground.feature.cs +++ /dev/null @@ -1,125 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Background")] - public partial class FailingBackgroundFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "FailingBackground.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing Background", "This feature has a failing background.", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the background step fails", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 6 - testRunner.And("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line hidden - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Add two numbers")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", ((string[])(null))); -#line 8 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 9 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 10 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 11 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 12 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Adding several numbers")] - [NUnit.Framework.TestCaseAttribute("60", "70", "130", "260", null)] - [NUnit.Framework.TestCaseAttribute("40", "50", "90", "180", null)] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 16 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 17 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 18 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/Minimal Features/Failing.feature b/test-harness/nunit/Minimal Features/Failing.feature deleted file mode 100644 index d7c5b7f53..000000000 --- a/test-harness/nunit/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step \ No newline at end of file diff --git a/test-harness/nunit/Minimal Features/Failing.feature.cs b/test-harness/nunit/Minimal Features/Failing.feature.cs deleted file mode 100644 index f5c84a205..000000000 --- a/test-harness/nunit/Minimal Features/Failing.feature.cs +++ /dev/null @@ -1,108 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing")] - public partial class FailingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Failing.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Feature Passing Scenario")] - public virtual void FailingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Feature Inconclusive Scenario")] - public virtual void FailingFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Feature Failing Scenario")] - public virtual void FailingFeatureFailingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Failing Scenario", ((string[])(null))); -#line 9 -this.ScenarioSetup(scenarioInfo); -#line 10 - testRunner.Then("failing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/Minimal Features/Inconclusive.feature b/test-harness/nunit/Minimal Features/Inconclusive.feature deleted file mode 100644 index 40c27b402..000000000 --- a/test-harness/nunit/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step \ No newline at end of file diff --git a/test-harness/nunit/Minimal Features/Inconclusive.feature.cs b/test-harness/nunit/Minimal Features/Inconclusive.feature.cs deleted file mode 100644 index 3bb3d2418..000000000 --- a/test-harness/nunit/Minimal Features/Inconclusive.feature.cs +++ /dev/null @@ -1,95 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Inconclusive")] - public partial class InconclusiveFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Inconclusive.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Inconclusive", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Inconclusive Feature Passing Scenario")] - public virtual void InconclusiveFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Inconclusive Feature Inconclusive Scenario")] - public virtual void InconclusiveFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/Minimal Features/Passing.feature b/test-harness/nunit/Minimal Features/Passing.feature deleted file mode 100644 index 14bf35e22..000000000 --- a/test-harness/nunit/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/nunit/Minimal Features/Passing.feature.cs b/test-harness/nunit/Minimal Features/Passing.feature.cs deleted file mode 100644 index a7b9a62ca..000000000 --- a/test-harness/nunit/Minimal Features/Passing.feature.cs +++ /dev/null @@ -1,82 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Passing")] - public partial class PassingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Passing.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Passing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Passing Feature Passing Scenario")] - public virtual void PassingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Passing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/NotAutomatedAtAll.feature b/test-harness/nunit/NotAutomatedAtAll.feature deleted file mode 100644 index 3bbfcb669..000000000 --- a/test-harness/nunit/NotAutomatedAtAll.feature +++ /dev/null @@ -1,19 +0,0 @@ -Feature: Not Automated At All - -Background: - Given unimplemented step - -Scenario: Not automated scenario 1 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 2 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 3 - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/nunit/NotAutomatedAtAll.feature.cs b/test-harness/nunit/NotAutomatedAtAll.feature.cs deleted file mode 100644 index 79b27b127..000000000 --- a/test-harness/nunit/NotAutomatedAtAll.feature.cs +++ /dev/null @@ -1,134 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.18051 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Not Automated At All")] - public partial class NotAutomatedAtAllFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "NotAutomatedAtAll.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Not Automated At All", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 3 -#line 4 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Not automated scenario 1")] - public virtual void NotAutomatedScenario1() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 1", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 7 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 8 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 9 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Not automated scenario 2")] - public virtual void NotAutomatedScenario2() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 2", ((string[])(null))); -#line 11 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 12 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 13 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 14 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Not automated scenario 3")] - public virtual void NotAutomatedScenario3() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 3", ((string[])(null))); -#line 16 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 17 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 18 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/Properties/AssemblyInfo.cs b/test-harness/nunit/Properties/AssemblyInfo.cs deleted file mode 100644 index 0446e36be..000000000 --- a/test-harness/nunit/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,36 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("nunit")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("")] -[assembly: AssemblyProduct("nunit")] -[assembly: AssemblyCopyright("Copyright © 2013")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM components. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("ba66d1f7-68a4-4307-ad63-abf63686ef9d")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Build and Revision Numbers -// by using the '*' as shown below: -// [assembly: AssemblyVersion("1.0.*")] -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/test-harness/nunit/ScenarioOutlines.feature b/test-harness/nunit/ScenarioOutlines.feature deleted file mode 100644 index 74f50e2af..000000000 --- a/test-harness/nunit/ScenarioOutlines.feature +++ /dev/null @@ -1,143 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - -Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - And I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - -Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - -Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - -Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - -Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | \ No newline at end of file diff --git a/test-harness/nunit/ScenarioOutlines.feature.cs b/test-harness/nunit/ScenarioOutlines.feature.cs deleted file mode 100644 index f53655b02..000000000 --- a/test-harness/nunit/ScenarioOutlines.feature.cs +++ /dev/null @@ -1,256 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Scenario Outlines")] - public partial class ScenarioOutlinesFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenarioOutlines.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenario Outlines", "Here we demonstrate how we deal with scenario outlines", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline where all scenarios pass")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("pass_3", null)] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where all scenarios pass", exampleTags); -#line 4 -this.ScenarioSetup(scenarioInfo); -#line 8 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline where one scenario is inconclusive")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive_1", null)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario is inconclusive", exampleTags); -#line 17 -this.ScenarioSetup(scenarioInfo); -#line 21 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline where one scenario fails")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("fail_1", null)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario fails", exampleTags); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 34 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive_1", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive_2", null)] - [NUnit.Framework.TestCaseAttribute("fail_1", null)] - [NUnit.Framework.TestCaseAttribute("fail_2", null)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections_(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("And we can go totally bonkers with multiple example sections.", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 45 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal correctly with backslashes in the examples")] - [NUnit.Framework.TestCaseAttribute("c:\\Temp\\", null)] - public virtual void DealCorrectlyWithBackslashesInTheExamples(string filePath, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with backslashes in the examples", exampleTags); -#line 63 -this.ScenarioSetup(scenarioInfo); -#line 65 - testRunner.When(string.Format("I have backslashes in the value, for example a \'{0}\'", filePath), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal correctly with parenthesis in the examples")] - [NUnit.Framework.TestCaseAttribute("This is a description (and more)", null)] - public virtual void DealCorrectlyWithParenthesisInTheExamples(string overlyDescriptiveField, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with parenthesis in the examples", exampleTags); -#line 72 -this.ScenarioSetup(scenarioInfo); -#line 74 - testRunner.When(string.Format("I have parenthesis in the value, for example an \'{0}\'", overlyDescriptiveField), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal correctly with overlong example values")] - [NUnit.Framework.TestCaseAttribute("Please enter a valid two letter country code (e.g. DE)!", "This is just a very very very veery long error message!", null)] - public virtual void DealCorrectlyWithOverlongExampleValues(string value1, string value2, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with overlong example values", exampleTags); -#line 80 -this.ScenarioSetup(scenarioInfo); -#line 82 - testRunner.When(string.Format("I have a field with value \'{0}\'", value1), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 83 - testRunner.And(string.Format("I have a field with value \'{0}\'", value2), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 84 - testRunner.Then("the scenario will \'pass_1\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - public virtual void DealWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with duplicate values", exampleTags); -#line 90 -this.ScenarioSetup(scenarioInfo); -#line 91 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple example sections with duplicate values", exampleTags); -#line 101 -this.ScenarioSetup(scenarioInfo); -#line 102 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with multiple named example sections without duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections without duplicate values", exampleTags); -#line 117 -this.ScenarioSetup(scenarioInfo); -#line 118 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections with duplicate values", exampleTags); -#line 129 -this.ScenarioSetup(scenarioInfo); -#line 130 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/ScenariosWithSpecialCharacters.feature b/test-harness/nunit/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index c4bbe7971..000000000 --- a/test-harness/nunit/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,53 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'PASS' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This is a scenario outline with ampersand & - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step diff --git a/test-harness/nunit/ScenariosWithSpecialCharacters.feature.cs b/test-harness/nunit/ScenariosWithSpecialCharacters.feature.cs deleted file mode 100644 index c8ed82c11..000000000 --- a/test-harness/nunit/ScenariosWithSpecialCharacters.feature.cs +++ /dev/null @@ -1,200 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Scenarios With Special Characters")] - public partial class ScenariosWithSpecialCharactersFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenariosWithSpecialCharacters.feature" -#line hidden - - [NUnit.Framework.TestFixtureSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenarios With Special Characters", "Here we demonstrate usage of special characters in scenario names", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.TestFixtureTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)")] - public virtual void ThisIsAScenarioWithParenthesesHyphenAndComma10_2030_40() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)", ((string[])(null))); -#line 7 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 8 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 9 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 10 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 11 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [NUnit.Framework.TestCaseAttribute("**", null)] - [NUnit.Framework.TestCaseAttribute("++", null)] - [NUnit.Framework.TestCaseAttribute(".*", null)] - [NUnit.Framework.TestCaseAttribute("[]", null)] - [NUnit.Framework.TestCaseAttribute("{}", null)] - [NUnit.Framework.TestCaseAttribute("()", null)] - [NUnit.Framework.TestCaseAttribute("^.*(?BAR)\\s[^0-9]{3,4}A+$", null)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters(string regex, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This scenario contains examples with Regex-special characters", exampleTags); -#line 21 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 22 - testRunner.When(string.Format("I have special characters for regexes in the value, for example a \'{0}\'", regex), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 23 - testRunner.Then("the scenario will \'PASS\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline with german umlauts äöüß ÄÖÜ")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with german umlauts äöüß ÄÖÜ", exampleTags); -#line 35 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 36 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline with ampersand &")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - public virtual void ThisIsAScenarioOutlineWithAmpersand(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with ampersand &", exampleTags); -#line 42 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 43 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario with danish characters æøå ÆØÅ")] - public virtual void ThisIsAScenarioWithDanishCharactersAEoaAEOA() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with danish characters æøå ÆØÅ", ((string[])(null))); -#line 49 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 50 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario with spanish characters ñáéíóú")] - public virtual void ThisIsAScenarioWithSpanishCharactersNaeiou() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with spanish characters ñáéíóú", ((string[])(null))); -#line 52 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 53 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit/nunit.csproj b/test-harness/nunit/nunit.csproj deleted file mode 100644 index 5f3832088..000000000 --- a/test-harness/nunit/nunit.csproj +++ /dev/null @@ -1,145 +0,0 @@ - - - - - Debug - AnyCPU - {C13BF896-768D-47BC-86A0-99BC53CC54E6} - Library - Properties - Pickles.TestHarness.nunit - nunitHarness - v4.5 - 512 - ..\ - true - - - true - full - false - bin\Debug\ - DEBUG;TRACE - prompt - 4 - - - pdbonly - true - bin\Release\ - TRACE - prompt - 4 - - - - ..\packages\NUnit.2.7.0\lib\nunit.framework.dll - - - - - - - - - - ..\packages\SpecFlow.1.9.0\lib\net35\TechTalk.SpecFlow.dll - - - - - True - True - Addition.feature - - - FailingBackground.feature - True - True - - - Failing.feature - True - True - - - Inconclusive.feature - True - True - - - Passing.feature - True - True - - - True - True - NotAutomatedAtAll.feature - - - - ScenarioOutlines.feature - True - True - - - True - True - ScenariosWithSpecialCharacters.feature - - - - - SpecFlowSingleFileGenerator - Addition.feature.cs - - - - SpecFlowSingleFileGenerator - FailingBackground.feature.cs - - - SpecFlowSingleFileGenerator - Failing.feature.cs - - - SpecFlowSingleFileGenerator - Inconclusive.feature.cs - - - SpecFlowSingleFileGenerator - Passing.feature.cs - - - SpecFlowSingleFileGenerator - NotAutomatedAtAll.feature.cs - - - - SpecFlowSingleFileGenerator - ScenarioOutlines.feature.cs - - - SpecFlowSingleFileGenerator - ScenariosWithSpecialCharacters.feature.cs - - - - - {073862de-d599-4941-9716-03206cf1cfa2} - AutomationLayer - - - - - - - - \ No newline at end of file diff --git a/test-harness/nunit/packages.config b/test-harness/nunit/packages.config deleted file mode 100644 index 26ecd1153..000000000 --- a/test-harness/nunit/packages.config +++ /dev/null @@ -1,7 +0,0 @@ - - - - - - - \ No newline at end of file diff --git a/test-harness/nunit3/Addition.feature b/test-harness/nunit3/Addition.feature deleted file mode 100644 index 238e261e9..000000000 --- a/test-harness/nunit3/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/nunit3/Addition.feature.cs b/test-harness/nunit3/Addition.feature.cs deleted file mode 100644 index 27fd91d89..000000000 --- a/test-harness/nunit3/Addition.feature.cs +++ /dev/null @@ -1,198 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Addition")] - public partial class AdditionFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Addition.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Addition", "In order to avoid silly mistakes\r\nAs a math idiot\r\nI want to be told the sum of t" + - "wo numbers", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 6 -#line 7 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Adding several numbers")] - [NUnit.Framework.CategoryAttribute("tag2")] - [NUnit.Framework.TestCaseAttribute("60", "70", "130", "260", null)] - [NUnit.Framework.TestCaseAttribute("40", "50", "90", "180", null)] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - string[] @__tags = new string[] { - "tag2"}; - if ((exampleTags != null)) - { - @__tags = System.Linq.Enumerable.ToArray(System.Linq.Enumerable.Concat(@__tags, exampleTags)); - } - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", @__tags); -#line 10 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 11 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 12 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 13 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 14 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 15 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Add two numbers")] - [NUnit.Framework.CategoryAttribute("tag1")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", new string[] { - "tag1"}); -#line 23 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 24 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 25 - testRunner.And("I have entered 2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 26 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 27 - testRunner.Then("the result should be 3 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Fail to add two numbers")] - [NUnit.Framework.CategoryAttribute("tag1")] - public virtual void FailToAddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Fail to add two numbers", new string[] { - "tag1"}); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 31 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 32 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 33 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 34 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Ignored adding two numbers")] - [NUnit.Framework.IgnoreAttribute("")] - public virtual void IgnoredAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Ignored adding two numbers", new string[] { - "ignore"}); -#line 37 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 38 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 39 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 40 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 41 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Not automated adding two numbers")] - public virtual void NotAutomatedAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated adding two numbers", ((string[])(null))); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 44 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 45 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 46 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/App.config b/test-harness/nunit3/App.config deleted file mode 100644 index 6a85a1d39..000000000 --- a/test-harness/nunit3/App.config +++ /dev/null @@ -1,13 +0,0 @@ - - - -
          - - - - - - - - - \ No newline at end of file diff --git a/test-harness/nunit3/FailingBackground.feature b/test-harness/nunit3/FailingBackground.feature deleted file mode 100644 index 83a70483a..000000000 --- a/test-harness/nunit3/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/nunit3/FailingBackground.feature.cs b/test-harness/nunit3/FailingBackground.feature.cs deleted file mode 100644 index 735588239..000000000 --- a/test-harness/nunit3/FailingBackground.feature.cs +++ /dev/null @@ -1,125 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Background")] - public partial class FailingBackgroundFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "FailingBackground.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing Background", "This feature has a failing background.", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the background step fails", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 6 - testRunner.And("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line hidden - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Add two numbers")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", ((string[])(null))); -#line 8 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 9 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 10 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 11 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 12 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Adding several numbers")] - [NUnit.Framework.TestCaseAttribute("60", "70", "130", "260", null)] - [NUnit.Framework.TestCaseAttribute("40", "50", "90", "180", null)] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 16 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 17 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 18 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/Minimal Features/Failing.feature b/test-harness/nunit3/Minimal Features/Failing.feature deleted file mode 100644 index d7c5b7f53..000000000 --- a/test-harness/nunit3/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step \ No newline at end of file diff --git a/test-harness/nunit3/Minimal Features/Failing.feature.cs b/test-harness/nunit3/Minimal Features/Failing.feature.cs deleted file mode 100644 index 022a994b3..000000000 --- a/test-harness/nunit3/Minimal Features/Failing.feature.cs +++ /dev/null @@ -1,108 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing")] - public partial class FailingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Failing.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Feature Passing Scenario")] - public virtual void FailingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Feature Inconclusive Scenario")] - public virtual void FailingFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Failing Feature Failing Scenario")] - public virtual void FailingFeatureFailingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Failing Scenario", ((string[])(null))); -#line 9 -this.ScenarioSetup(scenarioInfo); -#line 10 - testRunner.Then("failing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/Minimal Features/Inconclusive.feature b/test-harness/nunit3/Minimal Features/Inconclusive.feature deleted file mode 100644 index 40c27b402..000000000 --- a/test-harness/nunit3/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step \ No newline at end of file diff --git a/test-harness/nunit3/Minimal Features/Inconclusive.feature.cs b/test-harness/nunit3/Minimal Features/Inconclusive.feature.cs deleted file mode 100644 index bbfc5bdf2..000000000 --- a/test-harness/nunit3/Minimal Features/Inconclusive.feature.cs +++ /dev/null @@ -1,95 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Inconclusive")] - public partial class InconclusiveFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Inconclusive.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Inconclusive", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Inconclusive Feature Passing Scenario")] - public virtual void InconclusiveFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Inconclusive Feature Inconclusive Scenario")] - public virtual void InconclusiveFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/Minimal Features/Passing.feature b/test-harness/nunit3/Minimal Features/Passing.feature deleted file mode 100644 index 14bf35e22..000000000 --- a/test-harness/nunit3/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/nunit3/Minimal Features/Passing.feature.cs b/test-harness/nunit3/Minimal Features/Passing.feature.cs deleted file mode 100644 index f38719008..000000000 --- a/test-harness/nunit3/Minimal Features/Passing.feature.cs +++ /dev/null @@ -1,82 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Passing")] - public partial class PassingFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Passing.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Passing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Passing Feature Passing Scenario")] - public virtual void PassingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Passing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/NotAutomatedAtAll.feature b/test-harness/nunit3/NotAutomatedAtAll.feature deleted file mode 100644 index fe34b832d..000000000 --- a/test-harness/nunit3/NotAutomatedAtAll.feature +++ /dev/null @@ -1,11 +0,0 @@ -Feature: NotAutomatedAtAll - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -@mytag -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen diff --git a/test-harness/nunit3/NotAutomatedAtAll.feature.cs b/test-harness/nunit3/NotAutomatedAtAll.feature.cs deleted file mode 100644 index 0b9cb48b5..000000000 --- a/test-harness/nunit3/NotAutomatedAtAll.feature.cs +++ /dev/null @@ -1,91 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("NotAutomatedAtAll")] - public partial class NotAutomatedAtAllFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "NotAutomatedAtAll.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "NotAutomatedAtAll", "In order to avoid silly mistakes\nAs a math idiot\nI want to be told the sum of two" + - " numbers", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Add two numbers")] - [NUnit.Framework.CategoryAttribute("mytag")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", new string[] { - "mytag"}); -#line 7 -this.ScenarioSetup(scenarioInfo); -#line 8 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 9 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 10 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 11 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/Properties/AssemblyInfo.cs b/test-harness/nunit3/Properties/AssemblyInfo.cs deleted file mode 100644 index a1e149f02..000000000 --- a/test-harness/nunit3/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,36 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("nunit3")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("")] -[assembly: AssemblyProduct("nunit3")] -[assembly: AssemblyCopyright("Copyright © 2015")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM components. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("c5e91aee-8234-443a-a327-6a6581e49d4b")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Build and Revision Numbers -// by using the '*' as shown below: -// [assembly: AssemblyVersion("1.0.*")] -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/test-harness/nunit3/ScenarioOutlines.feature b/test-harness/nunit3/ScenarioOutlines.feature deleted file mode 100644 index 74f50e2af..000000000 --- a/test-harness/nunit3/ScenarioOutlines.feature +++ /dev/null @@ -1,143 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - -Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - And I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - -Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - -Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - -Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - -Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | \ No newline at end of file diff --git a/test-harness/nunit3/ScenarioOutlines.feature.cs b/test-harness/nunit3/ScenarioOutlines.feature.cs deleted file mode 100644 index 5fbcee27d..000000000 --- a/test-harness/nunit3/ScenarioOutlines.feature.cs +++ /dev/null @@ -1,256 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Scenario Outlines")] - public partial class ScenarioOutlinesFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenarioOutlines.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenario Outlines", "Here we demonstrate how we deal with scenario outlines", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline where all scenarios pass")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("pass_3", null)] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where all scenarios pass", exampleTags); -#line 4 -this.ScenarioSetup(scenarioInfo); -#line 8 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline where one scenario is inconclusive")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive_1", null)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario is inconclusive", exampleTags); -#line 17 -this.ScenarioSetup(scenarioInfo); -#line 21 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline where one scenario fails")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("fail_1", null)] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario fails", exampleTags); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 34 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("And we can go totally bonkers with multiple example sections.")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - [NUnit.Framework.TestCaseAttribute("pass_2", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive_1", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive_2", null)] - [NUnit.Framework.TestCaseAttribute("fail_1", null)] - [NUnit.Framework.TestCaseAttribute("fail_2", null)] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections_(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("And we can go totally bonkers with multiple example sections.", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 45 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal correctly with backslashes in the examples")] - [NUnit.Framework.TestCaseAttribute("c:\\Temp\\", null)] - public virtual void DealCorrectlyWithBackslashesInTheExamples(string filePath, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with backslashes in the examples", exampleTags); -#line 63 -this.ScenarioSetup(scenarioInfo); -#line 65 - testRunner.When(string.Format("I have backslashes in the value, for example a \'{0}\'", filePath), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal correctly with parenthesis in the examples")] - [NUnit.Framework.TestCaseAttribute("This is a description (and more)", null)] - public virtual void DealCorrectlyWithParenthesisInTheExamples(string overlyDescriptiveField, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with parenthesis in the examples", exampleTags); -#line 72 -this.ScenarioSetup(scenarioInfo); -#line 74 - testRunner.When(string.Format("I have parenthesis in the value, for example an \'{0}\'", overlyDescriptiveField), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal correctly with overlong example values")] - [NUnit.Framework.TestCaseAttribute("Please enter a valid two letter country code (e.g. DE)!", "This is just a very very very veery long error message!", null)] - public virtual void DealCorrectlyWithOverlongExampleValues(string value1, string value2, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with overlong example values", exampleTags); -#line 80 -this.ScenarioSetup(scenarioInfo); -#line 82 - testRunner.When(string.Format("I have a field with value \'{0}\'", value1), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 83 - testRunner.And(string.Format("I have a field with value \'{0}\'", value2), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 84 - testRunner.Then("the scenario will \'pass_1\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - public virtual void DealWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with duplicate values", exampleTags); -#line 90 -this.ScenarioSetup(scenarioInfo); -#line 91 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with multiple example sections with duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple example sections with duplicate values", exampleTags); -#line 101 -this.ScenarioSetup(scenarioInfo); -#line 102 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with multiple named example sections without duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections without duplicate values", exampleTags); -#line 117 -this.ScenarioSetup(scenarioInfo); -#line 118 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("Deal with multiple named example sections with duplicate values")] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("inconclusive", null)] - [NUnit.Framework.TestCaseAttribute("fail", null)] - [NUnit.Framework.TestCaseAttribute("pass", null)] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections with duplicate values", exampleTags); -#line 129 -this.ScenarioSetup(scenarioInfo); -#line 130 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/ScenariosWithSpecialCharacters.feature b/test-harness/nunit3/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index c4bbe7971..000000000 --- a/test-harness/nunit3/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,53 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'PASS' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This is a scenario outline with ampersand & - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step diff --git a/test-harness/nunit3/ScenariosWithSpecialCharacters.feature.cs b/test-harness/nunit3/ScenariosWithSpecialCharacters.feature.cs deleted file mode 100644 index 9e8276398..000000000 --- a/test-harness/nunit3/ScenariosWithSpecialCharacters.feature.cs +++ /dev/null @@ -1,200 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.nunit3 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - [NUnit.Framework.TestFixtureAttribute()] - [NUnit.Framework.DescriptionAttribute("Scenarios With Special Characters")] - public partial class ScenariosWithSpecialCharactersFeature - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenariosWithSpecialCharacters.feature" -#line hidden - - [NUnit.Framework.OneTimeSetUpAttribute()] - public virtual void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenarios With Special Characters", "Here we demonstrate usage of special characters in scenario names", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - [NUnit.Framework.OneTimeTearDownAttribute()] - public virtual void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - [NUnit.Framework.SetUpAttribute()] - public virtual void TestInitialize() - { - } - - [NUnit.Framework.TearDownAttribute()] - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)")] - public virtual void ThisIsAScenarioWithParenthesesHyphenAndComma10_2030_40() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)", ((string[])(null))); -#line 7 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 8 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 9 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 10 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 11 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This scenario contains examples with Regex-special characters")] - [NUnit.Framework.TestCaseAttribute("**", null)] - [NUnit.Framework.TestCaseAttribute("++", null)] - [NUnit.Framework.TestCaseAttribute(".*", null)] - [NUnit.Framework.TestCaseAttribute("[]", null)] - [NUnit.Framework.TestCaseAttribute("{}", null)] - [NUnit.Framework.TestCaseAttribute("()", null)] - [NUnit.Framework.TestCaseAttribute("^.*(?BAR)\\s[^0-9]{3,4}A+$", null)] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters(string regex, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This scenario contains examples with Regex-special characters", exampleTags); -#line 21 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 22 - testRunner.When(string.Format("I have special characters for regexes in the value, for example a \'{0}\'", regex), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 23 - testRunner.Then("the scenario will \'PASS\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline with german umlauts äöüß ÄÖÜ")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with german umlauts äöüß ÄÖÜ", exampleTags); -#line 35 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 36 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario outline with ampersand &")] - [NUnit.Framework.TestCaseAttribute("pass_1", null)] - public virtual void ThisIsAScenarioOutlineWithAmpersand(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with ampersand &", exampleTags); -#line 42 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 43 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario with danish characters æøå ÆØÅ")] - public virtual void ThisIsAScenarioWithDanishCharactersAEoaAEOA() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with danish characters æøå ÆØÅ", ((string[])(null))); -#line 49 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 50 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [NUnit.Framework.TestAttribute()] - [NUnit.Framework.DescriptionAttribute("This is a scenario with spanish characters ñáéíóú")] - public virtual void ThisIsAScenarioWithSpanishCharactersNaeiou() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with spanish characters ñáéíóú", ((string[])(null))); -#line 52 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 53 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/nunit3/nunit3.csproj b/test-harness/nunit3/nunit3.csproj deleted file mode 100644 index 0fadf8e36..000000000 --- a/test-harness/nunit3/nunit3.csproj +++ /dev/null @@ -1,154 +0,0 @@ - - - - - - Debug - AnyCPU - {C5E91AEE-8234-443A-A327-6A6581E49D4B} - Library - Properties - Pickles.TestHarness.nunit3 - nunit3Harness - v4.5 - 512 - - - - - true - full - false - bin\Debug\ - DEBUG;TRACE - prompt - 4 - - - pdbonly - true - bin\Release\ - TRACE - prompt - 4 - - - - ..\packages\NUnit.3.11.0\lib\net45\nunit.framework.dll - - - - - - - - - - - ..\packages\SpecFlow.1.9.0\lib\net35\TechTalk.SpecFlow.dll - True - - - - - True - True - Addition.feature - - - FailingBackground.feature - True - True - - - Failing.feature - True - True - - - Inconclusive.feature - True - True - - - Passing.feature - True - True - - - True - True - NotAutomatedAtAll.feature - - - - ScenarioOutlines.feature - True - True - - - True - True - ScenariosWithSpecialCharacters.feature - - - - - SpecFlowSingleFileGenerator - Addition.feature.cs - - - - SpecFlowSingleFileGenerator - FailingBackground.feature.cs - - - SpecFlowSingleFileGenerator - Failing.feature.cs - - - SpecFlowSingleFileGenerator - Inconclusive.feature.cs - - - SpecFlowSingleFileGenerator - Passing.feature.cs - - - SpecFlowSingleFileGenerator - NotAutomatedAtAll.feature.cs - - - - SpecFlowSingleFileGenerator - ScenarioOutlines.feature.cs - - - SpecFlowSingleFileGenerator - ScenariosWithSpecialCharacters.feature.cs - - - - - {073862de-d599-4941-9716-03206cf1cfa2} - AutomationLayer - - - - - - - - - This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}. - - - - - \ No newline at end of file diff --git a/test-harness/nunit3/packages.config b/test-harness/nunit3/packages.config deleted file mode 100644 index cb92cc4b9..000000000 --- a/test-harness/nunit3/packages.config +++ /dev/null @@ -1,13 +0,0 @@ - - - - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/HTML.xslt b/test-harness/packagesNonNuget/xunit.runner/HTML.xslt deleted file mode 100644 index 2a1a4c72a..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/HTML.xslt +++ /dev/null @@ -1,126 +0,0 @@ - - - - - ]]> - - - - xUnit.net Test Results - <xsl:value-of select="@name"/> - - - - - -

          Assemblies Run

          - - -

          Summary

          -
          - Tests run:   - Failures: , - Skipped: , - Run time: s -
          - -
          -

          Failed tests

          - -           - -
          -

          Failed fixtures

          - -           - -
          -

          Skipped tests

          - -           -
          -

          All tests

          -
          Click test class name to expand/collapse test details
          - - - -           - - -
          -           - - -
          - altrow - s - Skipped❢ - ✘ - ✔ -   - : -
          - -
          -           - -

          Output

          -
          -           -
          -           - - - ✘ :
          - Stack Trace:
          -
          -           - - -

          - s - - ToggleClass('class') - ToggleClass('class') - ✘ - ✔ -   -  ( tests) - -
          -

          -
          - display: none; - class - -
          -           - -           \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/NUnitXml.xslt b/test-harness/packagesNonNuget/xunit.runner/NUnitXml.xslt deleted file mode 100644 index 4d82799f5..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/NUnitXml.xslt +++ /dev/null @@ -1,121 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - False - True - - - - - - - - - - - - - - - - - - False - True - - - - - - - - - - - - - - - - - - - - - - - - - False - True - - - - False - True - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/license.txt b/test-harness/packagesNonNuget/xunit.runner/license.txt deleted file mode 100644 index b9e8a2b5d..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/license.txt +++ /dev/null @@ -1,13 +0,0 @@ -Copyright 2013 Outercurve Foundation - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.exe deleted file mode 100644 index 25553d9fc..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.exe.config b/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.exe.config deleted file mode 100644 index 1aae4c31f..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.exe.config +++ /dev/null @@ -1,21 +0,0 @@ - - - - -
          - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.x86.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.x86.exe deleted file mode 100644 index 7b0dc7afd..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.x86.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.x86.exe.config b/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.x86.exe.config deleted file mode 100644 index 24ca922c9..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.console.clr4.x86.exe.config +++ /dev/null @@ -1,21 +0,0 @@ - - - - -
          - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.console.exe deleted file mode 100644 index 08ede11a1..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.console.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.exe.config b/test-harness/packagesNonNuget/xunit.runner/xunit.console.exe.config deleted file mode 100644 index a253b460d..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.console.exe.config +++ /dev/null @@ -1,21 +0,0 @@ - - - - -
          - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.x86.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.console.x86.exe deleted file mode 100644 index 4976fa087..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.console.x86.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.console.x86.exe.config b/test-harness/packagesNonNuget/xunit.runner/xunit.console.x86.exe.config deleted file mode 100644 index 89e63fa2e..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.console.x86.exe.config +++ /dev/null @@ -1,21 +0,0 @@ - - - - -
          - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.dll b/test-harness/packagesNonNuget/xunit.runner/xunit.dll deleted file mode 100644 index c2534a82a..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.dll and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.dll.tdnet b/test-harness/packagesNonNuget/xunit.runner/xunit.dll.tdnet deleted file mode 100644 index 4d8afc8ef..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.dll.tdnet +++ /dev/null @@ -1,5 +0,0 @@ - - xUnit.net {0}.{1}.{2} build {3} - xunit.runner.tdnet.dll - Xunit.Runner.TdNet.TdNetRunner - \ No newline at end of file diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.extensions.dll b/test-harness/packagesNonNuget/xunit.runner/xunit.extensions.dll deleted file mode 100644 index ea46cb16c..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.extensions.dll and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.extensions.xml b/test-harness/packagesNonNuget/xunit.runner/xunit.extensions.xml deleted file mode 100644 index a0718b1d6..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.extensions.xml +++ /dev/null @@ -1,811 +0,0 @@ - - - - xunit.extensions - - - - - A wrapper for Assert which is used by . - - - - - Verifies that a collection contains a given object. - - The type of the object to be verified - The object expected to be in the collection - The collection to be inspected - Thrown when the object is not present in the collection - - - - Verifies that a collection contains a given object, using an equality comparer. - - The type of the object to be verified - The object expected to be in the collection - The collection to be inspected - The comparer used to equate objects in the collection with the expected object - Thrown when the object is not present in the collection - - - - Verifies that a string contains a given sub-string, using the current culture. - - The sub-string expected to be in the string - The string to be inspected - Thrown when the sub-string is not present inside the string - - - - Verifies that a string contains a given sub-string, using the given comparison type. - - The sub-string expected to be in the string - The string to be inspected - The type of string comparison to perform - Thrown when the sub-string is not present inside the string - - - - Verifies that a collection does not contain a given object. - - The type of the object to be compared - The object that is expected not to be in the collection - The collection to be inspected - Thrown when the object is present inside the container - - - - Verifies that a collection does not contain a given object, using an equality comparer. - - The type of the object to be compared - The object that is expected not to be in the collection - The collection to be inspected - The comparer used to equate objects in the collection with the expected object - Thrown when the object is present inside the container - - - - Verifies that a string does not contain a given sub-string, using the current culture. - - The sub-string which is expected not to be in the string - The string to be inspected - Thrown when the sub-string is present inside the string - - - - Verifies that a string does not contain a given sub-string, using the current culture. - - The sub-string which is expected not to be in the string - The string to be inspected - The type of string comparison to perform - Thrown when the sub-string is present inside the given string - - - - Verifies that a block of code does not throw any exceptions. - - A delegate to the code to be tested - - - - Verifies that a collection is empty. - - The collection to be inspected - Thrown when the collection is null - Thrown when the collection is not empty - - - - Verifies that two objects are equal, using a default comparer. - - The type of the objects to be compared - The expected value - The value to be compared against - Thrown when the objects are not equal - - - - Verifies that two objects are equal, using a custom equatable comparer. - - The type of the objects to be compared - The expected value - The value to be compared against - The comparer used to compare the two objects - Thrown when the objects are not equal - - - - Verifies that two values are equal, within the number of decimal - places given by . - - The expected value - The value to be compared against - The number of decimal places (valid values: 0-15) - Thrown when the values are not equal - - - - Verifies that two values are equal, within the number of decimal - places given by . - - The expected value - The value to be compared against - The number of decimal places (valid values: 0-15) - Thrown when the values are not equal - - - - Verifies that the condition is false. - - The condition to be tested - Thrown if the condition is not false - - - - Verifies that the condition is false. - - The condition to be tested - The message to show when the condition is not false - Thrown if the condition is not false - - - - Verifies that a value is within a given range. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - Thrown when the value is not in the given range - - - - Verifies that a value is within a given range, using a comparer. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - The comparer used to evaluate the value's range - Thrown when the value is not in the given range - - - - Verifies that an object is of the given type or a derived type. - - The type the object should be - The object to be evaluated - The object, casted to type T when successful - Thrown when the object is not the given type - - - - Verifies that an object is of the given type or a derived type. - - The type the object should be - The object to be evaluated - Thrown when the object is not the given type - - - - Verifies that an object is not exactly the given type. - - The type the object should not be - The object to be evaluated - Thrown when the object is the given type - - - - Verifies that an object is not exactly the given type. - - The type the object should not be - The object to be evaluated - Thrown when the object is the given type - - - - Verifies that an object is exactly the given type (and not a derived type). - - The type the object should be - The object to be evaluated - The object, casted to type T when successful - Thrown when the object is not the given type - - - - Verifies that an object is exactly the given type (and not a derived type). - - The type the object should be - The object to be evaluated - Thrown when the object is not the given type - - - - Verifies that a collection is not empty. - - The collection to be inspected - Thrown when a null collection is passed - Thrown when the collection is empty - - - - Verifies that two objects are not equal, using a default comparer. - - The type of the objects to be compared - The expected object - The actual object - Thrown when the objects are equal - - - - Verifies that two objects are not equal, using a custom equality comparer. - - The type of the objects to be compared - The expected object - The actual object - The comparer used to examine the objects - Thrown when the objects are equal - - - - Verifies that a value is not within a given range, using the default comparer. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - Thrown when the value is in the given range - - - - Verifies that a value is not within a given range, using a comparer. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - The comparer used to evaluate the value's range - Thrown when the value is in the given range - - - - Verifies that an object reference is not null. - - The object to be validated - Thrown when the object is not null - - - - Verifies that two objects are not the same instance. - - The expected object instance - The actual object instance - Thrown when the objects are the same instance - - - - Verifies that an object reference is null. - - The object to be inspected - Thrown when the object reference is not null - - - - Verifies that two objects are the same instance. - - The expected object instance - The actual object instance - Thrown when the objects are not the same instance - - - - Verifies that the given collection contains only a single - element of the given type. - - The collection. - The single item in the collection. - Thrown when the collection does not contain - exactly one element. - - - - Verifies that the given collection contains only a single - element of the given type. - - The collection type. - The collection. - The single item in the collection. - Thrown when the collection does not contain - exactly one element. - - - - Verifies that the exact exception is thrown (and not a derived exception type). - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that the exact exception is thrown (and not a derived exception type). - Generally used to test property accessors. - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that the exact exception is thrown (and not a derived exception type). - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that the exact exception is thrown (and not a derived exception type). - Generally used to test property accessors. - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that an expression is true. - - The condition to be inspected - Thrown when the condition is false - - - - Verifies that an expression is true. - - The condition to be inspected - The message to be shown when the condition is false - Thrown when the condition is false - - - - A class which can be derived from for test classes, which bring an overridable version - of Assert (using the class. - - - - - Gets a class which provides assertions. - - - - - Apply this attribute to your test method to replace the - with another role. - - - - - Replaces the identity of the current thread with . - - The role's name - - - - Restores the original . - - The method under test - - - - Stores the current and replaces it with - a new role identified in constructor. - - The method under test - - - - Gets the name. - - - - - Apply this attribute to your test method to automatically create a - that is rolled back when the test is - finished. - - - - - Rolls back the transaction. - - - - - Creates the transaction. - - - - - Gets or sets the isolation level of the transaction. - Default value is .Unspecified. - - - - - Gets or sets the scope option for the transaction. - Default value is .Required. - - - - - Gets or sets the timeout of the transaction, in milliseconds. - By default, the transaction will not timeout. - - - - - Provides a data source for a data theory, with the data coming from a class - which must implement IEnumerable<object[]>. - - - - - Abstract attribute which represents a data source for a data theory. - Data source providers derive from this attribute and implement GetData - to return the data for the theory. - - - - - Returns the data to be used to test the theory. - - - The parameter is provided so that the - test data can be converted to the destination parameter type when necessary. - Generally, data should NOT be automatically converted, UNLESS the source data - format does not have rich types (for example, all numbers in Excel spreadsheets - are returned as even if they are integers). Derivers of - this class should NOT throw exceptions for mismatched types or mismatched number - of parameters; the test framework will throw these exceptions at the correct - time. - - The method that is being tested - The types of the parameters for the test method - The theory data - - - - - - - Initializes a new instance of the class. - - The class that provides the data. - - - - - - - Gets the type of the class that provides the data. - - - - - Represents an implementation of which uses an - instance of to get the data for a - decorated test method. - - - - - - - - Converts a parameter to its destination parameter type, if necessary. - - The parameter value - The destination parameter type (null if not known) - The converted parameter value - - - - Gets the data adapter to be used to retrieve the test data. - - - - - Provides a data source for a data theory, with the data coming from inline values. - - - - - Initializes a new instance of the class. - - The data values to pass to the theory - - - - Returns the data to be used to test the theory. - - The method that is being tested - The types of the parameters for the test method - The theory data, in table form - - - - Gets the data values. - - - - - Provides a data source for a data theory, with the data coming from an OLEDB connection. - - - - - Creates a new instance of . - - The OLEDB connection string to the data - The SELECT statement used to return the data for the theory - - - - Gets the connection string. - - - - - Gets the select statement. - - - - - - - - Provides a data source for a data theory, with the data coming from a public static property on the test class. - The property must return IEnumerable<object[]> with the test data. - - - - - Creates a new instance of / - - The name of the public static property on the test class that will provide the test data - - - - Returns the data to be used to test the theory. - - The method that is being tested - The types of the parameters for the test method - The theory data, in table form - - - - Gets the property name. - - - - - Gets or sets the type to retrieve the property data from. If not set, then the property will be - retrieved from the unit test class. - - - - - Provides a data source for a data theory, with the data coming a Microsoft SQL Server. - - - - - Creates a new instance of , using a trusted connection. - - The server name of the Microsoft SQL Server - The database name - The SQL SELECT statement to return the data for the data theory - - - - Creates a new instance of , using the provided username and password. - - The server name of the Microsoft SQL Server - The database name - The username for the server - The password for the server - The SQL SELECT statement to return the data for the data theory - - - - Provides a data source for a data theory, with the data coming a Microsoft Excel (.xls) spreadsheet. - - - - - Creates a new instance of . - - The filename of the XLS spreadsheet file; if the filename provided - is relative, then it is relative to the location of xunit.extensions.dll. - The SELECT statement that returns the data for the theory - - - - - - - A wrapper around the static operations on which allows time - to be frozen using the . The clock begins in the - thawed state; that is, calls to , , and - return current (non-frozen) values. - - - - - Freezes the clock with the current time. - Until is called, all calls to , , and - will return the exact same values. - - - - - Freezes the clock with the given date and time, considered to be local time. - Until is called, all calls to , , and - will return the exact same values. - - The local date and time to freeze to - - - - Freezes the clock with the given date and time, considered to be Coordinated Universal Time (UTC). - Until is called, all calls to , , and - will return the exact same values. - - The UTC date and time to freeze to - - - - Thaws the clock so that , , and - return normal values. - - - - - Gets a object that is set to the current date and time on this computer, - expressed as the local time. - - - - - Gets the current date. - - - - - Gets a object that is set to the current date and time on this computer, - expressed as the Coordinated Universal Time (UTC). - - - - - Apply this attribute to your test method to freeze the time represented by the - class. - - - - - Freeze the clock with the current date and time. - - - - - Freeze the clock with the given date, considered to be local time. - - The frozen year - The frozen month - The frozen day - - - - Freeze the clock with the given date and time, considered to be in local time. - - The frozen year - The frozen month - The frozen day - The frozen hour - The frozen minute - The frozen second - - - - Freeze the clock with the given date and time, with the given kind of time. - - The frozen year - The frozen month - The frozen day - The frozen hour - The frozen minute - The frozen second - The frozen time kind - - - - Thaws the clock. - - The method under test - - - - Freezes the clock. - - The method under test - - - - Marks a test method as being a data theory. Data theories are tests which are fed - various bits of data from a data source, mapping to parameters on the test method. - If the data source contains multiple rows, then the test method is executed - multiple times (once with each data row). - - - - - Creates instances of which represent individual intended - invocations of the test method, one per data row in the data source. - - The method under test - An enumerator through the desired test method invocations - - - - Represents a single invocation of a data theory test method. - - - - - Creates a new instance of . - - The method under test - The parameters to be passed to the test method - - - - Creates a new instance of based on a generic theory. - - The method under test - The parameters to be passed to the test method - The generic types that were used to resolved the generic method. - - - - - - - Gets the parameter values that are passed to the test method. - - - - - Apply to a test method to trace the method begin and end. - - - - - This method is called before the test method is executed. - - The method under test - - - - This method is called after the test method is executed. - - The method under test - - - diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.clr4.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.gui.clr4.exe deleted file mode 100644 index e2ab1b197..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.clr4.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.clr4.x86.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.gui.clr4.x86.exe deleted file mode 100644 index 22465a7df..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.clr4.x86.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.gui.exe deleted file mode 100644 index 212499861..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.x86.exe b/test-harness/packagesNonNuget/xunit.runner/xunit.gui.x86.exe deleted file mode 100644 index 7f73bb2fb..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.gui.x86.exe and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.msbuild.dll b/test-harness/packagesNonNuget/xunit.runner/xunit.runner.msbuild.dll deleted file mode 100644 index 020857f9c..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.msbuild.dll and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.tdnet.dll b/test-harness/packagesNonNuget/xunit.runner/xunit.runner.tdnet.dll deleted file mode 100644 index 2c5b1b38e..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.tdnet.dll and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.utility.dll b/test-harness/packagesNonNuget/xunit.runner/xunit.runner.utility.dll deleted file mode 100644 index c22d73336..000000000 Binary files a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.utility.dll and /dev/null differ diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.utility.xml b/test-harness/packagesNonNuget/xunit.runner/xunit.runner.utility.xml deleted file mode 100644 index 0b2e37bd2..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.runner.utility.xml +++ /dev/null @@ -1,1212 +0,0 @@ - - - - xunit.runner.utility - - - - - Guard class, used for guard clauses and argument validation - - - - - - - - - - - - - - Wraps calls to the Executor. Used by runners to perform version-resilient test - enumeration and execution. - - - - - Wraps calls to the Executor. Used by runners to perform version-resilient test - enumeration and execution. - - - - - Enumerates the tests in an assembly. - - The fully-formed assembly node of the XML - - - - Gets a count of the tests in the assembly. - - Returns the number of tests, if known; returns -1 if not known. May not represent - an exact count, but should be a best effort guess by the framework. - - - - Runs all the tests in an assembly. - - The callback which is called as each test/class/assembly is - finished, providing XML nodes that are part of the xUnit.net XML output format. - Test runs can be cancelled by returning false to the callback. If null, there are - no status callbacks (and cancellation isn't possible). - Returns the fully-formed assembly node for the assembly that was just run. - - - - Runs all the tests in the given class. - - The type. - The callback which is called as each test/class is - finished, providing XML nodes that are part of the xUnit.net XML output format. - Test runs can be cancelled by returning false to the callback. If null, there are - no status callbacks (and cancellation isn't possible). - Returns the fully-formed class node for the class that was just run. - - - - Runs a single test in a class. - - The type to run. - The method to run. - The callback which is called as each test/class is - finished, providing XML nodes that are part of the xUnit.net XML output format. - Test runs can be cancelled by returning false to the callback. If null, there are - no status callbacks (and cancellation isn't possible). - Returns the fully-formed class node for the class of the test that was just run. - - - - Runs several tests in a single class. - - The type. - The methods to run. - The callback which is called as each test/class is - finished, providing XML nodes that are part of the xUnit.net XML output format. - Test runs can be cancelled by returning false to the callback. If null, there are - no status callbacks (and cancellation isn't possible). - Returns the fully-formed class node for the class of the tests that were just run. - - - - Gets the full pathname to the assembly under test. - - - - - Gets the full pathname to the configuration file. - - - - - Gets the version of xunit.dll used by the test assembly. - - - - - Initializes the class. - - - - - Initializes a new instance of the class. - - The assembly filename. - The config filename. If null, the default config filename will be used. - Set to true to enable shadow copying; false, otherwise. - - - - Performs application-defined tasks associated with freeing, releasing, or resetting unmanaged resources. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - THIS CLASS IS FOR INTERNAL USE ONLY. - - - - - - - - - - - THIS CLASS IS FOR INTERNAL USE ONLY. - - - - - - - - - - - - - - THIS CLASS IS FOR INTERNAL USE ONLY. - - - - - - - - - - - - - - THIS CLASS IS FOR INTERNAL USE ONLY. - - - - - - - - - - - - - - - - - - - - - - - THIS CLASS IS FOR INTERNAL USE ONLY. - - - - - - - - - - - - - - - - - THIS CLASS IS FOR INTERNAL USE ONLY. - - - - - - - - - - - - - - THIS CLASS IS FOR INTERNAL USE ONLY. - - - - - - - - - - - The callback object which receives real-time status notifications from the - test runner. - - - - - Called when the assembly has finished running. - - The test assembly. - The total number of tests run. - The number of failed tests. - The number of skipped tests. - The time taken to run, in seconds. - - - - Called when the assembly has started running. - - The test assembly. - - - - Called when a class failure is encountered (i.e., when a fixture from - IUseFixture throws an exception during construction or . - - The test class. - The full type name of the exception. - The exception message. - The exception stack trace. - - - - - Called when an exception is thrown (i.e., a catastrophic failure of the testing system). - - The test assembly. - The exception that was thrown. - - - - Called when a test has finished running, regardless of what the result was. - - The test method. - Return true to continue running tests; return false to stop the test run. - - - - Called when a test has started running. - - The test method. - Return true to continue running tests; return false to stop the test run. - - - - Represents the ability to load and unload test assemblies, as well as enumerate - the test assemblies, the test methods, and run tests. - - - - - Represents the ability to enumerate and filter test methods. - - - - - Enumerates all test methods. - - - - - Enumerates test methods which pass the given filter. - - The test method filter. - - - - The test assemblies loaded into the environment. - - - - - - - - Enumerates the test assemblies in the environment. - - - - - - - - - - - Enumerates the traits across all the loaded assemblies. - - - - - Loads the specified assembly, using the default configuration file. - - The assembly filename. - The which represents the newly - loaded test assembly. - - - - Loads the specified assembly using the specified configuration file. - - The assembly filename. - The config filename. - The which represents the newly - loaded test assembly. - - - - Loads the specified assembly using the specified configuration file. - - The assembly filename. - The config filename. - Whether the DLLs should be shadow copied. - The which represents the newly - loaded test assembly. - - - - Adds the assembly loaded into the given - into the environment. - - The executor wrapper. - The which represents the newly - loaded test assembly. - - - - Runs the specified test methods. - - The test methods to run. - The run status information callback. - Returns the result as XML. - - - - Unloads the specified assembly. - - The assembly to unload. - - - - Represents a failed test run in the object model. - - - - - Base class for all test results in the object model. - - - - - Initializes a new instance of the class. - - The duration the test took to run. For skipped tests, should be 0.0. - The display name of the test result. - - - - Gets the display name of the test result. - - - - - Gets the duration the test took to run. - - - - - Initializes a new instance of the class. - - The duration the test took to run. - The display name of the test result. - The output that was captured during the test run. - Type of the exception. - The exception message. - The exception stack trace. - - - - Gets the output that was captured during the test run. - - - - - Gets the type of the exception. - - - - - Gets the exception message. - - - - - Gets the exception stack trace. - - - - - Represents a skipped test run in the object model. - - - - - Initializes a new instance of the class. - - The display name of the test result. - The skip reason. - - - - Gets the skip reason. - - - - - Acts as an and adapts the callback messages - into calls to an instance of . - - - - - Represents a logger used by and . - - - - - Called when the assembly has finished running. - - The assembly filename. - The total number of tests run. - The number of failed tests. - The number of skipped tests. - The time taken to run, in seconds. - - - - Called when the assembly has started running. - - The assembly filename. - The configuration filename, if given; null, otherwise. - The version of xunit.dll. - - - - Called when a class failure is encountered (i.e., when a fixture from - IUseFixture throws an exception during construction or . - - The full type name of the class. - The full type name of the exception. - The exception message. - The exception stack trace. - - - - - Called when an exception is thrown (i.e., a catastrophic failure of the testing system). - - The assembly filename. - The exception that was thrown. - - - - Called when a test fails. - - The description name of the test. - The full type name of the test class. - The name of the method. - The time spent running the test, in seconds. - The output of the test during its run. - The full type name of the exception. - The exception message. - The exception stack trace. - - - - Called when a test has finished running, regardless of what the result was. - - The description name of the test. - The full type name of the test class. - The name of the method. - Return true to continue running tests; return false to stop the test run. - - - - Called when a test has passed. - - The description name of the test. - The full type name of the test class. - The name of the method. - The time spent running the test, in seconds. - The output of the test during its run. - - - - Called when a test was finished. - - The description name of the test. - The full type name of the test class. - The name of the method. - The skip reason. - - - - Called when a test has started running. - - The description name of the test. - The full type name of the test class. - The name of the method. - Return true to continue running tests; return false to stop the test run. - - - - Initializes a new instance of the class. - - The test class. - The run status information callback. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Represents a passed test run in the object model. - - - - - Initializes a new instance of the class. - - The duration the test took to run. - The display name of the test result. - The output that was captured during the test run. - - - - Gets the output that was captured during the test run. - - - - - Indicates the composite test method status - - - - - The method has not been run - - - - - All test results for the last run passed - - - - - At least one test result for the last run failed - - - - - At least one test result for the last run was skipped, and none failed - - - - - Represents a set of filters for an . - - - - - Initializes a new instance of the class. - - - - - Filters the given method using the defined filter values. - - The methods to filter. - Returns true if the method passed the filter; return false otherwise. - - - - Gets the set of trait filters for tests to exclude. - - - - - Gets the set of trait filters for tests to include. - - - - - Represents an xUnit Test Project file (.xunit file) - - - - - Initializes a new instance of the class. - - - - - Adds an assembly to the project - - The assembly to be added - - - - Loads an xUnit.net Test Project file from disk. - - The test project filename - - - - Removes assembly from the assembly list - - The assembly to be removed - - - - Saves the xUnit.net Test Project file to disk using the project's filename. - - - - - Saves the xUnit.net Test Project file to disk using the provided filename. - The projects filename is updated to match this new name. - - The test project filename - - - - Gets or sets the assemblies in the project. - - - - - Gets or set the filename of the project. - - - - - Gets the filters applied to this project. - - - - - Gets or sets a flag which indicates if this project has been modified since - the last time it was loaded or saved. - - - - - Represents an assembly in an . - - - - - Initializes a new instance of the class. - - - - - Gets or sets the assembly filename. - - - - - Gets or sets the config filename. - - - - - Gets or sets a value indicating whether to shadow copy the assembly - when running the tests. - - - The xUnit.net GUI runner does not support this field. - - - - - Gets or sets the output filenames. The dictionary key is the type - of the file to be output; the dictionary value is the filename to - write the output to. - - - The xUnit.net GUI runner does not support this field. The MSBuild - runner only supports output of type 'xml', 'html', and 'nunit'. - - - - - Interface which represents a high level test runner. - - - - - Executes the tests in the assembly. - - Returns true if there were no failures; return false otherwise. - - - - Executes the tests in the assembly, and then executes the transforms with the - resulting assembly XML. - - The transforms to execute. - Returns true if there were no failures; return false otherwise. - - - - Runs the class. - - The type. - - - - - Runs a single test in a test class. - - The full name of the class. - The name of the method. - - - - Runs the list of tests in a test class. - - The full name of the class. - The names of the methods to run. - - - - Represents a single test assembly with test classes. - - - - - Initializes a new instance of the class. - - The executor wrapper. - The test classes. - - - - - - - Enumerates the test classes in the assembly. - - - - - - - - - - - Runs the specified test methods. - - The test methods to run. - The run status information callback. - Returns the result as XML. - - - - Gets the assembly filename. - - - - - Gets the config filename. - - - - - Gets the executor wrapper. - - - - - Gets the version of xunit.dll that the tests are linked against. - - - - - Represents a single class with test methods. - - - - - Initializes a new instance of the class. - - The namespace-qualified type name that - this class represents. - The test methods inside this test class. - - - - - - - - - - Runs the specified test methods. - - The test methods to run. - The run status information callback. - Returns the result as XML. - - - - Runs the specified tests in the given type, calling the callback as appropriate. - This override point exists primarily for unit testing purposes. - - The test methods to run - The run status information callback. - - - - Gets the test assembly that this class belongs to. - - - - - Gets the namespace-qualified type name of this class. - - - - - Represents a single test method. - - - - - Initializes a new instance of the class. - - The method name. - The method's display name. - The method's traits. - - - - Gets the method's display name. - - - - - Gets the method's name. - - - - - Gets the run results for the last run. - - - - - Gets the composite run status for all the results of the last run. - - - - - Gets the test class this test method belongs to. - - - - - Gets the method's traits. - - - - - The result of a test run via . - - - - - All tests passed, with no class-level failures - - - - - At least one test failed, or there was a class-level failure - - - - - There were no tests to run - - - - - Represents a transformation of the resulting assembly XML into some output format. - - - - - Transforms the given assembly XML into the destination format. - - The assembly XML. - - - - Gets the output filename, if known; returns null if the output isn't done to file. - - - - - Runs tests in an assembly, and transforms the XML results into calls to - the provided . - - - - - Initializes a new instance of the class. - - The executor wrapper. - The logger. - - - - - - - - - - - - - - - - - - - An implementation of which writes the - XML to a file without any transformation applied. - - - - - Initializes a new instance of the class. - - The output filename. - - - - - - - - - - An implementation of which writes the - XML to a file after applying the XSL stylesheet in the given stream. - - - - - Initializes a new instance of the class. - - The XSL filename. - The output filename. - - - - Initializes a new instance of the class. - - The stream with the XSL stylesheet. - The output filename. - - - - - - - - - - Gets or sets the XSL filename. - - - - - Gets or sets the XSL stream. - - - - - A dictionary which contains multiple unique values for each key. - - The type of the key. - The type of the value. - - - - Adds the value for the given key. If the key does not exist in the - dictionary yet, it will add it. - - The key. - The value. - - - - Removes all keys and values from the dictionary. - - - - - Determines whether the dictionary contains to specified key and value. - - The key. - The value. - - - - Calls the delegate once for each key/value pair in the dictionary. - - - - - Removes the given key and all of its values. - - - - - Removes the given value from the given key. If this was the - last value for the key, then the key is removed as well. - - The key. - The value. - - - - Gets the values for the given key. - - - - - Gets the count of the keys in the dictionary. - - - - - Gets the keys. - - - - - - - - Responsible for building instances. Uses an instance - of to interrogate the list of available tests - and create the entire object model tree. - - - - - Creates a which is a complete object model over - the tests inside of instance of . - - The executor wrapper - The fully populated object model - - - - Parses the XML nodes from the version resilient runner facility and converts - them into calls against the provided . - - - - - Logs a result XML node. Maybe be any kind of XML node. - - The node to be logged. - The logger. - Returns true if the user wishes to continue running tests; returns false otherwise. - - - - Logs the assembly node by calling . - - The assembly node. - The logger. - - - - Logs the class node by calling (if the class failed). - The exception type was added in xUnit.net 1.1, so when the test assembly is linked against - xUnit.net versions prior to 1.1, the exception type will be null. - - The class node. - The logger. - Returns true if the user wishes to continue running tests; returns false otherwise. - - - - Logs the start node by calling . The start node was added - in xUnit.net 1.1, so it will only be present when the test assembly is linked against xunit.dll - version 1.1 or later. - - The start node. - The logger. - Returns true if the user wishes to continue running tests; returns false otherwise. - - - - Logs the test node by calling . It will also call - , , or - as appropriate. - - The test node. - The logger. - Returns true if the user wishes to continue running tests; returns false otherwise. - - - diff --git a/test-harness/packagesNonNuget/xunit.runner/xunit.xml b/test-harness/packagesNonNuget/xunit.runner/xunit.xml deleted file mode 100644 index d8b316f50..000000000 --- a/test-harness/packagesNonNuget/xunit.runner/xunit.xml +++ /dev/null @@ -1,2611 +0,0 @@ - - - - xunit - - - - - Contains various static methods that are used to verify that conditions are met during the - process of running tests. - - - - - Initializes a new instance of the class. - - - - - Verifies that a collection contains a given object. - - The type of the object to be verified - The object expected to be in the collection - The collection to be inspected - Thrown when the object is not present in the collection - - - - Verifies that a collection contains a given object, using an equality comparer. - - The type of the object to be verified - The object expected to be in the collection - The collection to be inspected - The comparer used to equate objects in the collection with the expected object - Thrown when the object is not present in the collection - - - - Verifies that a string contains a given sub-string, using the current culture. - - The sub-string expected to be in the string - The string to be inspected - Thrown when the sub-string is not present inside the string - - - - Verifies that a string contains a given sub-string, using the given comparison type. - - The sub-string expected to be in the string - The string to be inspected - The type of string comparison to perform - Thrown when the sub-string is not present inside the string - - - - Verifies that a collection does not contain a given object. - - The type of the object to be compared - The object that is expected not to be in the collection - The collection to be inspected - Thrown when the object is present inside the container - - - - Verifies that a collection does not contain a given object, using an equality comparer. - - The type of the object to be compared - The object that is expected not to be in the collection - The collection to be inspected - The comparer used to equate objects in the collection with the expected object - Thrown when the object is present inside the container - - - - Verifies that a string does not contain a given sub-string, using the current culture. - - The sub-string which is expected not to be in the string - The string to be inspected - Thrown when the sub-string is present inside the string - - - - Verifies that a string does not contain a given sub-string, using the current culture. - - The sub-string which is expected not to be in the string - The string to be inspected - The type of string comparison to perform - Thrown when the sub-string is present inside the given string - - - - Verifies that a block of code does not throw any exceptions. - - A delegate to the code to be tested - - - - Verifies that a collection is empty. - - The collection to be inspected - Thrown when the collection is null - Thrown when the collection is not empty - - - - Verifies that two objects are equal, using a default comparer. - - The type of the objects to be compared - The expected value - The value to be compared against - Thrown when the objects are not equal - - - - Verifies that two objects are equal, using a custom equatable comparer. - - The type of the objects to be compared - The expected value - The value to be compared against - The comparer used to compare the two objects - Thrown when the objects are not equal - - - - Verifies that two values are equal, within the number of decimal - places given by . - - The expected value - The value to be compared against - The number of decimal places (valid values: 0-15) - Thrown when the values are not equal - - - - Verifies that two values are equal, within the number of decimal - places given by . - - The expected value - The value to be compared against - The number of decimal places (valid values: 0-15) - Thrown when the values are not equal - - - - Verifies that two sequences are equivalent, using a default comparer. - - The type of the objects to be compared - The expected value - The value to be compared against - Thrown when the objects are not equal - - - - Verifies that two sequences are equivalent, using a custom equatable comparer. - - The type of the objects to be compared - The expected value - The value to be compared against - The comparer used to compare the two objects - Thrown when the objects are not equal - - - Do not call this method. - - - - Verifies that the condition is false. - - The condition to be tested - Thrown if the condition is not false - - - - Verifies that the condition is false. - - The condition to be tested - The message to show when the condition is not false - Thrown if the condition is not false - - - - Verifies that a value is within a given range. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - Thrown when the value is not in the given range - - - - Verifies that a value is within a given range, using a comparer. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - The comparer used to evaluate the value's range - Thrown when the value is not in the given range - - - - Verifies that an object is of the given type or a derived type. - - The type the object should be - The object to be evaluated - The object, casted to type T when successful - Thrown when the object is not the given type - - - - Verifies that an object is of the given type or a derived type. - - The type the object should be - The object to be evaluated - Thrown when the object is not the given type - - - - Verifies that an object is not exactly the given type. - - The type the object should not be - The object to be evaluated - Thrown when the object is the given type - - - - Verifies that an object is not exactly the given type. - - The type the object should not be - The object to be evaluated - Thrown when the object is the given type - - - - Verifies that an object is exactly the given type (and not a derived type). - - The type the object should be - The object to be evaluated - The object, casted to type T when successful - Thrown when the object is not the given type - - - - Verifies that an object is exactly the given type (and not a derived type). - - The type the object should be - The object to be evaluated - Thrown when the object is not the given type - - - - Verifies that a collection is not empty. - - The collection to be inspected - Thrown when a null collection is passed - Thrown when the collection is empty - - - - Verifies that two objects are not equal, using a default comparer. - - The type of the objects to be compared - The expected object - The actual object - Thrown when the objects are equal - - - - Verifies that two objects are not equal, using a custom equality comparer. - - The type of the objects to be compared - The expected object - The actual object - The comparer used to examine the objects - Thrown when the objects are equal - - - - Verifies that two sequences are not equivalent, using a default comparer. - - The type of the objects to be compared - The expected object - The actual object - Thrown when the objects are equal - - - - Verifies that two sequences are not equivalent, using a custom equality comparer. - - The type of the objects to be compared - The expected object - The actual object - The comparer used to compare the two objects - Thrown when the objects are equal - - - - Verifies that a value is not within a given range, using the default comparer. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - Thrown when the value is in the given range - - - - Verifies that a value is not within a given range, using a comparer. - - The type of the value to be compared - The actual value to be evaluated - The (inclusive) low value of the range - The (inclusive) high value of the range - The comparer used to evaluate the value's range - Thrown when the value is in the given range - - - - Verifies that an object reference is not null. - - The object to be validated - Thrown when the object is not null - - - - Verifies that two objects are not the same instance. - - The expected object instance - The actual object instance - Thrown when the objects are the same instance - - - - Verifies that an object reference is null. - - The object to be inspected - Thrown when the object reference is not null - - - - Verifies that the provided object raised INotifyPropertyChanged.PropertyChanged - as a result of executing the given test code. - - The object which should raise the notification - The property name for which the notification should be raised - The test code which should cause the notification to be raised - Thrown when the notification is not raised - - - - Verifies that two objects are the same instance. - - The expected object instance - The actual object instance - Thrown when the objects are not the same instance - - - - Verifies that the given collection contains only a single - element of the given type. - - The collection. - The single item in the collection. - Thrown when the collection does not contain - exactly one element. - - - - Verifies that the given collection contains only a single - element of the given value. The collection may or may not - contain other values. - - The collection. - The value to find in the collection. - The single item in the collection. - Thrown when the collection does not contain - exactly one element. - - - - Verifies that the given collection contains only a single - element of the given type. - - The collection type. - The collection. - The single item in the collection. - Thrown when the collection does not contain - exactly one element. - - - - Verifies that the given collection contains only a single - element of the given type which matches the given predicate. The - collection may or may not contain other values which do not - match the given predicate. - - The collection type. - The collection. - The item matching predicate. - The single item in the filtered collection. - Thrown when the filtered collection does - not contain exactly one element. - - - - Verifies that the exact exception is thrown (and not a derived exception type). - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that the exact exception is thrown (and not a derived exception type). - Generally used to test property accessors. - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that the exact exception is thrown (and not a derived exception type). - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that the exact exception is thrown (and not a derived exception type). - Generally used to test property accessors. - - The type of the exception expected to be thrown - A delegate to the code to be tested - The exception that was thrown, when successful - Thrown when an exception was not thrown, or when an exception of the incorrect type is thrown - - - - Verifies that an expression is true. - - The condition to be inspected - Thrown when the condition is false - - - - Verifies that an expression is true. - - The condition to be inspected - The message to be shown when the condition is false - Thrown when the condition is false - - - - Used by the PropertyChanged. - - - - - Used by the Throws and DoesNotThrow methods. - - - - - Used by the Throws and DoesNotThrow methods. - - - - - This command sets up the necessary trace listeners and standard - output/error listeners to capture Assert/Debug.Trace failures, - output to stdout/stderr, and Assert/Debug.Write text. It also - captures any exceptions that are thrown and packages them as - FailedResults, including the possibility that the configuration - file is messed up (which is exposed when we attempt to manipulate - the trace listener list). - - - - - Base class used by commands which delegate to inner commands. - - - - - Interface which represents the ability to invoke of a test method. - - - - - Executes the test method. - - The instance of the test class - Returns information about the test run - - - - Creates the start XML to be sent to the callback when the test is about to start - running. - - Return the of the start node, or null if the test - is known that it will not be running. - - - - Gets the display name of the test method. - - - - - Determines if the test runner infrastructure should create a new instance of the - test class before running the test. - - - - - Determines if the test should be limited to running a specific amount of time - before automatically failing. - - The timeout value, in milliseconds; if zero, the test will not have - a timeout. - - - - Creates a new instance of the class. - - The inner command to delegate to. - - - - - - - - - - - - - - - - - - - - - - Initializes a new instance of the - class. - - The command that will be wrapped. - The test method. - - - - - - - Represents an implementation of to be used with - tests which are decorated with the . - - - - - Represents an xUnit.net test command. - - - - - The method under test. - - - - - Initializes a new instance of the class. - - The method under test. - The display name of the test. - The timeout, in milliseconds. - - - - - - - - - - - - - Gets the name of the method under test. - - - - - - - - - - - Gets the name of the type under test. - - - - - Initializes a new instance of the class. - - The test method. - - - - - - - Base class for exceptions that have actual and expected values - - - - - The base assert exception class - - - - - Initializes a new instance of the class. - - - - - Initializes a new instance of the class. - - The user message to be displayed - - - - Initializes a new instance of the class. - - The user message to be displayed - The inner exception - - - - Initializes a new instance of the class. - - The user message to be displayed - The stack trace to be displayed - - - - - - - Determines whether to exclude a line from the stack frame. By default, this method - removes all stack frames from methods beginning with Xunit.Assert or Xunit.Sdk. - - The stack frame to be filtered. - Return true to exclude the line from the stack frame; false, otherwise. - - - - Filters the stack trace to remove all lines that occur within the testing framework. - - The original stack trace - The filtered stack trace - - - - - - - Gets a string representation of the frames on the call stack at the time the current exception was thrown. - - A string that describes the contents of the call stack, with the most recent method call appearing first. - - - - Gets the user message - - - - - Creates a new instance of the class. - - The expected value - The actual value - The user message to be shown - - - - Creates a new instance of the class. - - The expected value - The actual value - The user message to be shown - Set to true to skip the check for difference position - - - - - - - - - - Gets the actual value. - - - - - Gets the expected value. - - - - - Gets a message that describes the current exception. Includes the expected and actual values. - - The error message that explains the reason for the exception, or an empty string(""). - 1 - - - - Exception thrown when a collection unexpectedly does not contain the expected value. - - - - - Creates a new instance of the class. - - The expected object value - - - - Creates a new instance of the class. - - The expected object value - The actual value - - - - - - - Exception to be thrown from when the number of - parameter values does not the test method signature. - - - - - - - - - - - Exception thrown when code unexpectedly fails change a property. - - - - - Creates a new instance of the class. Call this constructor - when no exception was thrown. - - The name of the property that was expected to be changed. - - - - - - - Exception thrown when the collection did not contain exactly one element. - - - - - Initializes a new instance of the class. - - The numbers of items in the collection. - - - - Initializes a new instance of the class. - - The numbers of items in the collection. - The object expected to be in the collection. - - - - - - - Internal class used for version-resilient test runners. DO NOT CALL DIRECTLY. - Version-resilient runners should link against xunit.runner.utility.dll and use - ExecutorWrapper instead. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Exception thrown when the value is unexpectedly not of the given type or a derived type. - - - - - Creates a new instance of the class. - - The expected type - The actual object value - - - - - - - Allows the user to record actions for a test. - - - - - Records any exception which is thrown by the given code. - - The code which may thrown an exception. - Returns the exception that was thrown by the code; null, otherwise. - - - - Records any exception which is thrown by the given code that has - a return value. Generally used for testing property accessors. - - The code which may thrown an exception. - Returns the exception that was thrown by the code; null, otherwise. - - - - Exception that is thrown when one or more exceptions are thrown from - the After method of a . - - - - - Initializes a new instance of the class. - - The exceptions. - - - - Initializes a new instance of the class. - - The exceptions. - - - - - - - - - - Gets the list of exceptions thrown in the After method. - - - - - Gets a message that describes the current exception. - - - - - Gets a string representation of the frames on the call stack at the time the current exception was thrown. - - - - - Implementation of which executes the - instances attached to a test method. - - - - - Initializes a new instance of the class. - - The inner command. - The method. - - - - Executes the test method. - - The instance of the test class - Returns information about the test run - - - - This class supports the xUnit.net infrastructure and is not intended to be used - directly from your code. - - - - - This API supports the xUnit.net infrastructure and is not intended to be used - directly from your code. - - - - - This API supports the xUnit.net infrastructure and is not intended to be used - directly from your code. - - - - - This API supports the xUnit.net infrastructure and is not intended to be used - directly from your code. - - - - - Guard class, used for guard clauses and argument validation - - - - - - - - - - - - - - Base class which contains XML manipulation helper methods - - - - - Interface that represents a single test result. - - - - - Converts the test result into XML that is consumed by the test runners. - - The parent node. - The newly created XML node. - - - - The amount of time spent in execution - - - - - Adds the test execution time to the XML node. - - The XML node. - - - - - - - - - - Utility methods for dealing with exceptions. - - - - - Gets the message for the exception, including any inner exception messages. - - The exception - The formatted message - - - - Gets the stack trace for the exception, including any inner exceptions. - - The exception - The formatted stack trace - - - - Rethrows an exception object without losing the existing stack trace information - - The exception to re-throw. - - For more information on this technique, see - http://www.dotnetjunkies.com/WebLog/chris.taylor/archive/2004/03/03/8353.aspx - - - - - A dictionary which contains multiple unique values for each key. - - The type of the key. - The type of the value. - - - - Adds the value for the given key. If the key does not exist in the - dictionary yet, it will add it. - - The key. - The value. - - - - Removes all keys and values from the dictionary. - - - - - Determines whether the dictionary contains to specified key and value. - - The key. - The value. - - - - Calls the delegate once for each key/value pair in the dictionary. - - - - - Removes the given key and all of its values. - - - - - Removes the given value from the given key. If this was the - last value for the key, then the key is removed as well. - - The key. - The value. - - - - Gets the values for the given key. - - - - - Gets the count of the keys in the dictionary. - - - - - Gets the keys. - - - - - - - - XML utility methods - - - - - Adds an attribute to an XML node. - - The XML node. - The attribute name. - The attribute value. - - - - Adds a child element to an XML node. - - The parent XML node. - The child element name. - The new child XML element. - - - - Sets the inner text of the XML node, properly escaping it as necessary. - - The element whose inner text will be set. - The inner text to be escaped and then set. - - - - Exception that is thrown when a call to Debug.Assert() fails. - - - - - Creates a new instance of the class. - - The original assert message - - - - Creates a new instance of the class. - - The original assert message - The original assert detailed message - - - - - - - - - - Gets the original assert detailed message. - - - - - Gets the original assert message. - - - - - Gets a message that describes the current exception. - - - - - Exception thrown when a collection unexpectedly contains the expected value. - - - - - Creates a new instance of the class. - - The expected object value - - - - - - - Exception thrown when code unexpectedly throws an exception. - - - - - Creates a new instance of the class. - - Actual exception - - - - THIS CONSTRUCTOR IS FOR UNIT TESTING PURPOSES ONLY. - - - - - - - - - - - Gets a string representation of the frames on the call stack at the time the current exception was thrown. - - A string that describes the contents of the call stack, with the most recent method call appearing first. - - - - Exception thrown when a collection is unexpectedly not empty. - - - - - Creates a new instance of the class. - - - - - - - - Exception thrown when two values are unexpectedly not equal. - - - - - Creates a new instance of the class. - - The expected object value - The actual object value - - - - Creates a new instance of the class. - - The expected object value - The actual object value - Set to true to skip the check for difference position - - - - - - - Exception thrown when a value is unexpectedly true. - - - - - Creates a new instance of the class. - - The user message to be display, or null for the default message - - - - - - - Exception thrown when a value is unexpectedly not in the given range. - - - - - Creates a new instance of the class. - - The actual object value - The low value of the range - The high value of the range - - - - - - - - - - Gets the actual object value - - - - - Gets the high value of the range - - - - - Gets the low value of the range - - - - - Gets a message that describes the current exception. - - The error message that explains the reason for the exception, or an empty string(""). - - - - Exception thrown when the value is unexpectedly of the exact given type. - - - - - Creates a new instance of the class. - - The expected type - The actual object value - - - - - - - Exception thrown when the value is unexpectedly not of the exact given type. - - - - - Creates a new instance of the class. - - The expected type - The actual object value - - - - - - - Used to decorate xUnit.net test classes that utilize fixture classes. - An instance of the fixture data is initialized just before the first - test in the class is run, and if it implements IDisposable, is disposed - after the last test in the class is run. - - The type of the fixture - - - - Called on the test class just before each test method is run, - passing the fixture data so that it can be used for the test. - All test runs share the same instance of fixture data. - - The fixture data - - - - Exception thrown when a value is unexpectedly in the given range. - - - - - Creates a new instance of the class. - - The actual object value - The low value of the range - The high value of the range - - - - - - - - - - Gets the actual object value - - - - - Gets the high value of the range - - - - - Gets the low value of the range - - - - - Gets a message that describes the current exception. - - The error message that explains the reason for the exception, or an empty string(""). - - - - Base attribute which indicates a test method interception (allows code to be run before and - after the test is run). - - - - - This method is called after the test method is executed. - - The method under test - - - - This method is called before the test method is executed. - - The method under test - - - - - - - Exception thrown when a collection is unexpectedly empty. - - - - - Creates a new instance of the class. - - - - - - - - Exception thrown when two values are unexpectedly equal. - - - - - Creates a new instance of the class. - - - - - - - - Exception thrown when an object is unexpectedly null. - - - - - Creates a new instance of the class. - - - - - - - - Exception thrown when two values are unexpected the same instance. - - - - - Creates a new instance of the class. - - - - - - - - Exception thrown when an object reference is unexpectedly not null. - - - - - Creates a new instance of the class. - - - - - - - - - Command that automatically creates the instance of the test class - and disposes it (if it implements ). - - - - - Creates a new instance of the object. - - The command that is bring wrapped - The method under test - - - - Executes the test method. Creates a new instance of the class - under tests and passes it to the inner command. Also catches - any exceptions and converts them into s. - - The instance of the test class - Returns information about the test run - - - - Command used to wrap a which has associated - fixture data. - - - - - Creates a new instance of the class. - - The inner command - The fixtures to be set on the test class - - - - Sets the fixtures on the test class by calling SetFixture, then - calls the inner command. - - The instance of the test class - Returns information about the test run - - - - A timer class used to figure out how long tests take to run. On most .NET implementations - this will use the class because it's a high - resolution timer; however, on Silverlight/CoreCLR, it will use - (which will provide lower resolution results). - - - - - Creates a new instance of the class. - - - - - Starts timing. - - - - - Stops timing. - - - - - Gets how long the timer ran, in milliseconds. In order for this to be valid, - both and must have been called. - - - - - Attribute used to decorate a test method with arbitrary name/value pairs ("traits"). - - - - - Creates a new instance of the class. - - The trait name - The trait value - - - - Gets the trait name. - - - - - - - - Gets the trait value. - - - - - Runner that executes an synchronously. - - - - - Execute the . - - The test class command to execute - The methods to execute; if null or empty, all methods will be executed - The start run callback - The end run result callback - A with the results of the test run - - - - Factory for objects, based on the type under test. - - - - - Creates the test class command, which implements , for a given type. - - The type under test - The test class command, if the class is a test class; null, otherwise - - - - Creates the test class command, which implements , for a given type. - - The type under test - The test class command, if the class is a test class; null, otherwise - - - - Represents an xUnit.net test class - - - - - Interface which describes the ability to executes all the tests in a test class. - - - - - Allows the test class command to choose the next test to be run from the list of - tests that have not yet been run, thereby allowing it to choose the run order. - - The tests remaining to be run - The index of the test that should be run - - - - Execute actions to be run after all the test methods of this test class are run. - - Returns the thrown during execution, if any; null, otherwise - - - - Execute actions to be run before any of the test methods of this test class are run. - - Returns the thrown during execution, if any; null, otherwise - - - - Enumerates the test commands for a given test method in this test class. - - The method under test - The test commands for the given test method - - - - Enumerates the methods which are test methods in this test class. - - The test methods - - - - Determines if a given refers to a test method. - - The test method to validate - True if the method is a test method; false, otherwise - - - - Gets the object instance that is under test. May return null if you wish - the test framework to create a new object instance for each test method. - - - - - Gets or sets the type that is being tested - - - - - Creates a new instance of the class. - - - - - Creates a new instance of the class. - - The type under test - - - - Creates a new instance of the class. - - The type under test - - - - Chooses the next test to run, randomly, using the . - - The tests remaining to be run - The index of the test that should be run - - - - Execute actions to be run after all the test methods of this test class are run. - - Returns the thrown during execution, if any; null, otherwise - - - - Execute actions to be run before any of the test methods of this test class are run. - - Returns the thrown during execution, if any; null, otherwise - - - - Enumerates the test commands for a given test method in this test class. - - The method under test - The test commands for the given test method - - - - Enumerates the methods which are test methods in this test class. - - The test methods - - - - Determines if a given refers to a test method. - - The test method to validate - True if the method is a test method; false, otherwise - - - - Gets the object instance that is under test. May return null if you wish - the test framework to create a new object instance for each test method. - - - - - Gets or sets the randomizer used to determine the order in which tests are run. - - - - - Sets the type that is being tested - - - - - Implementation of that represents a skipped test. - - - - - Creates a new instance of the class. - - The method that is being skipped - The display name for the test. If null, the fully qualified - type name is used. - The reason the test was skipped. - - - - - - - - - - Gets the skip reason. - - - - - - - - Factory for creating objects. - - - - - Make instances of objects for the given class and method. - - The class command - The method under test - The set of objects - - - - A command wrapper which times the running of a command. - - - - - Creates a new instance of the class. - - The command that will be timed. - - - - Executes the inner test method, gathering the amount of time it takes to run. - - Returns information about the test run - - - - Wraps a command which should fail if it runs longer than the given timeout value. - - - - - Creates a new instance of the class. - - The command to be run - The timout, in milliseconds - The method under test - - - - Executes the test method, failing if it takes too long. - - Returns information about the test run - - - - - - - Attributes used to decorate a test fixture that is run with an alternate test runner. - The test runner must implement the interface. - - - - - Creates a new instance of the class. - - The class which implements ITestClassCommand and acts as the runner - for the test fixture. - - - - Gets the test class command. - - - - - Exception thrown when two object references are unexpectedly not the same instance. - - - - - Creates a new instance of the class. - - The expected object reference - The actual object reference - - - - - - - Contains the test results from an assembly. - - - - - Contains multiple test results, representing them as a composite test result. - - - - - Adds a test result to the composite test result list. - - - - - - Gets the test results. - - - - - Creates a new instance of the class. - - The filename of the assembly - - - - Creates a new instance of the class. - - The filename of the assembly - The configuration filename - - - - Converts the test result into XML that is consumed by the test runners. - - The parent node. - The newly created XML node. - - - - Gets the fully qualified filename of the configuration file. - - - - - Gets the directory where the assembly resides. - - - - - Gets the number of failed results. - - - - - Gets the fully qualified filename of the assembly. - - - - - Gets the number of passed results. - - - - - Gets the number of skipped results. - - - - - Contains the test results from a test class. - - - - - Creates a new instance of the class. - - The type under test - - - - Creates a new instance of the class. - - The simple name of the type under test - The fully qualified name of the type under test - The namespace of the type under test - - - - Sets the exception thrown by the test fixture. - - The thrown exception - - - - Converts the test result into XML that is consumed by the test runners. - - The parent node. - The newly created XML node. - - - - Gets the fully qualified test fixture exception type, when an exception has occurred. - - - - - Gets the number of tests which failed. - - - - - Gets the fully qualified name of the type under test. - - - - - Gets the test fixture exception message, when an exception has occurred. - - - - - Gets the simple name of the type under test. - - - - - Gets the namespace of the type under test. - - - - - Gets the number of tests which passed. - - - - - Gets the number of tests which were skipped. - - - - - Gets the test fixture exception stack trace, when an exception has occurred. - - - - - Represents a failed test result. - - - - - Represents the results from running a test method - - - - - Initializes a new instance of the class. The traits for - the test method are discovered using reflection. - - The method under test. - The display name for the test. If null, the fully qualified - type name is used. - - - - Initializes a new instance of the class. - - The name of the method under test. - The type of the method under test. - The display name for the test. If null, the fully qualified - type name is used. - The traits. - - - - Converts the test result into XML that is consumed by the test runners. - - The parent node. - The newly created XML node. - - - - Gets or sets the display name of the method under test. This is the value that's shown - during failures and in the resulting output XML. - - - - - Gets the name of the method under test. - - - - - Gets or sets the standard output/standard error from the test that was captured - while the test was running. - - - - - Gets the traits attached to the test method. - - - - - Gets the name of the type under test. - - - - - Creates a new instance of the class. - - The method under test - The exception throw by the test - The display name for the test. If null, the fully qualified - type name is used. - - - - Creates a new instance of the class. - - The name of the method under test - The name of the type under test - The display name of the test - The custom properties attached to the test method - The full type name of the exception throw - The exception message - The exception stack trace - - - - Converts the test result into XML that is consumed by the test runners. - - The parent node. - The newly created XML node. - - - - Gets the exception type thrown by the test method. - - - - - Gets the exception message thrown by the test method. - - - - - Gets the stack trace of the exception thrown by the test method. - - - - - Represents a passing test result. - - - - - Create a new instance of the class. - - The method under test - The display name for the test. If null, the fully qualified - type name is used. - - - - Create a new instance of the class. - - The name of the method under test - The name of the type under test - The display name for the test. If null, the fully qualified - type name is used. - The custom properties attached to the test method - - - - Converts the test result into XML that is consumed by the test runners. - - The parent node. - The newly created XML node. - - - - Represents a skipped test result. - - - - - Creates a new instance of the class. Uses reflection to discover - the skip reason. - - The method under test - The display name for the test. If null, the fully qualified - type name is used. - The reason the test was skipped. - - - - Creates a new instance of the class. - - The name of the method under test - The name of the type under test - The display name for the test. If null, the fully qualified - type name is used. - The traits attached to the method under test - The skip reason - - - - Converts the test result into XML that is consumed by the test runners. - - The parent node. - The newly created XML node. - - - - Gets the skip reason. - - - - - Represents information about an attribute. - - - - - Gets the instance of the attribute, if available. - - The type of the attribute - The instance of the attribute, if available. - - - - Gets an initialized property value of the attribute. - - The type of the property - The name of the property - The property value - - - - Represents information about a method. - - - - - Creates an instance of the type where this test method was found. If using - reflection, this should be the ReflectedType. - - A new instance of the type. - - - - Gets all the custom attributes for the method that are of the given type. - - The type of the attribute - The matching attributes that decorate the method - - - - Determines if the method has at least one instance of the given attribute type. - - The type of the attribute - True if the method has at least one instance of the given attribute type; false, otherwise - - - - Invokes the test on the given class, with the given parameters. - - The instance of the test class (may be null if - the test method is static). - The parameters to be passed to the test method. - - - - Gets a value which represents the class that this method was - reflected from (i.e., equivalent to MethodInfo.ReflectedType) - - - - - Gets a value indicating whether the method is abstract. - - - - - Gets a value indicating whether the method is static. - - - - - Gets the underlying for the method, if available. - - - - - Gets the name of the method. - - - - - Gets the fully qualified type name of the return type. - - - - - Gets the fully qualified type name of the type that this method belongs to. If - using reflection, this should be the ReflectedType. - - - - - Represents information about a type. - - - - - Gets all the custom attributes for the type that are of the given attribute type. - - The type of the attribute - The matching attributes that decorate the type - - - - Gets a test method by name. - - The name of the method - The method, if it exists; null, otherwise. - - - - Gets all the methods - - - - - - Determines if the type has at least one instance of the given attribute type. - - The type of the attribute - True if the type has at least one instance of the given attribute type; false, otherwise - - - - Determines if the type implements the given interface. - - The type of the interface - True if the type implements the given interface; false, otherwise - - - - Gets a value indicating whether the type is abstract. - - - - - Gets a value indicating whether the type is sealed. - - - - - Gets the underlying object, if available. - - - - - Utility class which inspects methods for test information - - - - - Gets the display name. - - The method to be inspected - The display name - - - - Gets the skip reason from a test method. - - The method to be inspected - The skip reason - - - - Gets the test commands for a test method. - - The method to be inspected - The objects for the test method - - - - Gets the timeout value for a test method. - - The method to be inspected - The timeout, in milliseconds - - - - Gets the traits on a test method. - - The method to be inspected - A dictionary of the traits - - - - Determines whether a test method has a timeout. - - The method to be inspected - True if the method has a timeout; false, otherwise - - - - Determines whether a test method has traits. - - The method to be inspected - True if the method has traits; false, otherwise - - - - Determines whether a test method should be skipped. - - The method to be inspected - True if the method should be skipped; false, otherwise - - - - Determines whether a method is a test method. A test method must be decorated - with the (or derived class) and must not be abstract. - - The method to be inspected - True if the method is a test method; false, otherwise - - - - Wrapper to implement and using reflection. - - - - - Converts an into an using reflection. - - - - - - - Converts a into an using reflection. - - The method to wrap - The wrapper - - - - Converts a into an using reflection. - - The type to wrap - The wrapper - - - - Utility class which inspects types for test information - - - - - Determines if a type contains any test methods - - The type to be inspected - True if the class contains any test methods; false, otherwise - - - - Retrieves the type to run the test class with from the , if present. - - The type to be inspected - The type of the test class runner, if present; null, otherwise - - - - Retrieves a list of the test methods from the test class. - - The type to be inspected - The test methods - - - - Determines if the test class has a applied to it. - - The type to be inspected - True if the test class has a run with attribute; false, otherwise - - - - Determines if the type implements . - - The type to be inspected - True if the type implements ; false, otherwise - - - - Determines whether the specified type is abstract. - - The type. - - true if the specified type is abstract; otherwise, false. - - - - - Determines whether the specified type is static. - - The type. - - true if the specified type is static; otherwise, false. - - - - - Determines if a class is a test class. - - The type to be inspected - True if the type is a test class; false, otherwise - - - - Attribute that is applied to a method to indicate that it is a fact that should be run - by the test runner. It can also be extended to support a customized definition of a - test method. - - - - - Creates instances of which represent individual intended - invocations of the test method. - - The method under test - An enumerator through the desired test method invocations - - - - Enumerates the test commands represented by this test method. Derived classes should - override this method to return instances of , one per execution - of a test method. - - The test method - The test commands which will execute the test runs for the given method - - - - Gets the name of the test to be used when the test is skipped. Defaults to - null, which will cause the fully qualified test name to be used. - - - - - Obsolete. Please use the property instead. - - - - - Marks the test so that it will not be run, and gets or sets the skip reason - - - - - Marks the test as failing if it does not finish running within the given time - period, in milliseconds; set to 0 or less to indicate the method has no timeout - - - - - Exception thrown when code unexpectedly fails to throw an exception. - - - - - Creates a new instance of the class. Call this constructor - when no exception was thrown. - - The type of the exception that was expected - - - - Creates a new instance of the class. Call this constructor - when an exception of the wrong type was thrown. - - The type of the exception that was expected - The actual exception that was thrown - - - - - - - THIS CONSTRUCTOR IS FOR UNIT TESTING PURPOSES ONLY. - - - - - - - - Gets a string representation of the frames on the call stack at the time the current exception was thrown. - - A string that describes the contents of the call stack, with the most recent method call appearing first. - - - - Exception thrown when a test method exceeds the given timeout value - - - - - Creates a new instance of the class. - - The timeout value, in milliseconds - - - - - - - Exception thrown when a value is unexpectedly false. - - - - - Creates a new instance of the class. - - The user message to be displayed, or null for the default message - - - - - - diff --git a/test-harness/xunit/Addition.feature b/test-harness/xunit/Addition.feature deleted file mode 100644 index 238e261e9..000000000 --- a/test-harness/xunit/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/xunit/Addition.feature.cs b/test-harness/xunit/Addition.feature.cs deleted file mode 100644 index 8e70a5ed2..000000000 --- a/test-harness/xunit/Addition.feature.cs +++ /dev/null @@ -1,223 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class AdditionFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Addition.feature" -#line hidden - - public AdditionFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Addition", "In order to avoid silly mistakes\r\nAs a math idiot\r\nI want to be told the sum of t" + - "wo numbers", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 6 -#line 7 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void SetFixture(AdditionFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Adding several numbers")] - [Xunit.Extensions.InlineDataAttribute("60", "70", "130", "260", new string[0])] - [Xunit.Extensions.InlineDataAttribute("40", "50", "90", "180", new string[0])] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - string[] @__tags = new string[] { - "tag2"}; - if ((exampleTags != null)) - { - @__tags = System.Linq.Enumerable.ToArray(System.Linq.Enumerable.Concat(@__tags, exampleTags)); - } - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", @__tags); -#line 10 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 11 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 12 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 13 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 14 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 15 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Add two numbers")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", new string[] { - "tag1"}); -#line 23 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 24 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 25 - testRunner.And("I have entered 2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 26 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 27 - testRunner.Then("the result should be 3 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Fail to add two numbers")] - public virtual void FailToAddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Fail to add two numbers", new string[] { - "tag1"}); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 31 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 32 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 33 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 34 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute(Skip="Ignored")] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Ignored adding two numbers")] - public virtual void IgnoredAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Ignored adding two numbers", new string[] { - "ignore"}); -#line 37 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 38 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 39 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 40 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 41 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Not automated adding two numbers")] - public virtual void NotAutomatedAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated adding two numbers", ((string[])(null))); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 44 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 45 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 46 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - AdditionFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - AdditionFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/App.config b/test-harness/xunit/App.config deleted file mode 100644 index 555737021..000000000 --- a/test-harness/xunit/App.config +++ /dev/null @@ -1,13 +0,0 @@ - - - -
          - - - - - - - - - \ No newline at end of file diff --git a/test-harness/xunit/FailingBackground.feature b/test-harness/xunit/FailingBackground.feature deleted file mode 100644 index 83a70483a..000000000 --- a/test-harness/xunit/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/xunit/FailingBackground.feature.cs b/test-harness/xunit/FailingBackground.feature.cs deleted file mode 100644 index 0d8fd5a39..000000000 --- a/test-harness/xunit/FailingBackground.feature.cs +++ /dev/null @@ -1,151 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class FailingBackgroundFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "FailingBackground.feature" -#line hidden - - public FailingBackgroundFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing Background", "This feature has a failing background.", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the background step fails", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 6 - testRunner.And("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line hidden - } - - public virtual void SetFixture(FailingBackgroundFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing Background")] - [Xunit.TraitAttribute("Description", "Add two numbers")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", ((string[])(null))); -#line 8 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 9 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 10 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 11 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 12 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing Background")] - [Xunit.TraitAttribute("Description", "Adding several numbers")] - [Xunit.Extensions.InlineDataAttribute("60", "70", "130", "260", new string[0])] - [Xunit.Extensions.InlineDataAttribute("40", "50", "90", "180", new string[0])] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 16 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 17 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 18 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - FailingBackgroundFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - FailingBackgroundFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/Minimal Features/Failing.feature b/test-harness/xunit/Minimal Features/Failing.feature deleted file mode 100644 index d7c5b7f53..000000000 --- a/test-harness/xunit/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step \ No newline at end of file diff --git a/test-harness/xunit/Minimal Features/Failing.feature.cs b/test-harness/xunit/Minimal Features/Failing.feature.cs deleted file mode 100644 index 58e0b11a3..000000000 --- a/test-harness/xunit/Minimal Features/Failing.feature.cs +++ /dev/null @@ -1,135 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class FailingFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Failing.feature" -#line hidden - - public FailingFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(FailingFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing")] - [Xunit.TraitAttribute("Description", "Failing Feature Passing Scenario")] - public virtual void FailingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing")] - [Xunit.TraitAttribute("Description", "Failing Feature Inconclusive Scenario")] - public virtual void FailingFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing")] - [Xunit.TraitAttribute("Description", "Failing Feature Failing Scenario")] - public virtual void FailingFeatureFailingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Failing Scenario", ((string[])(null))); -#line 9 -this.ScenarioSetup(scenarioInfo); -#line 10 - testRunner.Then("failing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - FailingFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - FailingFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/Minimal Features/Inconclusive.feature b/test-harness/xunit/Minimal Features/Inconclusive.feature deleted file mode 100644 index 7ce63f2d5..000000000 --- a/test-harness/xunit/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step \ No newline at end of file diff --git a/test-harness/xunit/Minimal Features/Inconclusive.feature.cs b/test-harness/xunit/Minimal Features/Inconclusive.feature.cs deleted file mode 100644 index 2c285554d..000000000 --- a/test-harness/xunit/Minimal Features/Inconclusive.feature.cs +++ /dev/null @@ -1,121 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class InconclusiveFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Inconclusive.feature" -#line hidden - - public InconclusiveFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Inconclusive", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(InconclusiveFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Inconclusive")] - [Xunit.TraitAttribute("Description", "Inconclusive Feature Passing Scenario")] - public virtual void InconclusiveFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Inconclusive")] - [Xunit.TraitAttribute("Description", "Inconclusive Feature Inconclusive Scenario")] - public virtual void InconclusiveFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - InconclusiveFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - InconclusiveFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/Minimal Features/Passing.feature b/test-harness/xunit/Minimal Features/Passing.feature deleted file mode 100644 index 14bf35e22..000000000 --- a/test-harness/xunit/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/xunit/Minimal Features/Passing.feature.cs b/test-harness/xunit/Minimal Features/Passing.feature.cs deleted file mode 100644 index 99010a9fc..000000000 --- a/test-harness/xunit/Minimal Features/Passing.feature.cs +++ /dev/null @@ -1,107 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class PassingFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Passing.feature" -#line hidden - - public PassingFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Passing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(PassingFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Passing")] - [Xunit.TraitAttribute("Description", "Passing Feature Passing Scenario")] - public virtual void PassingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Passing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - PassingFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - PassingFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/NotAutomatedAtAll.feature b/test-harness/xunit/NotAutomatedAtAll.feature deleted file mode 100644 index 3bbfcb669..000000000 --- a/test-harness/xunit/NotAutomatedAtAll.feature +++ /dev/null @@ -1,19 +0,0 @@ -Feature: Not Automated At All - -Background: - Given unimplemented step - -Scenario: Not automated scenario 1 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 2 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 3 - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/xunit/NotAutomatedAtAll.feature.cs b/test-harness/xunit/NotAutomatedAtAll.feature.cs deleted file mode 100644 index 66874d430..000000000 --- a/test-harness/xunit/NotAutomatedAtAll.feature.cs +++ /dev/null @@ -1,161 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class NotAutomatedAtAllFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "NotAutomatedAtAll.feature" -#line hidden - - public NotAutomatedAtAllFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Not Automated At All", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 3 -#line 4 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void SetFixture(NotAutomatedAtAllFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Not Automated At All")] - [Xunit.TraitAttribute("Description", "Not automated scenario 1")] - public virtual void NotAutomatedScenario1() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 1", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 7 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 8 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 9 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Not Automated At All")] - [Xunit.TraitAttribute("Description", "Not automated scenario 2")] - public virtual void NotAutomatedScenario2() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 2", ((string[])(null))); -#line 11 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 12 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 13 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 14 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Not Automated At All")] - [Xunit.TraitAttribute("Description", "Not automated scenario 3")] - public virtual void NotAutomatedScenario3() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 3", ((string[])(null))); -#line 16 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 17 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 18 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - NotAutomatedAtAllFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - NotAutomatedAtAllFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/Properties/AssemblyInfo.cs b/test-harness/xunit/Properties/AssemblyInfo.cs deleted file mode 100644 index 1d6f58aea..000000000 --- a/test-harness/xunit/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,36 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("xunit")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("")] -[assembly: AssemblyProduct("xunit")] -[assembly: AssemblyCopyright("Copyright © 2013")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM components. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("51211987-b886-4465-bbbd-081d7a7dd9d1")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Build and Revision Numbers -// by using the '*' as shown below: -// [assembly: AssemblyVersion("1.0.*")] -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/test-harness/xunit/ScenarioOutlines.feature b/test-harness/xunit/ScenarioOutlines.feature deleted file mode 100644 index 74f50e2af..000000000 --- a/test-harness/xunit/ScenarioOutlines.feature +++ /dev/null @@ -1,143 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - -Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - And I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - -Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - -Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - -Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - -Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | \ No newline at end of file diff --git a/test-harness/xunit/ScenarioOutlines.feature.cs b/test-harness/xunit/ScenarioOutlines.feature.cs deleted file mode 100644 index 593dc7091..000000000 --- a/test-harness/xunit/ScenarioOutlines.feature.cs +++ /dev/null @@ -1,291 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class ScenarioOutlinesFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenarioOutlines.feature" -#line hidden - - public ScenarioOutlinesFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenario Outlines", "Here we demonstrate how we deal with scenario outlines", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(ScenarioOutlinesFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "This is a scenario outline where all scenarios pass")] - [Xunit.Extensions.InlineDataAttribute("pass_1", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass_2", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass_3", new string[0])] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where all scenarios pass", exampleTags); -#line 4 -this.ScenarioSetup(scenarioInfo); -#line 8 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "This is a scenario outline where one scenario is inconclusive")] - [Xunit.Extensions.InlineDataAttribute("pass_1", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass_2", new string[0])] - [Xunit.Extensions.InlineDataAttribute("inconclusive_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario is inconclusive", exampleTags); -#line 17 -this.ScenarioSetup(scenarioInfo); -#line 21 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "This is a scenario outline where one scenario fails")] - [Xunit.Extensions.InlineDataAttribute("pass_1", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass_2", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario fails", exampleTags); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 34 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "And we can go totally bonkers with multiple example sections.")] - [Xunit.Extensions.InlineDataAttribute("pass_1", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass_2", new string[0])] - [Xunit.Extensions.InlineDataAttribute("inconclusive_1", new string[0])] - [Xunit.Extensions.InlineDataAttribute("inconclusive_2", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail_1", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail_2", new string[0])] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections_(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("And we can go totally bonkers with multiple example sections.", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 45 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal correctly with backslashes in the examples")] - [Xunit.Extensions.InlineDataAttribute("c:\\Temp\\", new string[0])] - public virtual void DealCorrectlyWithBackslashesInTheExamples(string filePath, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with backslashes in the examples", exampleTags); -#line 63 -this.ScenarioSetup(scenarioInfo); -#line 65 - testRunner.When(string.Format("I have backslashes in the value, for example a \'{0}\'", filePath), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal correctly with parenthesis in the examples")] - [Xunit.Extensions.InlineDataAttribute("This is a description (and more)", new string[0])] - public virtual void DealCorrectlyWithParenthesisInTheExamples(string overlyDescriptiveField, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with parenthesis in the examples", exampleTags); -#line 72 -this.ScenarioSetup(scenarioInfo); -#line 74 - testRunner.When(string.Format("I have parenthesis in the value, for example an \'{0}\'", overlyDescriptiveField), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal correctly with overlong example values")] - [Xunit.Extensions.InlineDataAttribute("Please enter a valid two letter country code (e.g. DE)!", "This is just a very very very veery long error message!", new string[0])] - public virtual void DealCorrectlyWithOverlongExampleValues(string value1, string value2, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with overlong example values", exampleTags); -#line 80 -this.ScenarioSetup(scenarioInfo); -#line 82 - testRunner.When(string.Format("I have a field with value \'{0}\'", value1), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 83 - testRunner.And(string.Format("I have a field with value \'{0}\'", value2), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 84 - testRunner.Then("the scenario will \'pass_1\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with duplicate values")] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("inconclusive", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - public virtual void DealWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with duplicate values", exampleTags); -#line 90 -this.ScenarioSetup(scenarioInfo); -#line 91 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with multiple example sections with duplicate values")] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("inconclusive", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple example sections with duplicate values", exampleTags); -#line 101 -this.ScenarioSetup(scenarioInfo); -#line 102 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with multiple named example sections without duplicate values")] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("inconclusive", new string[0])] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections without duplicate values", exampleTags); -#line 117 -this.ScenarioSetup(scenarioInfo); -#line 118 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with multiple named example sections with duplicate values")] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("inconclusive", new string[0])] - [Xunit.Extensions.InlineDataAttribute("fail", new string[0])] - [Xunit.Extensions.InlineDataAttribute("pass", new string[0])] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections with duplicate values", exampleTags); -#line 129 -this.ScenarioSetup(scenarioInfo); -#line 130 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - ScenarioOutlinesFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - ScenarioOutlinesFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/ScenariosWithSpecialCharacters.feature b/test-harness/xunit/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index 9597b2f2b..000000000 --- a/test-harness/xunit/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,54 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'PASS' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This is a scenario outline with ampersand & - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step diff --git a/test-harness/xunit/ScenariosWithSpecialCharacters.feature.cs b/test-harness/xunit/ScenariosWithSpecialCharacters.feature.cs deleted file mode 100644 index d26c29c88..000000000 --- a/test-harness/xunit/ScenariosWithSpecialCharacters.feature.cs +++ /dev/null @@ -1,231 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class ScenariosWithSpecialCharactersFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenariosWithSpecialCharacters.feature" -#line hidden - - public ScenariosWithSpecialCharactersFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenarios With Special Characters", "Here we demonstrate usage of special characters in scenario names", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void SetFixture(ScenariosWithSpecialCharactersFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario with parentheses, hyphen and comma (10-20, 30-40)")] - public virtual void ThisIsAScenarioWithParenthesesHyphenAndComma10_2030_40() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)", ((string[])(null))); -#line 7 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 8 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 9 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 10 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 11 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)")] - [Xunit.Extensions.InlineDataAttribute("pass_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This scenario contains examples with Regex-special characters")] - [Xunit.Extensions.InlineDataAttribute("**", new string[0])] - [Xunit.Extensions.InlineDataAttribute("++", new string[0])] - [Xunit.Extensions.InlineDataAttribute(".*", new string[0])] - [Xunit.Extensions.InlineDataAttribute("[]", new string[0])] - [Xunit.Extensions.InlineDataAttribute("{}", new string[0])] - [Xunit.Extensions.InlineDataAttribute("()", new string[0])] - [Xunit.Extensions.InlineDataAttribute("^.*(?BAR)\\s[^0-9]{3,4}A+$", new string[0])] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters(string regex, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This scenario contains examples with Regex-special characters", exampleTags); -#line 21 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 22 - testRunner.When(string.Format("I have special characters for regexes in the value, for example a \'{0}\'", regex), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 23 - testRunner.Then("the scenario will \'PASS\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario outline with german umlauts äöüß ÄÖÜ")] - [Xunit.Extensions.InlineDataAttribute("pass_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with german umlauts äöüß ÄÖÜ", exampleTags); -#line 36 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 37 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.Extensions.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario outline with ampersand &")] - [Xunit.Extensions.InlineDataAttribute("pass_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWithAmpersand(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with ampersand &", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 44 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario with danish characters æøå ÆØÅ")] - public virtual void ThisIsAScenarioWithDanishCharactersAEoaAEOA() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with danish characters æøå ÆØÅ", ((string[])(null))); -#line 50 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 51 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario with spanish characters ñáéíóú")] - public virtual void ThisIsAScenarioWithSpanishCharactersNaeiou() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with spanish characters ñáéíóú", ((string[])(null))); -#line 53 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 54 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - ScenariosWithSpecialCharactersFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - ScenariosWithSpecialCharactersFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit/packages.config b/test-harness/xunit/packages.config deleted file mode 100644 index 2975804e6..000000000 --- a/test-harness/xunit/packages.config +++ /dev/null @@ -1,7 +0,0 @@ - - - - - - - \ No newline at end of file diff --git a/test-harness/xunit/xunit.csproj b/test-harness/xunit/xunit.csproj deleted file mode 100644 index 0f372726f..000000000 --- a/test-harness/xunit/xunit.csproj +++ /dev/null @@ -1,150 +0,0 @@ - - - - - Debug - AnyCPU - {F4AB7229-9022-4FFC-86EC-570ADF2A682C} - Library - Properties - Pickles.TestHarness.xunit - xunitHarness - v4.5 - 512 - ..\ - true - - - true - full - false - bin\Debug\ - DEBUG;TRACE - prompt - 4 - - - pdbonly - true - bin\Release\ - TRACE - prompt - 4 - - - - - - - - - - - ..\packages\SpecFlow.1.9.0\lib\net35\TechTalk.SpecFlow.dll - - - False - ..\packages\xunit.1.9.2\lib\net20\xunit.dll - - - False - ..\packages\xunit.extensions.1.9.2\lib\net20\xunit.extensions.dll - - - - - Addition.feature - True - True - - - FailingBackground.feature - True - True - - - Failing.feature - True - True - - - Inconclusive.feature - True - True - - - Passing.feature - True - True - - - NotAutomatedAtAll.feature - True - True - - - - True - True - ScenarioOutlines.feature - - - True - True - ScenariosWithSpecialCharacters.feature - - - - - SpecFlowSingleFileGenerator - Addition.feature.cs - - - - SpecFlowSingleFileGenerator - FailingBackground.feature.cs - - - SpecFlowSingleFileGenerator - Failing.feature.cs - - - SpecFlowSingleFileGenerator - Inconclusive.feature.cs - - - SpecFlowSingleFileGenerator - Passing.feature.cs - - - SpecFlowSingleFileGenerator - NotAutomatedAtAll.feature.cs - - - - SpecFlowSingleFileGenerator - ScenarioOutlines.feature.cs - - - SpecFlowSingleFileGenerator - ScenariosWithSpecialCharacters.feature.cs - - - - - {073862de-d599-4941-9716-03206cf1cfa2} - AutomationLayer - - - - - - - - \ No newline at end of file diff --git a/test-harness/xunit2/Addition.feature b/test-harness/xunit2/Addition.feature deleted file mode 100644 index 238e261e9..000000000 --- a/test-harness/xunit2/Addition.feature +++ /dev/null @@ -1,46 +0,0 @@ -Feature: Addition - In order to avoid silly mistakes - As a math idiot - I want to be told the sum of two numbers - -Background: - Given the calculator has clean memory - -@tag2 -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | - -@tag1 -Scenario: Add two numbers - Given I have entered 1 into the calculator - And I have entered 2 into the calculator - When I press add - Then the result should be 3 on the screen - -@tag1 -Scenario: Fail to add two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -@ignore -Scenario: Ignored adding two numbers - Given I have entered 1 into the calculator - And I have entered 2.2 into the calculator - When I press add - Then the result should be 3.2 on the screen - -Scenario: Not automated adding two numbers - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/xunit2/Addition.feature.cs b/test-harness/xunit2/Addition.feature.cs deleted file mode 100644 index 13865cf68..000000000 --- a/test-harness/xunit2/Addition.feature.cs +++ /dev/null @@ -1,223 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class AdditionFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Addition.feature" -#line hidden - - public AdditionFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Addition", "In order to avoid silly mistakes\r\nAs a math idiot\r\nI want to be told the sum of t" + - "wo numbers", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 6 -#line 7 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void SetFixture(AdditionFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Adding several numbers")] - [Xunit.InlineDataAttribute("60", "70", "130", "260", new string[0])] - [Xunit.InlineDataAttribute("40", "50", "90", "180", new string[0])] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - string[] @__tags = new string[] { - "tag2"}; - if ((exampleTags != null)) - { - @__tags = System.Linq.Enumerable.ToArray(System.Linq.Enumerable.Concat(@__tags, exampleTags)); - } - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", @__tags); -#line 10 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 11 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 12 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 13 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 14 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 15 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Add two numbers")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", new string[] { - "tag1"}); -#line 23 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 24 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 25 - testRunner.And("I have entered 2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 26 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 27 - testRunner.Then("the result should be 3 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Fail to add two numbers")] - public virtual void FailToAddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Fail to add two numbers", new string[] { - "tag1"}); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 31 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 32 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 33 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 34 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute(Skip="Ignored")] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Ignored adding two numbers")] - public virtual void IgnoredAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Ignored adding two numbers", new string[] { - "ignore"}); -#line 37 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 38 - testRunner.Given("I have entered 1 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 39 - testRunner.And("I have entered 2.2 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 40 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 41 - testRunner.Then("the result should be 3.2 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Addition")] - [Xunit.TraitAttribute("Description", "Not automated adding two numbers")] - public virtual void NotAutomatedAddingTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated adding two numbers", ((string[])(null))); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 6 -this.FeatureBackground(); -#line 44 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 45 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 46 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - AdditionFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - AdditionFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/FailingBackground.feature b/test-harness/xunit2/FailingBackground.feature deleted file mode 100644 index 83a70483a..000000000 --- a/test-harness/xunit2/FailingBackground.feature +++ /dev/null @@ -1,24 +0,0 @@ -Feature: Failing Background -This feature has a failing background. - -Background: - Given the background step fails - And the calculator has clean memory - -Scenario: Add two numbers - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - -Scenario Outline: Adding several numbers - Given I have entered into the calculator - And I have entered into the calculator - And I have entered into the calculator - When I press add - Then the result should be on the screen - -Examples: - | first number | second number | third number | result | - | 60 | 70 | 130 | 260 | - | 40 | 50 | 90 | 180 | diff --git a/test-harness/xunit2/FailingBackground.feature.cs b/test-harness/xunit2/FailingBackground.feature.cs deleted file mode 100644 index dd8ea94ff..000000000 --- a/test-harness/xunit2/FailingBackground.feature.cs +++ /dev/null @@ -1,151 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class FailingBackgroundFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "FailingBackground.feature" -#line hidden - - public FailingBackgroundFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing Background", "This feature has a failing background.", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the background step fails", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 6 - testRunner.And("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line hidden - } - - public virtual void SetFixture(FailingBackgroundFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing Background")] - [Xunit.TraitAttribute("Description", "Add two numbers")] - public virtual void AddTwoNumbers() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Add two numbers", ((string[])(null))); -#line 8 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 9 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 10 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 11 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 12 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing Background")] - [Xunit.TraitAttribute("Description", "Adding several numbers")] - [Xunit.InlineDataAttribute("60", "70", "130", "260", new string[0])] - [Xunit.InlineDataAttribute("40", "50", "90", "180", new string[0])] - public virtual void AddingSeveralNumbers(string firstNumber, string secondNumber, string thirdNumber, string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Adding several numbers", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Given(string.Format("I have entered {0} into the calculator", firstNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 16 - testRunner.And(string.Format("I have entered {0} into the calculator", secondNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 17 - testRunner.And(string.Format("I have entered {0} into the calculator", thirdNumber), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 18 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then(string.Format("the result should be {0} on the screen", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - FailingBackgroundFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - FailingBackgroundFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/Minimal Features/Failing.feature b/test-harness/xunit2/Minimal Features/Failing.feature deleted file mode 100644 index d7c5b7f53..000000000 --- a/test-harness/xunit2/Minimal Features/Failing.feature +++ /dev/null @@ -1,10 +0,0 @@ -Feature: Failing - -Scenario: Failing Feature Passing Scenario - Then passing step - -Scenario: Failing Feature Inconclusive Scenario - Then inconclusive step - -Scenario: Failing Feature Failing Scenario - Then failing step \ No newline at end of file diff --git a/test-harness/xunit2/Minimal Features/Failing.feature.cs b/test-harness/xunit2/Minimal Features/Failing.feature.cs deleted file mode 100644 index 7e3b307c2..000000000 --- a/test-harness/xunit2/Minimal Features/Failing.feature.cs +++ /dev/null @@ -1,135 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class FailingFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Failing.feature" -#line hidden - - public FailingFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Failing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(FailingFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing")] - [Xunit.TraitAttribute("Description", "Failing Feature Passing Scenario")] - public virtual void FailingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing")] - [Xunit.TraitAttribute("Description", "Failing Feature Inconclusive Scenario")] - public virtual void FailingFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Failing")] - [Xunit.TraitAttribute("Description", "Failing Feature Failing Scenario")] - public virtual void FailingFeatureFailingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Failing Feature Failing Scenario", ((string[])(null))); -#line 9 -this.ScenarioSetup(scenarioInfo); -#line 10 - testRunner.Then("failing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - FailingFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - FailingFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/Minimal Features/Inconclusive.feature b/test-harness/xunit2/Minimal Features/Inconclusive.feature deleted file mode 100644 index 7ce63f2d5..000000000 --- a/test-harness/xunit2/Minimal Features/Inconclusive.feature +++ /dev/null @@ -1,7 +0,0 @@ -Feature: Inconclusive - -Scenario: Inconclusive Feature Passing Scenario - Then passing step - -Scenario: Inconclusive Feature Inconclusive Scenario - Then inconclusive step \ No newline at end of file diff --git a/test-harness/xunit2/Minimal Features/Inconclusive.feature.cs b/test-harness/xunit2/Minimal Features/Inconclusive.feature.cs deleted file mode 100644 index 5949fe978..000000000 --- a/test-harness/xunit2/Minimal Features/Inconclusive.feature.cs +++ /dev/null @@ -1,121 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class InconclusiveFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Inconclusive.feature" -#line hidden - - public InconclusiveFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Inconclusive", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(InconclusiveFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Inconclusive")] - [Xunit.TraitAttribute("Description", "Inconclusive Feature Passing Scenario")] - public virtual void InconclusiveFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Inconclusive")] - [Xunit.TraitAttribute("Description", "Inconclusive Feature Inconclusive Scenario")] - public virtual void InconclusiveFeatureInconclusiveScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Inconclusive Feature Inconclusive Scenario", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 7 - testRunner.Then("inconclusive step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - InconclusiveFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - InconclusiveFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/Minimal Features/Passing.feature b/test-harness/xunit2/Minimal Features/Passing.feature deleted file mode 100644 index 14bf35e22..000000000 --- a/test-harness/xunit2/Minimal Features/Passing.feature +++ /dev/null @@ -1,4 +0,0 @@ -Feature: Passing - -Scenario: Passing Feature Passing Scenario - Then passing step diff --git a/test-harness/xunit2/Minimal Features/Passing.feature.cs b/test-harness/xunit2/Minimal Features/Passing.feature.cs deleted file mode 100644 index e04c3c079..000000000 --- a/test-harness/xunit2/Minimal Features/Passing.feature.cs +++ /dev/null @@ -1,107 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2.MinimalFeatures -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class PassingFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "Passing.feature" -#line hidden - - public PassingFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Passing", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(PassingFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Passing")] - [Xunit.TraitAttribute("Description", "Passing Feature Passing Scenario")] - public virtual void PassingFeaturePassingScenario() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Passing Feature Passing Scenario", ((string[])(null))); -#line 3 -this.ScenarioSetup(scenarioInfo); -#line 4 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - PassingFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - PassingFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/NotAutomatedAtAll.feature b/test-harness/xunit2/NotAutomatedAtAll.feature deleted file mode 100644 index 3bbfcb669..000000000 --- a/test-harness/xunit2/NotAutomatedAtAll.feature +++ /dev/null @@ -1,19 +0,0 @@ -Feature: Not Automated At All - -Background: - Given unimplemented step - -Scenario: Not automated scenario 1 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 2 - Given unimplemented step - When unimplemented step - Then unimplemented step - -Scenario: Not automated scenario 3 - Given unimplemented step - When unimplemented step - Then unimplemented step diff --git a/test-harness/xunit2/NotAutomatedAtAll.feature.cs b/test-harness/xunit2/NotAutomatedAtAll.feature.cs deleted file mode 100644 index 378699640..000000000 --- a/test-harness/xunit2/NotAutomatedAtAll.feature.cs +++ /dev/null @@ -1,161 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class NotAutomatedAtAllFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "NotAutomatedAtAll.feature" -#line hidden - - public NotAutomatedAtAllFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Not Automated At All", "", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 3 -#line 4 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void SetFixture(NotAutomatedAtAllFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Not Automated At All")] - [Xunit.TraitAttribute("Description", "Not automated scenario 1")] - public virtual void NotAutomatedScenario1() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 1", ((string[])(null))); -#line 6 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 7 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 8 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 9 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Not Automated At All")] - [Xunit.TraitAttribute("Description", "Not automated scenario 2")] - public virtual void NotAutomatedScenario2() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 2", ((string[])(null))); -#line 11 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 12 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 13 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 14 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Not Automated At All")] - [Xunit.TraitAttribute("Description", "Not automated scenario 3")] - public virtual void NotAutomatedScenario3() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Not automated scenario 3", ((string[])(null))); -#line 16 -this.ScenarioSetup(scenarioInfo); -#line 3 -this.FeatureBackground(); -#line 17 - testRunner.Given("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 18 - testRunner.When("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 19 - testRunner.Then("unimplemented step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - NotAutomatedAtAllFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - NotAutomatedAtAllFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/Properties/AssemblyInfo.cs b/test-harness/xunit2/Properties/AssemblyInfo.cs deleted file mode 100644 index 9f27651f8..000000000 --- a/test-harness/xunit2/Properties/AssemblyInfo.cs +++ /dev/null @@ -1,36 +0,0 @@ -using System.Reflection; -using System.Runtime.CompilerServices; -using System.Runtime.InteropServices; - -// General Information about an assembly is controlled through the following -// set of attributes. Change these attribute values to modify the information -// associated with an assembly. -[assembly: AssemblyTitle("xunit2")] -[assembly: AssemblyDescription("")] -[assembly: AssemblyConfiguration("")] -[assembly: AssemblyCompany("")] -[assembly: AssemblyProduct("xunit2")] -[assembly: AssemblyCopyright("Copyright © 2015")] -[assembly: AssemblyTrademark("")] -[assembly: AssemblyCulture("")] - -// Setting ComVisible to false makes the types in this assembly not visible -// to COM components. If you need to access a type in this assembly from -// COM, set the ComVisible attribute to true on that type. -[assembly: ComVisible(false)] - -// The following GUID is for the ID of the typelib if this project is exposed to COM -[assembly: Guid("e5b28db5-295e-4e33-a9e3-d84a49265baf")] - -// Version information for an assembly consists of the following four values: -// -// Major Version -// Minor Version -// Build Number -// Revision -// -// You can specify all the values or you can default the Build and Revision Numbers -// by using the '*' as shown below: -// [assembly: AssemblyVersion("1.0.*")] -[assembly: AssemblyVersion("1.0.0.0")] -[assembly: AssemblyFileVersion("1.0.0.0")] diff --git a/test-harness/xunit2/ScenarioOutlines.feature b/test-harness/xunit2/ScenarioOutlines.feature deleted file mode 100644 index ff2d2fb53..000000000 --- a/test-harness/xunit2/ScenarioOutlines.feature +++ /dev/null @@ -1,143 +0,0 @@ -Feature: Scenario Outlines - Here we demonstrate how we deal with scenario outlines - -Scenario Outline: This is a scenario outline where all scenarios pass - - This means the entire scenario outline passes. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | pass_3 | - - -Scenario Outline: This is a scenario outline where one scenario is inconclusive - - This means the entire scenario outline is inconclusive. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | inconclusive_1 | - - -Scenario Outline: This is a scenario outline where one scenario fails - - This means the entire scenario outline fails. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - | fail_1 | - - -Scenario Outline: And we can go totally bonkers with multiple example sections. - - Then the scenario will '' - - Examples: - | result | - | pass_1 | - | pass_2 | - - Examples: - | result | - | inconclusive_1 | - | inconclusive_2 | - - Examples: - | result | - | fail_1 | - | fail_2 | - - -Scenario Outline: Deal correctly with backslashes in the examples - - When I have backslashes in the value, for example a '' - - Examples: - | file path | - | c:\Temp\ | - - -Scenario Outline: Deal correctly with parenthesis in the examples - - When I have parenthesis in the value, for example an '' - - Examples: - | overly descriptive field | - | This is a description (and more) | - -Scenario Outline: Deal correctly with overlong example values - - When I have a field with value '' - And I have a field with value '' - Then the scenario will 'pass_1' - - Examples: - | value1 | value2 | - | Please enter a valid two letter country code (e.g. DE)! | This is just a very very very veery long error message! | - -Scenario Outline: Deal with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | inconclusive | - | pass | - | fail | - -Scenario Outline: Deal with multiple example sections with duplicate values - Then the scenario will '' - - Examples: - | result | - | pass | - | fail | - | pass | - - Examples: - | result | - | fail | - | inconclusive | - | fail | - | pass | - -Scenario Outline: Deal with multiple named example sections without duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - - Examples: Second set - | result | - | inconclusive | - -Scenario Outline: Deal with multiple named example sections with duplicate values - Then the scenario will '' - - Examples: First set - | result | - | pass | - | fail | - | pass | - - Examples: Second set - | result | - | fail | - | inconclusive | - | fail | - | pass | \ No newline at end of file diff --git a/test-harness/xunit2/ScenarioOutlines.feature.cs b/test-harness/xunit2/ScenarioOutlines.feature.cs deleted file mode 100644 index 9faa638f1..000000000 --- a/test-harness/xunit2/ScenarioOutlines.feature.cs +++ /dev/null @@ -1,291 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class ScenarioOutlinesFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenarioOutlines.feature" -#line hidden - - public ScenarioOutlinesFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenario Outlines", "Here we demonstrate how we deal with scenario outlines", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void SetFixture(ScenarioOutlinesFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "This is a scenario outline where all scenarios pass")] - [Xunit.InlineDataAttribute("pass_1", new string[0])] - [Xunit.InlineDataAttribute("pass_2", new string[0])] - [Xunit.InlineDataAttribute("pass_3", new string[0])] - public virtual void ThisIsAScenarioOutlineWhereAllScenariosPass(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where all scenarios pass", exampleTags); -#line 4 -this.ScenarioSetup(scenarioInfo); -#line 8 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "This is a scenario outline where one scenario is inconclusive")] - [Xunit.InlineDataAttribute("pass_1", new string[0])] - [Xunit.InlineDataAttribute("pass_2", new string[0])] - [Xunit.InlineDataAttribute("inconclusive_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioIsInconclusive(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario is inconclusive", exampleTags); -#line 17 -this.ScenarioSetup(scenarioInfo); -#line 21 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "This is a scenario outline where one scenario fails")] - [Xunit.InlineDataAttribute("pass_1", new string[0])] - [Xunit.InlineDataAttribute("pass_2", new string[0])] - [Xunit.InlineDataAttribute("fail_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWhereOneScenarioFails(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline where one scenario fails", exampleTags); -#line 30 -this.ScenarioSetup(scenarioInfo); -#line 34 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "And we can go totally bonkers with multiple example sections.")] - [Xunit.InlineDataAttribute("pass_1", new string[0])] - [Xunit.InlineDataAttribute("pass_2", new string[0])] - [Xunit.InlineDataAttribute("inconclusive_1", new string[0])] - [Xunit.InlineDataAttribute("inconclusive_2", new string[0])] - [Xunit.InlineDataAttribute("fail_1", new string[0])] - [Xunit.InlineDataAttribute("fail_2", new string[0])] - public virtual void AndWeCanGoTotallyBonkersWithMultipleExampleSections_(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("And we can go totally bonkers with multiple example sections.", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 45 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal correctly with backslashes in the examples")] - [Xunit.InlineDataAttribute("c:\\Temp\\", new string[0])] - public virtual void DealCorrectlyWithBackslashesInTheExamples(string filePath, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with backslashes in the examples", exampleTags); -#line 63 -this.ScenarioSetup(scenarioInfo); -#line 65 - testRunner.When(string.Format("I have backslashes in the value, for example a \'{0}\'", filePath), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal correctly with parenthesis in the examples")] - [Xunit.InlineDataAttribute("This is a description (and more)", new string[0])] - public virtual void DealCorrectlyWithParenthesisInTheExamples(string overlyDescriptiveField, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with parenthesis in the examples", exampleTags); -#line 72 -this.ScenarioSetup(scenarioInfo); -#line 74 - testRunner.When(string.Format("I have parenthesis in the value, for example an \'{0}\'", overlyDescriptiveField), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal correctly with overlong example values")] - [Xunit.InlineDataAttribute("Please enter a valid two letter country code (e.g. DE)!", "This is just a very very very veery long error message!", new string[0])] - public virtual void DealCorrectlyWithOverlongExampleValues(string value1, string value2, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal correctly with overlong example values", exampleTags); -#line 80 -this.ScenarioSetup(scenarioInfo); -#line 82 - testRunner.When(string.Format("I have a field with value \'{0}\'", value1), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 83 - testRunner.And(string.Format("I have a field with value \'{0}\'", value2), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 84 - testRunner.Then("the scenario will \'pass_1\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with duplicate values")] - [Xunit.InlineDataAttribute("pass", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("inconclusive", new string[0])] - [Xunit.InlineDataAttribute("pass", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - public virtual void DealWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with duplicate values", exampleTags); -#line 90 -this.ScenarioSetup(scenarioInfo); -#line 91 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with multiple example sections with duplicate values")] - [Xunit.InlineDataAttribute("pass", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("pass", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("inconclusive", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("pass", new string[0])] - public virtual void DealWithMultipleExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple example sections with duplicate values", exampleTags); -#line 101 -this.ScenarioSetup(scenarioInfo); -#line 102 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with multiple named example sections without duplicate values")] - [Xunit.InlineDataAttribute("pass", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("inconclusive", new string[0])] - public virtual void DealWithMultipleNamedExampleSectionsWithoutDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections without duplicate values", exampleTags); -#line 117 -this.ScenarioSetup(scenarioInfo); -#line 118 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenario Outlines")] - [Xunit.TraitAttribute("Description", "Deal with multiple named example sections with duplicate values")] - [Xunit.InlineDataAttribute("pass", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("pass", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("inconclusive", new string[0])] - [Xunit.InlineDataAttribute("fail", new string[0])] - [Xunit.InlineDataAttribute("pass", new string[0])] - public virtual void DealWithMultipleNamedExampleSectionsWithDuplicateValues(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("Deal with multiple named example sections with duplicate values", exampleTags); -#line 129 -this.ScenarioSetup(scenarioInfo); -#line 130 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - ScenarioOutlinesFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - ScenarioOutlinesFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/ScenariosWithSpecialCharacters.feature b/test-harness/xunit2/ScenariosWithSpecialCharacters.feature deleted file mode 100644 index 9597b2f2b..000000000 --- a/test-harness/xunit2/ScenariosWithSpecialCharacters.feature +++ /dev/null @@ -1,54 +0,0 @@ -Feature: Scenarios With Special Characters - Here we demonstrate usage of special characters in scenario names - -Background: - Given the calculator has clean memory - -Scenario: This is a scenario with parentheses, hyphen and comma (10-20, 30-40) - Given I have entered 50 into the calculator - And I have entered 70 into the calculator - When I press add - Then the result should be 120 on the screen - - -Scenario Outline: This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40) - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This scenario contains examples with Regex-special characters - When I have special characters for regexes in the value, for example a '' - Then the scenario will 'PASS' - - Examples: - | regex | - | ** | - | ++ | - | .* | - | [] | - | {} | - | () | - | ^.*(?BAR)\s[^0-9]{3,4}A+$ | - - -Scenario Outline: This is a scenario outline with german umlauts äöüß ÄÖÜ - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario Outline: This is a scenario outline with ampersand & - Then the scenario will '' - - Examples: - | result | - | pass_1 | - -Scenario: This is a scenario with danish characters æøå ÆØÅ - Then passing step - -Scenario: This is a scenario with spanish characters ñáéíóú - Then passing step diff --git a/test-harness/xunit2/ScenariosWithSpecialCharacters.feature.cs b/test-harness/xunit2/ScenariosWithSpecialCharacters.feature.cs deleted file mode 100644 index d96e26469..000000000 --- a/test-harness/xunit2/ScenariosWithSpecialCharacters.feature.cs +++ /dev/null @@ -1,231 +0,0 @@ -// ------------------------------------------------------------------------------ -// -// This code was generated by SpecFlow (http://www.specflow.org/). -// SpecFlow Version:1.9.0.77 -// SpecFlow Generator Version:1.9.0.0 -// Runtime Version:4.0.30319.42000 -// -// Changes to this file may cause incorrect behavior and will be lost if -// the code is regenerated. -// -// ------------------------------------------------------------------------------ -#region Designer generated code -#pragma warning disable -namespace Pickles.TestHarness.xunit2 -{ - using TechTalk.SpecFlow; - - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public partial class ScenariosWithSpecialCharactersFeature : Xunit.IUseFixture, System.IDisposable - { - - private static TechTalk.SpecFlow.ITestRunner testRunner; - -#line 1 "ScenariosWithSpecialCharacters.feature" -#line hidden - - public ScenariosWithSpecialCharactersFeature() - { - this.TestInitialize(); - } - - public static void FeatureSetup() - { - testRunner = TechTalk.SpecFlow.TestRunnerManager.GetTestRunner(); - TechTalk.SpecFlow.FeatureInfo featureInfo = new TechTalk.SpecFlow.FeatureInfo(new System.Globalization.CultureInfo("en-US"), "Scenarios With Special Characters", "Here we demonstrate usage of special characters in scenario names", ProgrammingLanguage.CSharp, ((string[])(null))); - testRunner.OnFeatureStart(featureInfo); - } - - public static void FeatureTearDown() - { - testRunner.OnFeatureEnd(); - testRunner = null; - } - - public virtual void TestInitialize() - { - } - - public virtual void ScenarioTearDown() - { - testRunner.OnScenarioEnd(); - } - - public virtual void ScenarioSetup(TechTalk.SpecFlow.ScenarioInfo scenarioInfo) - { - testRunner.OnScenarioStart(scenarioInfo); - } - - public virtual void ScenarioCleanup() - { - testRunner.CollectScenarioErrors(); - } - - public virtual void FeatureBackground() - { -#line 4 -#line 5 - testRunner.Given("the calculator has clean memory", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line hidden - } - - public virtual void SetFixture(ScenariosWithSpecialCharactersFeature.FixtureData fixtureData) - { - } - - void System.IDisposable.Dispose() - { - this.ScenarioTearDown(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario with parentheses, hyphen and comma (10-20, 30-40)")] - public virtual void ThisIsAScenarioWithParenthesesHyphenAndComma10_2030_40() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with parentheses, hyphen and comma (10-20, 30-40)", ((string[])(null))); -#line 7 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 8 - testRunner.Given("I have entered 50 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Given "); -#line 9 - testRunner.And("I have entered 70 into the calculator", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "And "); -#line 10 - testRunner.When("I press add", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 11 - testRunner.Then("the result should be 120 on the screen", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)")] - [Xunit.InlineDataAttribute("pass_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWithParenthesesHyphenAndComma10_2030_40(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with parentheses, hyphen and comma (10-20, 30-40)", exampleTags); -#line 14 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 15 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This scenario contains examples with Regex-special characters")] - [Xunit.InlineDataAttribute("**", new string[0])] - [Xunit.InlineDataAttribute("++", new string[0])] - [Xunit.InlineDataAttribute(".*", new string[0])] - [Xunit.InlineDataAttribute("[]", new string[0])] - [Xunit.InlineDataAttribute("{}", new string[0])] - [Xunit.InlineDataAttribute("()", new string[0])] - [Xunit.InlineDataAttribute("^.*(?BAR)\\s[^0-9]{3,4}A+$", new string[0])] - public virtual void ThisScenarioContainsExamplesWithRegex_SpecialCharacters(string regex, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This scenario contains examples with Regex-special characters", exampleTags); -#line 21 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 22 - testRunner.When(string.Format("I have special characters for regexes in the value, for example a \'{0}\'", regex), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "When "); -#line 23 - testRunner.Then("the scenario will \'PASS\'", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario outline with german umlauts äöüß ÄÖÜ")] - [Xunit.InlineDataAttribute("pass_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWithGermanUmlautsAouBAOU(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with german umlauts äöüß ÄÖÜ", exampleTags); -#line 36 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 37 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.TheoryAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario outline with ampersand &")] - [Xunit.InlineDataAttribute("pass_1", new string[0])] - public virtual void ThisIsAScenarioOutlineWithAmpersand(string result, string[] exampleTags) - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario outline with ampersand &", exampleTags); -#line 43 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 44 - testRunner.Then(string.Format("the scenario will \'{0}\'", result), ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario with danish characters æøå ÆØÅ")] - public virtual void ThisIsAScenarioWithDanishCharactersAEoaAEOA() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with danish characters æøå ÆØÅ", ((string[])(null))); -#line 50 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 51 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [Xunit.FactAttribute()] - [Xunit.TraitAttribute("FeatureTitle", "Scenarios With Special Characters")] - [Xunit.TraitAttribute("Description", "This is a scenario with spanish characters ñáéíóú")] - public virtual void ThisIsAScenarioWithSpanishCharactersNaeiou() - { - TechTalk.SpecFlow.ScenarioInfo scenarioInfo = new TechTalk.SpecFlow.ScenarioInfo("This is a scenario with spanish characters ñáéíóú", ((string[])(null))); -#line 53 -this.ScenarioSetup(scenarioInfo); -#line 4 -this.FeatureBackground(); -#line 54 - testRunner.Then("passing step", ((string)(null)), ((TechTalk.SpecFlow.Table)(null)), "Then "); -#line hidden - this.ScenarioCleanup(); - } - - [System.CodeDom.Compiler.GeneratedCodeAttribute("TechTalk.SpecFlow", "1.9.0.77")] - [System.Runtime.CompilerServices.CompilerGeneratedAttribute()] - public class FixtureData : System.IDisposable - { - - public FixtureData() - { - ScenariosWithSpecialCharactersFeature.FeatureSetup(); - } - - void System.IDisposable.Dispose() - { - ScenariosWithSpecialCharactersFeature.FeatureTearDown(); - } - } - } -} -#pragma warning restore -#endregion diff --git a/test-harness/xunit2/XunitCompatibility.cs b/test-harness/xunit2/XunitCompatibility.cs deleted file mode 100644 index ff239f63b..000000000 --- a/test-harness/xunit2/XunitCompatibility.cs +++ /dev/null @@ -1,32 +0,0 @@ -// -------------------------------------------------------------------------------------------------------------------- -// -// Copyright 2011 Jeffrey Cameron -// Copyright 2012-present PicklesDoc team and community contributors -// -// -// Licensed under the Apache License, Version 2.0 (the "License"); -// you may not use this file except in compliance with the License. -// You may obtain a copy of the License at -// -// http://www.apache.org/licenses/LICENSE-2.0 -// -// Unless required by applicable law or agreed to in writing, software -// distributed under the License is distributed on an "AS IS" BASIS, -// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -// See the License for the specific language governing permissions and -// limitations under the License. -// -// -------------------------------------------------------------------------------------------------------------------- -namespace Xunit -{ - /// - /// XUnit backwards compatibility for feature generator - /// - /// - /// Delete this when generator no longer uses this class - 5/25/15 - /// - /// - public interface IUseFixture : Xunit.IClassFixture where T : class, new() - { - } -} \ No newline at end of file diff --git a/test-harness/xunit2/app.config b/test-harness/xunit2/app.config deleted file mode 100644 index f62dc8400..000000000 --- a/test-harness/xunit2/app.config +++ /dev/null @@ -1,13 +0,0 @@ - - - -
          - - - - - - - - - \ No newline at end of file diff --git a/test-harness/xunit2/packages.config b/test-harness/xunit2/packages.config deleted file mode 100644 index ba2df9220..000000000 --- a/test-harness/xunit2/packages.config +++ /dev/null @@ -1,44 +0,0 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file diff --git a/test-harness/xunit2/xunit2.csproj b/test-harness/xunit2/xunit2.csproj deleted file mode 100644 index 9ff90b1f0..000000000 --- a/test-harness/xunit2/xunit2.csproj +++ /dev/null @@ -1,179 +0,0 @@ - - - - - - - - Debug - AnyCPU - {E5B28DB5-295E-4E33-A9E3-D84A49265BAF} - Library - Properties - Pickles.TestHarness.xunit2 - xunit2Harness - v4.5 - 512 - - - - - true - full - false - bin\Debug\ - DEBUG;TRACE - prompt - 4 - - - pdbonly - true - bin\Release\ - TRACE - prompt - 4 - - - - - - - - - ..\packages\System.Runtime.InteropServices.RuntimeInformation.4.3.0\lib\net45\System.Runtime.InteropServices.RuntimeInformation.dll - - - - - - - - - ..\packages\SpecFlow.1.9.0\lib\net35\TechTalk.SpecFlow.dll - True - - - ..\packages\xunit.abstractions.2.0.3\lib\net35\xunit.abstractions.dll - - - ..\packages\xunit.assert.2.4.0\lib\netstandard1.1\xunit.assert.dll - - - ..\packages\xunit.extensibility.core.2.4.0\lib\netstandard1.1\xunit.core.dll - - - ..\packages\xunit.extensibility.execution.2.4.0\lib\netstandard1.1\xunit.execution.dotnet.dll - - - - - Addition.feature - True - True - - - FailingBackground.feature - True - True - - - Failing.feature - True - True - - - Inconclusive.feature - True - True - - - Passing.feature - True - True - - - NotAutomatedAtAll.feature - True - True - - - - ScenarioOutlines.feature - True - True - - - True - True - ScenariosWithSpecialCharacters.feature - - - - - - {073862de-d599-4941-9716-03206cf1cfa2} - AutomationLayer - - - - - SpecFlowSingleFileGenerator - Addition.feature.cs - - - - SpecFlowSingleFileGenerator - FailingBackground.feature.cs - - - SpecFlowSingleFileGenerator - Failing.feature.cs - - - SpecFlowSingleFileGenerator - Inconclusive.feature.cs - - - SpecFlowSingleFileGenerator - Passing.feature.cs - - - SpecFlowSingleFileGenerator - NotAutomatedAtAll.feature.cs - - - - SpecFlowSingleFileGenerator - ScenarioOutlines.feature.cs - - - SpecFlowSingleFileGenerator - ScenariosWithSpecialCharacters.feature.cs - - - - - - - - - - - - This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is {0}. - - - - - - - - - \ No newline at end of file diff --git a/test.bat b/test.bat deleted file mode 100644 index fd66b86fb..000000000 --- a/test.bat +++ /dev/null @@ -1,4 +0,0 @@ -@echo off -set "fakeVersion=3.36.0" - -"packages\FAKE\tools\Fake.exe" test.fsx diff --git a/test.fsx b/test.fsx deleted file mode 100644 index 0089de853..000000000 --- a/test.fsx +++ /dev/null @@ -1,133 +0,0 @@ -// include Fake lib -#r @"packages\FAKE\tools\FakeLib.dll" -open Fake -open Fake.Testing - - -// Properties -let testDir = "./test/" - -Target "Test" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.Test.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.Test.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.TestFrameworks" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.TestFrameworks.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.TestFrameworks.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Cucumber" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Cucumber.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Cucumber.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Dhtml" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Dhtml.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Dhtml.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Excel" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Excel.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Excel.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Html" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Html.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Html.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Json" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Json.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Json.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Word" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Word.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Word.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Markdown.UnitTests" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Markdown.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Markdown.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.DocumentationBuilders.Markdown.AcceptanceTests" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.DocumentationBuilders.Markdown.AcceptanceTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.DocumentationBuilders.Markdown.AcceptanceTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - - -Target "Test.Runners.CommandLine" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.CommandLine.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.CommandLine.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -Target "Test.Runners.UI" (fun _ -> - !! (testDir + "PicklesDoc.Pickles.UserInterface.UnitTests.dll") - |> NUnit3 (fun p -> - {p with - ShadowCopy = false; - OutputDir = testDir + "PicklesDoc.Pickles.UserInterface.UnitTests.TestResults.xml"; - ToolPath = "packages/NUnit.ConsoleRunner/tools/nunit3-console.exe" }) -) - -"Test" - ==> "Test.DocumentationBuilders.Cucumber" - ==> "Test.DocumentationBuilders.Dhtml" - ==> "Test.DocumentationBuilders.Excel" - ==> "Test.DocumentationBuilders.Html" - ==> "Test.DocumentationBuilders.Json" - ==> "Test.DocumentationBuilders.Word" - ==> "Test.DocumentationBuilders.Markdown.UnitTests" - ==> "Test.DocumentationBuilders.Markdown.AcceptanceTests" - ==> "Test.Runners.CommandLine" - ==> "Test.Runners.UI" - ==> "Test.TestFrameworks" - -// start build -RunTargetOrDefault "Test.TestFrameworks" \ No newline at end of file diff --git a/testOutput.proj b/testOutput.proj deleted file mode 100644 index 662c463f3..000000000 --- a/testOutput.proj +++ /dev/null @@ -1,34 +0,0 @@ - - - .\Output\ - .\src\Pickles\Examples\ - - - - Html - - - Dhtml - - - Word - - - Excel - - - JSON - - - Cucumber - - - Markdown - - - - - - - - diff --git a/testOutput.ps1 b/testOutput.ps1 deleted file mode 100644 index 6e6fdd45c..000000000 --- a/testOutput.ps1 +++ /dev/null @@ -1,47 +0,0 @@ -$version = $args[0] -$formats = @("Html", "Dhtml", "Word", "Excel", "JSON", "Cucumber", "Markdown") -$PSScriptRoot = Split-Path $MyInvocation.MyCommand.Path -Parent - -Try -{ - foreach ($format in $formats) - { - # Setup variables - $FeatureDirectory = $PSScriptRoot + "\src\Pickles\Examples" - $OutputDirectory = $PSScriptRoot + "\Output\" + $format - $DocumentationFormat = $format - $SystemUnderTestName = "Pickles" - $SystemUnderTestVersion = $version - $TestResultsFormat = "" - $TestResultsFile = "" - - # Import the Pickles-comandlet - $pathToModule = ".\deploy\nuget\packages\pickles." + $version + "\tools\PicklesDoc.Pickles.PowerShell.dll" - Import-Module $pathToModule - - # Call pickles - Pickle-Features -FeatureDirectory $FeatureDirectory ` - -OutputDirectory $OutputDirectory ` - -DocumentationFormat $DocumentationFormat ` - -SystemUnderTestName $SystemUnderTestName ` - -SystemUnderTestVersion $SystemUnderTestVersion ` - -TestResultsFormat $TestResultsFormat ` - -TestResultsFile $TestResultsFile - - # Call pickles with experimental features - Pickle-Features -FeatureDirectory $FeatureDirectory ` - -OutputDirectory $OutputDirectory ` - -DocumentationFormat $DocumentationFormat ` - -SystemUnderTestName $SystemUnderTestName ` - -SystemUnderTestVersion $SystemUnderTestVersion ` - -TestResultsFormat $TestResultsFormat ` - -TestResultsFile $TestResultsFile ` - -IncludeExperimentalFeatures - } - - exit 0 -} -Catch -{ - exit 1 -} diff --git a/testRunnerCmd.cmd b/testRunnerCmd.cmd deleted file mode 100644 index e3c9ffade..000000000 --- a/testRunnerCmd.cmd +++ /dev/null @@ -1,13 +0,0 @@ -FOR %%A IN (Html Dhtml Word Excel JSON Cucumber Markdown) DO ( -.\deploy\nuget\packages\Pickles.CommandLine.%1\tools\Pickles.exe -f=.\src\Pickles\Examples\ -o=.\Output\%%A\ --sn=Pickles --sv=%1 --df=%%A -.\deploy\nuget\packages\Pickles.CommandLine.%1\tools\Pickles.exe -f=.\src\Pickles\Examples\ -o=.\Output\%%A\ --sn=Pickles --sv=%1 --df=%%A -exp -if errorlevel 1 exit /b 1 -) - -FOR %%A IN (Html Dhtml Word Excel JSON Cucumber Markdown) DO ( -.\deploy\chocolatey\packages\Pickles.%1\tools\Pickles.exe -f=.\src\Pickles\Examples\ -o=.\Output\%%A\ --sn=Pickles --sv=%1 --df=%%A -.\deploy\chocolatey\packages\Pickles.%1\tools\Pickles.exe -f=.\src\Pickles\Examples\ -o=.\Output\%%A\ --sn=Pickles --sv=%1 --df=%%A -exp -if errorlevel 1 exit /b 1 -) - -exit /b 0 diff --git a/testRunnerMsBuild.cmd b/testRunnerMsBuild.cmd deleted file mode 100644 index 3a8dce95c..000000000 --- a/testRunnerMsBuild.cmd +++ /dev/null @@ -1,4 +0,0 @@ -"\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" testOutput.proj /p:Version=%1 /p:ShouldIncludeExperimentalFeatures=false -"\Program Files (x86)\MSBuild\14.0\Bin\MSBuild.exe" testOutput.proj /p:Version=%1 /p:ShouldIncludeExperimentalFeatures=true -if errorlevel 1 exit /b 1 -exit /b 0 diff --git a/testRunnerPowerShell.cmd b/testRunnerPowerShell.cmd deleted file mode 100644 index c380bf045..000000000 --- a/testRunnerPowerShell.cmd +++ /dev/null @@ -1,4 +0,0 @@ -powershell.exe -executionpolicy bypass -nologo -noprofile -command "& { .\testOutput.ps1 %1; exit $LastExitCode}" - -if errorlevel 1 exit /b 1 -exit /b 0