[Ironruby-core] Toward MSpec
jdeville at microsoft.com
Fri May 16 23:24:19 EDT 2008
I've actually already got Optparse and MSpec working. That's the new spec runner that I'm almost ready to commit. I sent it through our internal checkin troll tonight, and if all goes well I will send a code review first thing Monday if not sooner.
I would like to see your catch parse implementation and any other patches to the mspec runner you have.
From: ironruby-core-bounces at rubyforge.org [ironruby-core-bounces at rubyforge.org] On Behalf Of Michael Letterle [michael.letterle at gmail.com]
Sent: Friday, May 16, 2008 3:15 PM
To: ironruby-core at rubyforge.org
Subject: Re: [Ironruby-core] Toward MSpec
I made it this far :)
C:\Mike\VS08Proj\IronRuby\trunk\build\debug>ir -D "c:\Mike\Dev\rubyspec\mspec\bin\mspec" -h
mspec [COMMAND] [options] (FILE|DIRECTORY|GLOB)+
The mspec command sets up and invokes the sub-commands
(see below) to enable, for instance, running the specs
with different implementations like ruby, jruby, rbx, etc.
I produced a pretty naive implementation of catch/throw that seems pretty functional for the moment, I think the sticking point now is regex's actually..
On Fri, May 16, 2008 at 4:59 PM, Michael Letterle <michael.letterle at gmail.com<mailto:michael.letterle at gmail.com>> wrote:
Just the end of the week update. I haven't been as active these last few months due to Cleveland Day of .NET planning, but that's this Saturday so hopefully soon I can get back in full swing. Right now I'm playing with getting MSpec (the RubySpec runner), running under IronRuby. The major hurdle right now seems to be that catch/throw isn't implemented. Bug #19888 was also an issue, which I submitted a patch for today.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ironruby-core