You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
//somwhere inside of a custom Program.cs that references both NUnit and NSpecvarbuilder= nspecThingy.TestFinder(someAssembly,(methodInfo)=>{if(nspecThingy.ContainsAttribute<Setup>(methodInfo)){return nspecThingy.Before();}if(nspecThingy.ContainsAttribute<TestMethod>(methodInfo)){return nspecThingy.Context("NUnit Method: "+ methodInfo.Name);}if(nspecThingy.ContainsAttribute<TearDown>(methodInfo)){return nspecThingy.After();}return nspecThingy.Skip();});
specRunner.run(builder, builder2, builder3);
The text was updated successfully, but these errors were encountered:
That looks quite like some kind of adapter from NUnit to NSpec 😺 . Might be interesting.
Going from the top of my head, are those the only test attributes we should look for within NUnit? Looking at doc page, there might some more to look at: TestFixture, Test. And when pushing forward with adaptation: OneTimeSetUp, OneTimeTearDown, SetUpFixture, TearDownFixture. Then theories as well, to somehow map them to parameterized tests.
Would be cool if you could do:
The text was updated successfully, but these errors were encountered: