My experience and articles like https://developer.atlassian.com/docs/getting-started/writing-and-running-plugin-tests/create-test-data-and-a-test-fixture suggest that most `atlas-FOO` methods will pull down a minimal set of test data for each product, enough to skip the new product install pages (in memory DB, basic license key, etc)
When you first start the application and load your plugin,
the atlas- commands download the specified <productDataVersion>,
unzip it, and use it to seed the PLUGIN_HOME/target/application/home directory.
However, running `mvn integration-test` is a discouraged practice, because post-integtation-test phase is never called, and might have important tear-down instructions bound to it. Instead you should run `mvn verify` which runs IT and post-IT lifecycle phases.
NOTE: when running integration tests, you should invoke Maven with the (shorter to type too) mvn verify rather than trying to invoke the integration-test phase directly, as otherwise the post-integration-test phase will not be executed.
However it seems for confluence specifically that running `atlas-mvn verify` does not load any test data, and my ITs are blocked at a "select database type" page.
This is only an issue for confluence, all other products seem to load typical plugin defaults.
JIRA loads fine
Confluence wants full setup
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG