Hi, Florent Guillaume schrieb: > Hi David, > > An extensive test suite is very welcome, thanks! > > I would go for option a), and refactor later if and when we feel tests > can benefit from the Chemistry API. However there's real value in using > something totally external to Chemistry to test it, as we may miss > things otherwise. So a) is really not a problem for a start. > > Regarding the location, I propose to create a chemistry-tck maven module > to hold the tests. > > And yes JIRA is best to track tasks. I haven't always used it for the > early Chemistry work when everything was still moved around a lot, but > I'll do it in the future.
Agreed. Especially "bigger junks" should definitely enter at least by being referred to in a JIRA issue. Since David is a committer he can easily direclty import into SVN. But maybe for completeness attaching the patch/module to JIRA for later tracking would not be bad either. Regards Felix > > Bye, > Florent > > > On 6 Jul 2009, at 15:57, David Caruana wrote: > >> Dear all, >> >> I'd like to contribute the Alfresco CMIS client test harness to >> Chemistry. It consists of many tests that cover many aspects of the >> specification. I think this would be of value to the wider CMIS >> community as a starting point for not only testing Chemistry but any >> CMIS provider thus promoting compatibility between providers. On a >> personal note, I'd like to ensure Alfresco is tested with a suite >> that's community tested. >> >> Currently, I have two harnesses, one testing AtomPub directly and the >> other testing Web Services directly. >> >> Having studied the current Chemistry code base there are >> implementation options for the test harnesses. >> >> a) Contribute as is (first removing Alfresco specifics). This allows >> the full test harness to be used immediately against any provider, but >> doesn't use the Chemistry stack i.e. the chemistry-api. It also >> consists of an Abdera extension but that can easily be merged with the >> one already there (I understand the Abdera concerns that have been >> raised). >> >> b) Refactor the tests to use chemistry-api consolidating on one test >> harness. But, relies on the AtomPub client and Web Service client >> implementations meaning tests are disabled while those implementations >> are filled out. I have questions re: chemistry-api which I'll post >> separately. >> >> Of course, a) can be a starting point, and refactoring to b) could >> take place in Chemistry. >> >> The tests are implemented as a series of JUnit test cases. However, >> that doesn't preclude custom UI for executing and reporting the >> results, thus allowing for some form of CMIS provider test kit. >> >> Let me know of interest, and if there is a preference for a) or b). >> I'm assuming a new module for housing this (as chemistry-tests seems >> focused on testing low-level aspects of Chemistry). >> >> Re: mechanics of Chemistry project. How should we track in-development >> / future tasks? I assume via JIRA. >> >> Regards, >> David Caruana >> >
