This sounds really good me, it would be excellent to have a set of SCA tests like the SDO CTS ones. So I say just go for it, we can help sort out any issues with automation and the testing framework as you come across them.
...ant On 3/29/07, Robbie Minshall <[EMAIL PROTECTED]> wrote:
Hi. For SDO we contributed to the SDO CTS allowing tuscany to consume our test cases. In the CTS we took the approach of a vendor independent component of tests (java/cts/sdo2.1) and a vendor specific impl (java/cts/sdo2.1-tuscany) which uses the tests and handled initialization etc. This has worked well for us. We are now looking at some sca testing and I am hoping that we can contribute our test cases back to tuscany as well. In general our tests are very similar to the format of the itests where there is an application which lifecycle is managed by the testing infrastructure and junit is used to test it's functionality. We have our own automation environment for handling the lifecycles of applications and test execution ( one day it would be really nice if this could be expressed in a general way so that ithe description could be portable between automation environments ). I think there is a good opportunity to work on a environment for tests that can be used and contributed to by implementations of the sca specification. This could be as simple as agreeing on some generic packaging schemes ( we used test.sdo... for the cts ) that would save constant refactoring when we contribute tests back to tuscany or could even involve a common description for the lifecycle of tests and sca applications. What are people's thoughts on this ? cheers, Robbie -- * * * Charlie * * * Check out some pics of little Charlie at http://www.flickr.com/photos/[EMAIL PROTECTED]/sets/ Check out Charlie's al crapo blog at http://robbieminshall.blogspot.com * * * Addresss * * * 1914 Overland Drive Chapel Hill NC 27517 * * * Number * * * 919-225-1553
