BrainCrumbz
BrainCrumbz
We created a Visual Studio Test Adapter for NSpec, [NSpec.VsAdapter](https://github.com/BrainCrumbz/NSpec.VsAdapter), so that a developer can list, group, select and launch NSpec specs directly from within Visual Studio. [Here's](https://raw.githubusercontent.com/BrainCrumbz/NSpec.VsAdapter/master/src/NSpec.VsAdapter/NSpec.VsAdapter.Vsix/Assets/Preview/NSpecVsAdapterPreview200x200.png) a (tiny)...
In currently avaliable package version, 1.0.4, `ContextRunner` still requires a `ContextBuilder` ([code](https://github.com/mattflo/NSpec/blob/v1.0.4/NSpec/Domain/ContextRunner.cs)). But since this (unpublished ?) [commit](https://github.com/mattflo/NSpec/commit/ccc5af0a78ebb55492f52762cab14528996c288e) that dependency has been removed. The reason seemed to be that the...
Yep, PR just merged
@amirrajan I was going to close this issue for inactivity, but then there's quite a point in being able to run NSpec through a single spec/test-case, instead of a whole...
Not sure how such codification of entire test structure would help, our main concern was to provide an API into nspec to run one or more selected `it`s, while now...
I don't think I knew that there's a `Tag` for every `it`, while I was aware there's one for every nspec-derived class. It must be memory then :)
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...
Hi @sschmid , sorry for late reply. No idea about this, never fiddled with Xamarin Studio. Have you got any pointer on how does integration work with this platform? Also,...
Well said, didn't thought about that. First assumption was "that is a windows command prompt". Then it might be enough to start prompt with `PM>` and yes, anyway, mention that...
#166 also introduced `PM>` prompt, so that is sorted. For one thing though, the console does not load that, at least on Windows Visual Studio 2015, with a .NET Core...