Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Naming your Test

In the past, tests were numbered sequentially (it001,it002, etc). This becomes problematic because it's not always obvious what the issue is related to the test. More importantly, it's hard to create and submit sequential tests via patches because non-committers have no way to reserve the next number. This leads to extra work to apply the patch.

 New tests should be named using the Jira Issue id along with a meaningful name. This name should typically be the subject of the issue or a subset. It should be informative of the issue but not excessively long. Therefore a good name would be: mng1234-groupIdOrderIsBackwards.

This name is typically used in several places of the test: the folder in core-integration-tests/src/test/resources/ that contains the sample project along with the name of the junit class used to invoke the sample project and check the results.

Sample IT Project

A sample project has been created to aid in IT test creation. It can be retrieved using svn hereor viewed with your browser here.

This project has also been converted into an archetype to make it even easier to use. (NOTE: This is currently not deployed -Brianf 8/8/07)

 Using ArchetypeNG To create a sample from the archetype

The maven-archetypeng-plugin is currently a snapshot. You will need to add the snapshot repository to your settings to be able to retreive the plugin and the archetype (when it gets deployed).

           <id>Maven Snapshots</id>

How you should execute for integration test to validate

How to submit your integration test

When you will know your IT has been reviewed

When you will know your IT has been integrated

  • No labels