search

joaquimcid / mb-unit

Automatically exported from code.google.com/p/mb-unit
0 stars 0 forks source link

unrecognized legacyUnhandledExceptionPolicy when using SpecFlow with configuration set for mbunit #770

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Install Gallio 
2. Install Specflow
3. Create a test project and add specflow and 
3. Add the following configuration block to an app.config project
  <specFlow>
    <unitTestProvider name="MbUnit" />
    <runtime detectAmbiguousMatches="true"
          stopAtFirstError="false"
          missingOrPendingStepsOutcome="Error" />
  </specFlow>
4. Add specs without implementing steps
5. Run the tests

What is the expected output? What do you see instead?
I expect the test to run and report a failure due to not having implemented 
steps.

What I see instead is: SEE ATTACH1.TXT

Navigating to the c106a2f91c7f3216.tmp.config that is generated in the folder I 
see that mbunit appends to the configuration section of specflow:

SEE ATTACH2.TXT

What version of the product are you using? On what operating system?
Gallio 3.1, 3.2, Windows 7 x64

Please provide any additional information below.
Running tests through both TestDriven.net and MsTest Runner.

Original issue reported on code.google.com by Indigo0086 on 14 Nov 2010 at 9:03

Attachments:

GoogleCodeExporter commented 8 years ago 
Correction: The configuration should be 
  <section name="specFlow"
           type="TechTalk.SpecFlow.Configuration.ConfigurationSectionHandler, TechTalk.SpecFlow" />

  <specFlow>
    <unitTestProvider name="MbUnit" />
  </specFlow>

Original comment by Indigo0086 on 14 Nov 2010 at 9:09