Date: 2005-01-28T08:06:43 Editor: MichaelBouschen Wiki: Apache JDO Wiki Page: TestRunner URL: http://wiki.apache.org/jdo/TestRunner
Added section about test runner and identity setting Change Log: ------------------------------------------------------------------------------ @@ -21,3 +21,13 @@ *Only a small subset of tests, some of those for chapter 18, must be run with multiple mapping files and multiple test data sets (true?) This may indicate that security and identity should be handled differently than mapping and data. + +== Test Runner and Identity Setting == + +Today the JDOTCK enhances the persistence capable and persistence aware classes into its own directory called enhanced. The current set of JDO metadata files is copied to a directory called metadata. These two directories are in the beginning of the classpath to make sure that we always find the enhanced version of the pc class. Under tests we have different metadata files for application identity (xxx.jdo.a) and datastore identity (xxx.jdo.d). The targets useapplicationidentity and usedatastoreidentity copy the metadata files into the metadata directory and skips the suffix .a or .d. When switching from one identity setting to another you need to clean the enhanced classes, copy the metadata and enhance the pc classes. + +This does not support easy switching the identity setting. The idea is to keep the enhanced class files for application and datastore identity in separate directories together with their metadata. During JDOTCK setup we would enhance for both identity types and keep the result in separate directories. Then configuring the identity setting for a test class (or a list of test classes) would be setting the correct classpath for the test run. + +Open questions: + *How about nondurable identity? + *What happens if the JDO implementation under test does support allication or datastore identity? Would it help to have a build property that specifies with identity types are supported?
