cliinteractively" with running a test "in-proccess". Interactively works without "in-proccess" but that's not a solution because I really need it for using webmock. My question is: should it work? If so I will be trying to do it more.
Which branch should I base my changes on - master?
Yes, please. master is the reference for all PRs.
Great! I think at best would be to have a look at the build logs on AppVeyor first and make sure all existing feature tests are green. A short list of issues I'm aware of.
#to_h. This is partially implemented and needs to be rebased.
whichcommand: Make sure command paths can be resolved - this is related to 2. and should be fixed first.
arubaon Windows if needed
I also added a platform tag to our issued tracker: https://github.com/cucumber/aruba/issues?q=is%3Aissue+is%3Aopen+label%3Aplatform%2Fwindows
@dg-ratiodata Had a quick look at the failing Windows specs.
To fix 2. and 4. I was thinking of re-implementing those commands as Ruby scripts (they are 2 or 3 lines each) to be executed by the specs so that they work in the same way on all platforms.
I believe that 7. should return what Ruby does, so Nil on Windows, and it should be tested.