Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
MODE-670 The modeshape-jcr-tck test case classes were being run in an arbitrary order (however JUnit/Surefire determines them), and the Level 1 TCK unit tests were being run after some of the other TCK unit tests that modified the repository. When some of those tests fail, apparently the repository is not being returned to its original state, and thus there is missing content required by the Level 1 TCK tests (which are all read-only). The fix was to add a static method to ModeShapeRepositoryStub that will force the JcrEngine to be rebuilt, and then to add a test case to each of the test suites that calls this method.

Normally, the org.apache.jackrabbit.test.JCRTestSuite runs the Level 1 tests first, followed by the Level 2 tests, the query tests, the node type tests, the lock tests, the version tests, and then the observation tests. So the order that the modeshape-jcr-tck tests are run does not reflect the actual TCK test order, so forcing the recreation of the engine IMO works fine.

Really, the 'correct' way to fix this is to create a single TestSuite that adds the appropriate tests in the appropriate order (e.g., org.apache.jackrabbit.test.JCRTestSuite class). However, we want to keep them separated and grouped by feature so that it is more obvious which test failures are for which (optional) features.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@1668 76366958-4244-0410-ad5e-bbfabb93f86b

    • -0
    • +35
    ./java/org/modeshape/jcr/ResetRepositoryInstanceTest.java
  1. … 4 more files in changeset.
MODE-660 Minor corrections to the way certain criteria are created in the Lucene Search Engine. Also moved the ElementTest from the Level 1 TCK unit tests to be Level 2, since it changes the content (which is not part of a Level 1 repository) and therefore causes failures with the integration test that uses the file system connector.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@1639 76366958-4244-0410-ad5e-bbfabb93f86b

  1. … 8 more files in changeset.
DNA-580 Rebranded all of the codebase, changing from 'JBoss DNA' to 'ModeShape'. For details about the procedure, see DNA-580. The rebranding is not yet complete with this commit, but at this point all modules have been renamed, all package names have been adjusted, all references to 'DNA' (in the various forms) have been changed, and all of the unit tests and integration tests do pass. The remaining work involves fixing a small number of issues (table names used by the JPA connector models, one TCK failure that has been commented out that apparently was uncovered by the node type names and prefixes were changes) that still have to be fixed. Also, I've not verified much of the Getting Started or Reference Guides (though these were changed automatically by my scripts). In short, there still is work to do before we release something.

git-svn-id: https://svn.jboss.org/repos/modeshape/trunk@1596 76366958-4244-0410-ad5e-bbfabb93f86b

    • -0
    • +122
    ./java/org/modeshape/jcr/Jsr170LevelOneTckTest.java
    • -0
    • +196
    ./java/org/modeshape/jcr/Jsr170LevelTwoTckTest.java
    • -0
    • +67
    ./java/org/modeshape/jcr/Jsr170OptionalLockingTckTest.java
    • -0
    • +67
    ./java/org/modeshape/jcr/Jsr170OptionalObservationTckTest.java
    • -0
    • +82
    ./java/org/modeshape/jcr/Jsr170OptionalSqlQueryTckTest.java
    • -0
    • +67
    ./java/org/modeshape/jcr/Jsr170OptionalVersionTckTest.java
    • -0
    • +12
    ./resources/log4j.properties
  1. … 3498 more files in changeset.