It’s slowly starting to appear that what Merb needs is to test the correctness of its generators, to ensure that no exceptions are raised during the generation process, as well as to ensure that all the files they create are accurately named and contain allowed Ruby syntax. How on earth you’d test this sort of thing is beyond me at the moment because I don’t fully understand how RubiGen works, or if that sort of testing should be delegated to RubiGen itself. Whatever the case, something needs to change.
-
About
Ardekantur writes about Ruby, Linux, .NET, and various other fun projects. -
Tags
bookmarking bookmarks bulletin cli command line datamapper delicious design edge merb geek code git github gui hacker key haml incomplete software interfaces iociem leopard links linux lookupfile mac manpages marsedit Merb meta nerdtree netnewswire newsgator opera pixelmator rails rspec rss ruby software spaces supertags taskomaly tdd testing usability vim yaml