This Confluence has been LDAP enabled, if you are an ASF Committer, please use your LDAP Credentials to login. Any problems file an INFRA jira ticket please.

Child pages
  • Moving integration tests closer to the code they test

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Currently we have integration tests (ITs) defined in the org.apache.sling.launchpad.tests module, and also some ITs split amongst various modules - Sightly Testing and Models ITs are some examples.

Having tests close to the code is very good as the feedback cycle is very short and we don't risk missing issues until after a release is done. However, having tests grouped in a single module is effective as well - we're using it to test Sling on multiple JVMs quite easily. The question now is whether we can have the best of both worlds - tests living next to the code but also executed centrally in a single global IT job.

...

The proposal would see the tests moved to each bundle in the src/maintest/it module and executed for each module on mvn verify. These tests would then also be collected and launched in the org.apache.sling.launchpad.testing module.

...