search

einari / Machine.Specifications.Core

.NET Core version of Machine.Specifications
MIT License
3 stars 1 forks source link

Roadmap and current status? #7

Open ivanz opened 8 years ago

ivanz commented 8 years ago

Hi,

Great to see what you have done here. Is there a roadmap or at least status of what is there, what is missing, what is working and what isn't? e.g. - is mspec in dotnet test supported yet?

einari commented 8 years ago

Sorry for being so slo; vacation time.

dotnet test is not yet supported. Right now it all works by having a regular console app and triggering the discovery mechanism that runs all the tests.

My personal goal with the project is to get to a place where it runs both with the dotnet testtooling, but also inside IDEs - for my sake; Visual Studio Code primarily. I've been a huge fan of TestDriven.NET in regular Visual Studio and want to bring at the very minimum this experience into VSCode for MSpec.

A long term dream would be to enable what WallabyJS does for JavaScript. I have a few ideas on how it can be done and be just as efficient - with the .NET Core runtime and the Roslyn compiler being developed as open sourced, there might be a chance I can get to it. Basically my idea is to continuously compile files being edited and hook into the runtime to evict JITed code so that we can replace it continuously. Of course this requires some deep insight into how Roslyn works with the AST and how the runtime actually works. I'm no sure it would be possible, but I'm willing to give it a try at one point.. :) But for now - first things first; for me - my goal is to become productive in .NET Core and VSCode. The reason for VSCode for myself is that I'm mostly on Macs and Linux boxes these days.