diff --git a/.gitignore b/.gitignore
index 6780768b2..58c1435cb 100644
--- a/.gitignore
+++ b/.gitignore
@@ -97,3 +97,4 @@ node_modules/
#include output docs
!docs/Output/
+src/Pickles/.vs/config/applicationhost.config
diff --git a/CHANGELOG.md b/CHANGELOG.md
index faef42fc1..2b41a831a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -14,6 +14,13 @@ 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).
+## [2.10.0] - 2016-10-22
+
+### Changed
+
+- Enable Pickles to with cultures in the language setting ([308](https://github.com/picklesdoc/pickles/pull/308)) (by [@dirkrombauts](https://github.com/dirkrombauts))
+- Improve Markdown Parsing to Reduce Unintended Block Quotes ([302](https://github.com/picklesdoc/pickles/pull/302)) (by [@dirkrombauts](https://github.com/dirkrombauts))
+
## [2.9.0] - 2016-10-07
### Changed
diff --git a/DeployArtifacts.cmd b/DeployArtifacts.cmd
index aae3b8997..aad36f1f7 100644
--- a/DeployArtifacts.cmd
+++ b/DeployArtifacts.cmd
@@ -1,4 +1,4 @@
@ECHO OFF
-call DeployOutput.cmd %1
+REM call DeployOutput.cmd %1
call DeployToChocolatey.cmd %1
call DeployToNuget.cmd %1
diff --git a/build.bat b/build.bat
index 977b1bb76..50d4fe636 100644
--- a/build.bat
+++ b/build.bat
@@ -1,5 +1,5 @@
@echo off
-set "picklesVersion=2.9.0"
+set "picklesVersion=2.10.0"
cls
diff --git a/build.fsx b/build.fsx
index 4baf7c332..ca05843fd 100644
--- a/build.fsx
+++ b/build.fsx
@@ -69,6 +69,36 @@ Target "BuildTest.TestFrameworks" (fun _ ->
|> 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: "
+)
+
let createZip (packageType : string) =
!! (buildDir + "/" + packageType + "/*.*") -- "*.zip"
|> Zip (buildDir + packageType) (deployDir + "Pickles-" + packageType + "-" + version + ".zip")
@@ -94,6 +124,11 @@ Target "Default" (fun _ ->
==> "BuildGui"
==> "BuildTest"
==> "BuildTest.TestFrameworks"
+ ==> "BuildTest.DocumentationBuilders.Dhtml"
+ ==> "BuildTest.DocumentationBuilders.Excel"
+ ==> "BuildTest.DocumentationBuilders.Html"
+ ==> "BuildTest.DocumentationBuilders.Json"
+ ==> "BuildTest.DocumentationBuilders.Word"
==> "Zip"
==> "Default"
diff --git a/chocolatey.fsx b/chocolatey.fsx
index f1a2ab5a6..dd1dc302e 100644
--- a/chocolatey.fsx
+++ b/chocolatey.fsx
@@ -30,6 +30,11 @@ Target "CreatePackage CMD" (fun _ ->
cmdDir + "PicklesDoc.Pickles.Library.dll";
cmdDir + "PicklesDoc.Pickles.ObjectModel.dll";
cmdDir + "PicklesDoc.Pickles.TestFrameworks.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 + "System.IO.Abstractions.dll";
cmdDir + "FeatureSwitcher.dll";
cmdDir + "Strike.Jint.dll";
@@ -68,6 +73,11 @@ Target "CreatePackage GUI" (fun _ ->
guiDir + "PicklesDoc.Pickles.Library.dll";
guiDir + "PicklesDoc.Pickles.ObjectModel.dll";
guiDir + "PicklesDoc.Pickles.TestFrameworks.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 + "System.IO.Abstractions.dll";
guiDir + "FeatureSwitcher.dll";
guiDir + "Strike.Jint.dll";
diff --git a/chocolatey/pickles.nuspec b/chocolatey/pickles.nuspec
index fe3b75be7..cf241ad87 100644
--- a/chocolatey/pickles.nuspec
+++ b/chocolatey/pickles.nuspec
@@ -47,6 +47,11 @@ Optionally, *Pickles* can **integrate test results**, so that your stakeholders
+
+
+
+
+
diff --git a/chocolatey/picklesui.nuspec b/chocolatey/picklesui.nuspec
index 4d77ba2f2..a6e498e53 100644
--- a/chocolatey/picklesui.nuspec
+++ b/chocolatey/picklesui.nuspec
@@ -54,6 +54,11 @@ Optionally, *Pickles* can **integrate test results**, so that your stakeholders
+
+
+
+
+
diff --git a/docs/Output/Dhtml/pickledFeatures.js b/docs/Output/Dhtml/pickledFeatures.js
index 6f1e0392d..38dd41e29 100644
--- a/docs/Output/Dhtml/pickledFeatures.js
+++ b/docs/Output/Dhtml/pickledFeatures.js
@@ -4,7 +4,7 @@ jsonPWrapper ({
"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 \r\nAs a SpecFlow evangelist \r\nI want to show that basic syntax\r\n\r\n![Test Image](test.jpg)",
"FeatureElements": [
{
"Name": "Simple GWT",
@@ -109,7 +109,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\01TestRunner\\TestRunnerIsNotImportant.feature",
"Feature": {
"Name": "The test runner is not (very) important",
- "Description": "\tIn order to show that the test runner is just for the autogenerated stuff in SpecFlow \r\n\tAs a SpecFlow evanglist \r\n\tI 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 \r\nAs a SpecFlow evanglist \r\nI want to be able to call my steps in the same manner inspite of the testrunner configured",
"FeatureElements": [
{
"Name": "A couple of simple steps",
@@ -160,7 +160,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\02TagsAndHooks\\Hooks.feature",
"Feature": {
"Name": "Addition",
- "Description": "\tIn order to explain the order in which hooks are run\r\n\tAs a SpecFlow evanglist\r\n\tI 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 \r\nAs a SpecFlow evanglist \r\nI wan to be able to hook into pre and post conditions in SpecFlow",
"FeatureElements": [
{
"Name": "Hooking into pre conditions for Test Runs in SpecFlow",
@@ -308,7 +308,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\02TagsAndHooks\\TagDemo.feature",
"Feature": {
"Name": "Tag demonstrator",
- "Description": "\tIn order to show the capabilities of tags in SpecFlow\r\n\tAs a SpecFlow evanglist\r\n\tI want to write scenarios that has tags and show their usage in code",
+ "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",
"FeatureElements": [
{
"Name": "Ignored scenario",
@@ -512,7 +512,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\03ScenarioOutline\\ScenarioOutline.feature",
"Feature": {
"Name": "Scenario outline",
- "Description": "\tIn order to not have to type the same scenario over and over\r\n\tAs a SpecFlow evangelist\r\n\tI want to show how to use ScenarioOutline",
+ "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",
"FeatureElements": [
{
"Examples": [
@@ -716,7 +716,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\031ScenarioContext\\ScenarioContext.feature",
"Feature": {
"Name": "Scenario Context features",
- "Description": "\tIn order to show how to use ScenarioContext\r\n\tAs a SpecFlow evangelist\r\n\tI want to write some simple scenarios with data in ScenarioContext",
+ "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",
"FeatureElements": [
{
"Name": "Store and retrive Person Marcus from ScenarioContext",
@@ -900,7 +900,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\032FeatureContext\\FeatureContextFeatures.feature",
"Feature": {
"Name": "FeatureContext features",
- "Description": "\tIn order to show how to use FeatureContext\r\n\tAs a SpecFlow evangelist\r\n\tI want to write some simple scenarios with data in FeatureContext",
+ "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",
"FeatureElements": [
{
"Name": "Store and retrive Person Marcus from FeatureContext Current",
@@ -1001,7 +1001,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\04Background\\BackgroundFeature.feature",
"Feature": {
"Name": "Show the use of background",
- "Description": "\tIn order to show how to use the Background keyword of Gherkin\r\n\tAs a SpecFlow evanglist\r\n\tI 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 \r\nAs a SpecFlow evanglist \r\nI want to show that background steps are called before any scenario step",
"FeatureElements": [
{
"Name": "Add 1 to the sum",
@@ -1096,7 +1096,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\05TablesAndAssist\\TableScenario.feature",
"Feature": {
"Name": "Showing table usage",
- "Description": "\tIn order to show how to use tables\r\n\tAs a SpecFlow evanglist\r\n\tI want to write some simple scenarios that uses tables tables",
+ "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",
"FeatureElements": [
{
"Name": "Using tables",
@@ -1425,7 +1425,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\06CompareToAssist\\CompareTo.feature",
"Feature": {
"Name": "Show the compare to feature",
- "Description": "\tIn order to show the compare to features of SpecFlow Assist\r\n\tAs a SpecFlow evanglist\r\n\tI want to show how the different versions of compareTo works",
+ "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",
"FeatureElements": [
{
"Name": "CompareToInstance",
@@ -1663,10 +1663,10 @@ jsonPWrapper ({
}
},
{
- "RelativeFolder": "Features\\07Svenska\\Svenska.feature",
+ "RelativeFolder": "Features\\07Localization\\Svenska.feature",
"Feature": {
- "Name": "Summering",
- "Description": "\tFör att slippa att göra dumma fel\r\n\tSom räknare\r\n\tVill jag kunna lägga summera",
+ "Name": "Svenska - Summering",
+ "Description": "För att slippa att göra dumma fel \r\nSom räknare \r\nVill jag kunna lägga summera",
"FeatureElements": [
{
"Name": "Summera 5 och 7 ska vara 12",
@@ -1720,11 +1720,90 @@ jsonPWrapper ({
"WasSuccessful": false
}
},
+ {
+ "RelativeFolder": "Features\\07Localization\\Vlaams.feature",
+ "Feature": {
+ "Name": "Test de Cultuur in het Vlaams",
+ "Description": "",
+ "FeatureElements": [
+ {
+ "Name": "Het Scenario",
+ "Slug": "het-scenario",
+ "Description": "",
+ "Steps": [
+ {
+ "Keyword": "Given",
+ "NativeKeyword": "Stel ",
+ "Name": "dat ik 50 ingeef",
+ "StepComments": [],
+ "AfterLastStepComments": []
+ },
+ {
+ "Keyword": "And",
+ "NativeKeyword": "En ",
+ "Name": "dat ik 70 ingeef",
+ "StepComments": [],
+ "AfterLastStepComments": []
+ },
+ {
+ "Keyword": "And",
+ "NativeKeyword": "And ",
+ "Name": "also this step",
+ "StepComments": [],
+ "AfterLastStepComments": []
+ },
+ {
+ "Keyword": "When",
+ "NativeKeyword": "Als ",
+ "Name": "ik plus druk",
+ "StepComments": [],
+ "AfterLastStepComments": []
+ },
+ {
+ "Keyword": "Then",
+ "NativeKeyword": "Dan ",
+ "Name": "moet het resultaat 120 zijn",
+ "StepComments": [],
+ "AfterLastStepComments": []
+ },
+ {
+ "Keyword": "And",
+ "NativeKeyword": "And ",
+ "Name": "that the number 4 is even",
+ "StepComments": [],
+ "AfterLastStepComments": []
+ },
+ {
+ "Keyword": "But",
+ "NativeKeyword": "But ",
+ "Name": "the number 3 is odd",
+ "StepComments": [],
+ "AfterLastStepComments": []
+ }
+ ],
+ "Tags": [],
+ "Result": {
+ "WasExecuted": false,
+ "WasSuccessful": false
+ }
+ }
+ ],
+ "Result": {
+ "WasExecuted": false,
+ "WasSuccessful": false
+ },
+ "Tags": []
+ },
+ "Result": {
+ "WasExecuted": false,
+ "WasSuccessful": false
+ }
+ },
{
"RelativeFolder": "Features\\08AttributeOverloading\\AttributeOverloading.feature",
"Feature": {
"Name": "Attribute overloading",
- "Description": "\tIn order to show that steps can be used with multiple attributes\r\n\tAs a SpecFlow Evangelist\r\n\tI 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 \r\nAs a SpecFlow Evangelist \r\nI want to show that similar attributes can be applied to the same step definition",
"FeatureElements": [
{
"Name": "Checking number for evenness",
@@ -1803,7 +1882,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\09CallingStepsFromSteps\\CallingStepsFromSteps.feature",
"Feature": {
"Name": "Calling Steps from StepDefinitions",
- "Description": "\tIn order to create steps of a higher abstraction\r\n\tAs a SpecFlow evangelist\r\n\tI want reuse other steps in my step definitions",
+ "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",
"FeatureElements": [
{
"Name": "Log in",
@@ -1894,7 +1973,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\10StepTransformation\\StepTransformation.feature",
"Feature": {
"Name": "Step Argument Transformations",
- "Description": "\tIn order to reduce the amount of code and repetitive tasks in my steps\r\n\tAs a SpecFlow evanglist\r\n\tI want to define reusable transformations for my step arguments",
+ "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",
"FeatureElements": [
{
"Name": "Steps with non-string arguments",
@@ -1945,7 +2024,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\11ContextInjection\\ContextInjection.feature",
"Feature": {
"Name": "Injecting context into step specifications",
- "Description": "\tIn order to don't have to rely on the global shared state\r\n\t\tand to be able to define the contexts required for each scenario.\r\n\tAs a SpecFlow Evanglist\r\n\tI would like to have the system automatically inject an instance of any class as \r\n\t\tdefined in the constructor of a step file",
+ "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",
"FeatureElements": [
{
"Name": "Feature with no context",
@@ -2107,7 +2186,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\12NestedFolders\\ChildFolder\\ChildChildFolder\\NestedFolderExample.feature",
"Feature": {
"Name": "Nested Folder Example",
- "Description": "\tIn order to test nested folder output\r\n\tAs a silly contributer\r\n\tI want to create an example of something several folders deep",
+ "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",
"FeatureElements": [
{
"Name": "Nested - Add two numbers",
@@ -2167,7 +2246,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\13MultilineText\\MultilineFeatureExample.feature",
"Feature": {
"Name": "Multiline Feature Example",
- "Description": "\tIn order capture this particular Gherkin feature\r\n\tAs a Pickles contributer\r\n\tI want to demonstrate an example of using multiline text in a Scenario",
+ "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",
"FeatureElements": [
{
"Name": "Mutliline Output",
@@ -2221,7 +2300,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\14MarkdownExample\\MarkdownExamples.feature",
"Feature": {
"Name": "Sample Markdown Feature",
- "Description": "Header 1\r\n========\r\n\r\nHeader 2\r\n--------\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\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)",
"FeatureElements": [
{
"Name": "Sample Markdown Scenario Example",
@@ -2253,7 +2332,7 @@ jsonPWrapper ({
"Examples": [
{
"Name": "",
- "Description": "This __message__ is important too and is for an *Example* table.",
+ "Description": "\tThis __message__ is important too and is for an *Example* table.",
"TableArgument": {
"HeaderRow": [
"test",
@@ -2336,7 +2415,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\15Pickles\\InteractiveDHTMLView.feature",
"Feature": {
"Name": "Interactive DHTML View",
- "Description": "\tIn order to increase stakeholder engagement with pickled specs\r\n\tAs a SpecFlow evangelist \r\n\tI want to adjust the level of detail in the DHTML view to suit my audience\r\n\tSo that I do not overwhelm them.",
+ "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.",
"FeatureElements": [
{
"Name": "Scenario with large data table",
@@ -2483,7 +2562,7 @@ jsonPWrapper ({
"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 \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}.$$",
"FeatureElements": [
{
"Name": "Add two numbers",
@@ -2677,7 +2756,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\Trigonometry.feature",
"Feature": {
"Name": "Trigonometry",
- "Description": "\tIn order to avoid perform more advanced calculations\r\n\tAs a math idiot\r\n\tI want to be able to use trigonometric functions",
+ "Description": "In order to avoid perform more advanced calculations \r\nAs a math idiot \r\nI want to be able to use trigonometric functions",
"FeatureElements": [
{
"Name": "Sine",
@@ -2803,7 +2882,7 @@ jsonPWrapper ({
"RelativeFolder": "Features\\Workflow\\ClearingScreen.feature",
"Feature": {
"Name": "Clearing Screen",
- "Description": "\tIn order to restart a new set of calculations\r\n\tAs a math idiot\r\n\tI want to be able to clear the 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",
"FeatureElements": [
{
"Name": "Clear the screen",
@@ -2986,10 +3065,10 @@ jsonPWrapper ({
"Folders": [
{
"Folder": "Features",
- "Total": 53,
+ "Total": 54,
"Passing": 0,
"Failing": 0,
- "Inconclusive": 53
+ "Inconclusive": 54
}
],
"NotTestedFolders": [
@@ -3002,21 +3081,21 @@ jsonPWrapper ({
}
],
"Scenarios": {
- "Total": 53,
+ "Total": 54,
"Passing": 0,
"Failing": 0,
- "Inconclusive": 53
+ "Inconclusive": 54
},
"Features": {
- "Total": 22,
+ "Total": 23,
"Passing": 0,
"Failing": 0,
- "Inconclusive": 22
+ "Inconclusive": 23
}
},
"Configuration": {
"SutName": "Pickles",
- "SutVersion": "2.8.3",
- "GeneratedOn": "28 September 2016 10:45:41"
+ "SutVersion": "2.10.0",
+ "GeneratedOn": "22 Oktober 2016 13:32:31"
}
});
\ No newline at end of file
diff --git a/docs/Output/Excel/features.xlsx b/docs/Output/Excel/features.xlsx
index 73fe93281..a69b643b4 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 b59324823..fba599cdc 100644
--- a/docs/Output/Html/Features/00BasicGherkin/BasicGherkin.html
+++ b/docs/Output/Html/Features/00BasicGherkin/BasicGherkin.html
@@ -132,11 +132,14 @@
@@ -251,9 +254,7 @@
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
@@ -304,9 +305,9 @@
Using And and But