-
Notifications
You must be signed in to change notification settings - Fork 750
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding TestResult-files necessary for ReportingTests. Increasing vers…
…ion number to 1.3.1.
- Loading branch information
jbandi
committed
Jun 20, 2010
1 parent
8d4a8ec
commit f4d6352
Showing
6 changed files
with
98 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Empty file.
33 changes: 33 additions & 0 deletions
33
Tests/ReportingTest.SampleProject/NUnitResult/TestResult.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,33 @@ | ||
***** ReportingTest.SampleProject.FeatureWithFailingScenariosFeature.IgnoredScenario | ||
***** ReportingTest.SampleProject.FeatureWithFailingScenariosFeature.ScenarioWithFailingSteps | ||
Given I have a precondition that is failing | ||
-> error: simulated failure | ||
***** ReportingTest.SampleProject.FeatureWithFailingScenariosFeature.ScenarioWithPendingSteps | ||
Given I have a pending precondition | ||
-> No matching step definition found for the step. Use the following code to create one: | ||
[Binding] | ||
public class StepDefinitions | ||
{ | ||
[Given(@"I have a pending precondition")] | ||
public void GivenIHaveAPendingPrecondition() | ||
{ | ||
ScenarioContext.Current.Pending(); | ||
} | ||
} | ||
|
||
***** ReportingTest.SampleProject.FeatureWithSuccessfulScenariosFeature.FirstSuccessfulScenario | ||
Given I have a precondition that is successful | ||
-> done: StepDefinitions.GivenIHaveAPreconditionThatIs("successful") (0,0s) | ||
When I do something that works | ||
-> done: StepDefinitions.GivenIHaveAPreconditionThatIs("works") (0,0s) | ||
Then I have a postcondition that is successful | ||
-> done: StepDefinitions.GivenIHaveAPreconditionThatIs("successful") (0,0s) | ||
***** ReportingTest.SampleProject.FeatureWithSuccessfulScenariosFeature.SecondSuccessfulScenario | ||
Given I have a precondition that is successful | ||
-> done: StepDefinitions.GivenIHaveAPreconditionThatIs("successful") (0,0s) | ||
And I have a precondition that is successful | ||
-> done: StepDefinitions.GivenIHaveAPreconditionThatIs("successful") (0,0s) | ||
When I do something that works | ||
-> done: StepDefinitions.GivenIHaveAPreconditionThatIs("works") (0,0s) | ||
Then I have a postcondition that is successful | ||
-> done: StepDefinitions.GivenIHaveAPreconditionThatIs("successful") (0,0s) |
61 changes: 61 additions & 0 deletions
61
Tests/ReportingTest.SampleProject/NUnitResult/TestResult.xml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,61 @@ | ||
<?xml version="1.0" encoding="utf-8" standalone="no"?> | ||
<!--This file represents the results of running a test suite--> | ||
<test-results name="bin\Debug\ReportingTest.SampleProject.dll" total="4" errors="0" failures="1" not-run="1" inconclusive="1" ignored="1" skipped="0" invalid="0" date="2010-06-20" time="16:47:13"> | ||
<environment nunit-version="2.5.5.10112" clr-version="2.0.50727.4927" os-version="Microsoft Windows NT 6.1.7600.0" platform="Win32NT" cwd="C:\Users\jba\Dev\Projects\SpecFlow\Tests\ReportingTest.SampleProject" machine-name="TTV-JBA01" user="jba" user-domain="TECHTALK" /> | ||
<culture-info current-culture="de-AT" current-uiculture="en-US" /> | ||
<test-suite type="Assembly" name="bin\Debug\ReportingTest.SampleProject.dll" executed="True" result="Failure" success="False" time="1.085" asserts="0"> | ||
<results> | ||
<test-suite type="Namespace" name="ReportingTest" executed="True" result="Failure" success="False" time="1.076" asserts="0"> | ||
<results> | ||
<test-suite type="Namespace" name="SampleProject" executed="True" result="Failure" success="False" time="1.075" asserts="0"> | ||
<results> | ||
<test-suite type="TestFixture" name="FeatureWithFailingScenariosFeature" description="Feature with failing scenarios" executed="True" result="Failure" success="False" time="1.039" asserts="0"> | ||
<results> | ||
<test-case name="ReportingTest.SampleProject.FeatureWithFailingScenariosFeature.IgnoredScenario" description="Ignored scenario" executed="False" result="Ignored"> | ||
<reason> | ||
<message><![CDATA[]]></message> | ||
</reason> | ||
</test-case> | ||
<test-case name="ReportingTest.SampleProject.FeatureWithFailingScenariosFeature.ScenarioWithFailingSteps" description="Scenario with failing steps" executed="True" result="Failure" success="False" time="0.222" asserts="0"> | ||
<failure> | ||
<message><![CDATA[simulated failure]]></message> | ||
<stack-trace><![CDATA[at ReportingTest.SampleProject.StepDefinitions.GivenIHaveAPreconditionThatIs(String result) in C:\Users\jba\Dev\Projects\SpecFlow\Tests\ReportingTest.SampleProject\StepDefinitions.cs:line 24 | ||
at lambda_method(ExecutionScope , String ) | ||
at TechTalk.SpecFlow.Bindings.MethodBinding.InvokeAction(Object[] arguments, ITestTracer testTracer, TimeSpan& duration) in C:\Users\jba\Dev\Projects\SpecFlow\Runtime\Bindings\StepMethodBinding.cs:line 150 | ||
at TechTalk.SpecFlow.TestRunner.ExecuteStepMatch(BindingMatch match, Object[] arguments) in C:\Users\jba\Dev\Projects\SpecFlow\Runtime\TestRunner.cs:line 406 | ||
at TechTalk.SpecFlow.TestRunner.ExecuteStep(StepArgs stepArgs) in C:\Users\jba\Dev\Projects\SpecFlow\Runtime\TestRunner.cs:line 289 | ||
at TechTalk.SpecFlow.TestRunner.CollectScenarioErrors() in C:\Users\jba\Dev\Projects\SpecFlow\Runtime\TestRunner.cs:line 148 | ||
at ReportingTest.SampleProject.FeatureWithFailingScenariosFeature.ScenarioWithFailingSteps() in c:\Users\jba\Dev\Projects\SpecFlow\Tests\ReportingTest.SampleProject\FeatureWithFailingScenarios.feature:line 14 | ||
]]></stack-trace> | ||
</failure> | ||
</test-case> | ||
<test-case name="ReportingTest.SampleProject.FeatureWithFailingScenariosFeature.ScenarioWithPendingSteps" description="Scenario with pending steps" executed="True" result="Inconclusive" success="False" time="0.106" asserts="0"> | ||
<reason> | ||
<message><![CDATA[No matching step definition found for one or more steps. | ||
[Binding] | ||
public class StepDefinitions | ||
{ | ||
[Given(@"I have a pending precondition")] | ||
public void GivenIHaveAPendingPrecondition() | ||
{ | ||
ScenarioContext.Current.Pending(); | ||
} | ||
} | ||
]]></message> | ||
</reason> | ||
</test-case> | ||
</results> | ||
</test-suite> | ||
<test-suite type="TestFixture" name="FeatureWithSuccessfulScenariosFeature" description="Feature with successful scenarios" executed="True" result="Success" success="True" time="0.030" asserts="0"> | ||
<results> | ||
<test-case name="ReportingTest.SampleProject.FeatureWithSuccessfulScenariosFeature.FirstSuccessfulScenario" description="First successful scenario" executed="True" result="Success" success="True" time="0.023" asserts="0" /> | ||
<test-case name="ReportingTest.SampleProject.FeatureWithSuccessfulScenariosFeature.SecondSuccessfulScenario" description="Second successful scenario" executed="True" result="Success" success="True" time="0.004" asserts="0" /> | ||
</results> | ||
</test-suite> | ||
</results> | ||
</test-suite> | ||
</results> | ||
</test-suite> | ||
</results> | ||
</test-suite> | ||
</test-results> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters