[MacRuby-devel] Xcode Project Template with Testing Baked In

[Eloy Duran]

Hey Matt,

> hmm for once I don't fully agree with Eloy :)

I'm sure we've disagreed before ;-)

> But, on the long run this should all move to Rucola to provide one  
> piece that pulls it all together.
>
> It's a small details but I think we do need a solid testing  
> framework in XCode too. Not everyone will use Rucola and therefore  
> offering a great test solution for both tools would be great.

Rucola has always been about allowing Ruby devs _and_ xcode users to  
use it without knowing the difference. Also, Rucola/HotCocoa will come  
with MacRuby, so they can use it without knowing so.

> I don't think Eloy was against such thing but I thought it was  
> important to mention it.

I'm against maintaining duplicate stuff. People should just use the  
code which has been battle tested and has added facilities to make it  
easier, even if they don't know what it is their using in the  
bakcground. Ie, the test helper would just require the test case  
helper, the user doesn't need to know where it actually lives. Adding  
this to the project template makes people think they have to add  
facilities themselves imo.

Eloy

> On Fri, Oct 2, 2009 at 1:18 AM, Eloy Duran <eloy.de.enige at gmail.com>  
> wrote:
> Hi Dylan,
>
>
> So, I've been mucking about with MacRuby lately. It's been fun so  
> far. Thanks to all the devs for this great project.
>
> Welcome!
>
>
> I'm a pretty firm believer in unit testing my Ruby code. I love how  
> Ruby on Rails and similar frameworks nudge you in the right  
> direction by baking in an existing testing infrastructure.
>
> Great, we agree! :)
>
>
> I've got testing pretty much figured out and was wondering if the  
> team would be open to modifying the basic Xcode project template to  
> add unit testing, with a stub test and test_suite file to get  
> started. This would also involve creating a framework for any  
> objective-c code that the user writes so that it can be included in  
> both the .app and the test files.
>
> Well, unfortunately atm it's not that easy. Because we currently  
> can't both run test::unit or minitest properly. I know the  
> test::unit, which is currently in macruby's trunk, works work the  
> greater part, but it's not ideal.
>
> I have been working on this area for a while now, getting a little  
> closer every time. This work is part of Rucola, which at some point  
> will merge with HotCocoa and will provide a classic layout as you  
> are accustomed to by frameworks such as Rails.
>
> At this point, the test framework which we can fully run is Bacon,  
> which is what I'm gonna base the rest of my current work on.  
> However, once we can fully run minitest/test::unit we'll support  
> that as well. More importantly right now is a working mocking and  
> stubbing lib. My choice is Mocha, but MacRuby is not mature enough  
> yet to do all the fancy meta stuff that is needed for this.
>
> So for the time being, I'd say cool let's add it to the project  
> template! But, on the long run this should all move to Rucola to  
> provide one piece that pulls it all together. If you are interested  
> on working on this, please contact me directly. Anyone can do that  
> btw.
>
> Cheers,
> Eloy
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
>
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macosforge.org/pipermail/macruby-devel/attachments/20091002/a00c34d3/attachment-0001.html>