Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel
borderColor#6699ff
bgColor#ffffff
titleBGColor#D5EFFF
titleApache Tuscany SDO Community Test Suite
borderStylesolid


 

Section

Anchor
Core Definition
Core Definition
What is

...

SDO Community Test Suite (SDO CTS)

...

The SDO CTS provides a set of test that exercise any SDO 2.1 implementation. The tests validate an SDO implementation behaves as expected, according to the community's understanding of the SDO specification.

...

If the SDO specification appears ambiguous or unclear then the community may decide what to do; it could decide to test the area with an agreed expected behaviour, or decide not to test this area. Ambiguities will be fed back to the specification group for clarification.

Anchor
How to get involved?
How to get involved?
How to get involved?

SDO users feedback and involvement would be greatly appreciated. Tell us what is important to you, and if you can provide test cases.

...

If you already have suitable test cases that you'd like to contribute, then go ahead and open an improvement in our tracking system.

Anchor
Obtaining and using the CTS
Obtaining and using the CTS
Obtaining and using the CTS

Currently the SDO CTS is only available in source form from the subversion repository. You will need the following:

...

If you would like to execute the SDO CTS against a different implementation then you will need to provide a helper class. For more info on this see the Contributing section.

Anchor
Run it
Run it
Running the CTS against Tuscany in Eclipse

Within the Tuscany svn repository there are two distinct source code hierarchies related to the CTS. The first, under the directory sdo2.1 is the real community test suite, and the second, sdo2.1-tuscany is the code that Tuscany uses to exercise the CTS. Another SDO implementation wishing to use the CTS would need to produce code similar to the Tuscany specific code to run the CTS tests against itself. It is important to maintain the separation of these two source hierarchies, so that no Tuscany code leaks into the generic CTS code, otherwise other SDO implementations would see compile failures in the core CTS because of the absence of the Tuscany code from their environment.

...