With ref to my earlier append --- when I said .... "so that a 2.0 project could be started at some time" or course what I meant was a 3.0 project!
Regards, Kelvin. On 11/12/06, kelvin goodson <[EMAIL PROTECTED]> wrote:
I've created a JIRA component "Java SDO Compliance Test Suite". I don't feel I have enough info to do much about putting a framework into svn yet. Can we come to a consensus on the list some details like where it's housed and what the base package name base is, etc. At the top of this thread "test.sdo" was suggested as a package name; Let's assume this is OK unless anyone has any objections. Currently we have the SDO spec code in java/spec/sdo-api. Is it appropriate to make the test suite a peer of sdo-api? e.g. java/spec/sdo-cts? What about future proofing for handling future spec revisions. We have at least a couple of instruments to do this with. We could create a maven subproject for the 2.1 level tests, so that a 2.0 project could be started at some time. We could build a spec revision level into the package names. We could do both of those things. Should I transfer in the contents of my sandbox containing the early test code contribution from RogueWave? Regards, Kelvin. On 09/12/06, Dan Murphy <[EMAIL PROTECTED]> wrote: > > Hi Robbie, > > Sounds like an interesting approach, some examples would be great :) > > I was initially thinking we'd use junit v4 since it gets around some of > the > older limitations (eg. no longer needed to extend testcase). However > this > does mean we'd be requiring Java 5, which may not be a good idea.... > > Kelvin, can you get a svn module setup and (presumably) a jira Component > so > we can start using jiras to track contributions etc... > > What do you think ? > > Thanks to all for positive responses, > Dan > >
