Frequently Asked Questions

  1. Why is this plugin called the shitty-maven-plugin?
  1. My tests require some kinda complicated setup before they will run correctly. How should I handle this?
  2. How can I easily validate that my test has actually done what it should have?
Why is this plugin called the shitty-maven-plugin?

Well, there is no really good reason for it... I spent a while trying to think up a clever name, and eventually (maybe after a few beers) started thinking of acronym names and I quickly came up with SHITTY... because IMO this plugin is really super helpful for all of my integration testing needs, so eh... why not. It does make me giggle a little each time I talk about the shitty-maven-plugin too, which is a side bonus ;-)

[top]
My tests require some kinda complicated setup before they will run correctly. How should I handle this?

If you've got a bunch of complicated stuff to create for your tests then you probably want to look at using a setup.groovy script to perform some pre-test execution setup logic.

[top]
How can I easily validate that my test has actually done what it should have?

The easiest way to validate test results is to use a validate.groovy script to perform some post-test execution validation logic.

[top]