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.