On Wed, Nov 18, 2009 at 9:47 AM, <[email protected]> wrote: > This is no problem .. I know groovy and ant.. The problem is to justify in > a big project the inclusion of one more technology just to supply a test > feature :) Actually, the maven plugin is working here - it do the test, I > can see the results in the console, but: the report doesn't work .. I don't > know why.. >
Including WebTest might indeed be an extra dependency, which you prefer to avoid. But on the other hand, I think you should be pragmatic enough: doesn't the added value of easy integration tests outweights the "trouble" of adding an extra "technology"? On other words, what alternative do you have? Don't write integration tests? Write your own framework from scratch? > I can share my test project if you want.. It is ~10Kb, tell me if I can > post her ein the list.. (and if you think it make sense at all) > I haven't used WebTest in Maven yet, but I run rather out of the box using Ant for me personally. Maybe you can give more details about your setup and summarize what's going wrong in Maven. Or try to run Maven verbosely with the "-X" parameter. You claim that the tests are executed, so I guess it's just some integration issue between Maven and WebTest. It may be caused by incompatible Maven plugins, which can be rather tricky to untangle. But usually, such problems give you some error message, and not silently stop.
