Hi Kelvin,
Thanks for creating the component for Jiras... I agree we need to amend the
names to cope with different spec / implementation versions
We need to agree on:
- SVN module - propose java/cts/sdo2.1
- allow for java/cts/sdo30 & java/cts/sca (if needed) in the
future
- Java package - propose test.sdo21
- allows for test.sdo30 / test.sca.096 (if needed) in the future
- How to easily link between test cases (or suite) and sections in the
spec - propose package conversion of test.sdo21.section.subsection
- eg. package test.sdo21.api.datagraph for tests relating to the
Java API (main section) DataGraph (minor section) of the spec (section
3.2)
- another eg. test.sdo21.typeconv for the DataTypes Conversion
section (section 16)
- Using test.sdo21.section.subsection makes it easy to link
cases to spec, but might be a little overkill - any thoughts ?
- Where to locate SDO 2.1.0 Java Classes - propose linking to tuscany
sdo spec project
- Link to existing ones in Tuscany (in java/spec/sdo-api), or
- package own copy
- Framework to use - JUnit or the approach Robbie has, or some other ?
- need to ensure sdo implementation is pluggable
Now that we have a Jira component (SDO Community Tests) I guess we can start
opening up new features against it and identifying what we have - if there
is an existing large suit / contribution then we could always just adopt its
approach (to start with).
Cheers,
Dan
