Community
Participate
Working Groups
Our testcases pretty much all usr "/test1" or "/res1" or some variation thereof. In preparation of a patch to address the Bugzilla about improving test performance (which I can't find right now), I'd like to introduce a method AbstractCDOTest.getResourcePath(String resourceName) that creates a resource path that is unique to the test method. This will isolate the tests at the resource level, and will make it easier to reuse an existing store. Patch coming in a minute.
Created attachment 188975 [details] Patch A This patch contains only the method I want to add to AbstractCDOTest. Later today I'll attach part B, which will actually put this method to work in pretty much all cases we have. Hence, part B will be large, but very trivial, mostly a sed 's/x/y/' job replacing stuff like "/test1" with getResourcePath("/test1").
Created attachment 188977 [details] Patch B This puts the method added in 'Patch A' to use in all normal test cases (i.e. non-DB).
Note: the changes in patch B are almost all trivial, the only exceptions being a small number of assertions where I had to raise the number of expected objects by +1, because using a test-specific resource path creates a top-level ResourceFolder with the test name.
Created attachment 188986 [details] Patch (all in one)
Created attachment 189013 [details] Patch v4 - adjusted to HEAD
Committed to trunk, rev. 7086 Not resolving yet, I'll provide a similar patch for the DB test classes today.
Created attachment 189070 [details] Patch for DB tests
Created attachment 189160 [details] Patch for DB tests v2
Committed to trunk, rev. 7180
Available in R20110608-1407