Introduce automated tests for the Gradle and Maven plugins

[sbrannen]

In order to avoid bugs such as #44, the native build tools project should introduce automated tests for the Gradle and Maven plugins.

This can be achieved in various ways.

For Gradle, one option may be to use the Gradle TestKit.

Another option is the approach taken by the JUnit team in the platform-tooling-support-tests project, where individual demo projects are tested in isolation.

[lazar-mitrovic]

Another option is the approach taken by the JUnit team in the platform-tooling-support-tests project, where individual demo projects are tested in isolation.

We are already doing a similar thing here, so easiest fix might be to populate examples directory with multiple examples for each supported build tool.

[sbrannen]

We are already doing a similar thing here, so easiest fix might be to populate examples directory with multiple examples for each supported build tool.

Does that actually perform some form of verification of the results (assertions, etc.)? If so, what is the error reporting like?

Or does it just run something and hope there's no bad exit code of the executed command?

[lazar-mitrovic]

Fixed by #87