Amir Rajan
Amir Rajan
Thanks man, I'll give it a shot in a couple of weeks!
Some of the promise libraries out there have an `on_error` callback. so maybe: ``` on_error = (e) => { }; ``` Keep in mind that you can inherit from `nspec`...
I'm fine with adding additional stuff if needed, just wanted show the inheritance technique and see if that would suffice. As long as the wiki entry is updated, I'm good...
There is a `Conventions` concept have baked in NSpec
`System.Diagnostics.Debugger.Launch` or roll your own `Program.cs` console app which is really simple: https://gist.github.com/amirrajan/236cbaafef2c7c2195b47c41cbf9c918#file-program-cs With building your own console app, you'd put the breakpoint in there and run that instead of...
Here's what I've used for the past few years. Basically this detects changes and then fires of rake scripts: ```csharp using System; using System.Collections.Generic; using System.Linq; using System.Text; using System.IO;...
Aside: I'm a glutton for low-fi solutions. CLI and terminal all the things. With regards to running a context by clicking, I'd (personally), prefer some file watcher keep track of...
@warwickfoster looking forward to your VS2017 Enterprise test runner contributions.
@ivan-prodanov dig in and figure it out :-)
> I'm trying to create a useful NUnit wrapper for NSpec. I think @BrainCrumbz is working on a wrapper. That being said, here is how NSpec executes specifications: ``` //types...