Cayenne QA

[Andrus Adamchik <an...@objectstyle.org>]

Adama's suggestion to help with Cayenne testing raises an interesting question - what is a useful way of "manually" testing Cayenne framework? I am taking "manually" in quotes as any such testing would involve writing Java apps.

On the one hand we have a pretty comprehensive suite of unit tests, on the other we have the mostly untested Modeler. ObjectStyle QA team is now experimenting with the Modeler testing and has already found a number of bugs. We'll load them to the Apache Jira at some point. 

So between those two test efforts (unit tests and manual Modeler QA), is there anything else we can do to make sure we do not overlook any issues with Cayenne? My few ideas are:

* Testing cross-version upgrade procedures (i.e. checking whether our UPGRADE.txt instructions are adequate, and expanding them as needed)
* Checking Cayenne behavior in a real app accessed from multiple threads - both thread-safety and performance. 

Thoughts on this?

Andrus



On Mar 19, 2012, at 10:55 PM, Adama Coulibaly wrote:
> Hi Andrus,
> 
> Thanks, I am comfortable writing Java. I can work on tetting the runtime
> framework.
> 
> Best,
> 
> Adama
> 
> On Mon, Mar 19, 2012 at 3:25 AM, Andrus Adamchik <an...@objectstyle.org>wrote:
> 
>> Hi Adama,
>> 
>> Sounds great. As you may have seen, Cayenne is made of a runtime framework
>> and CayenneModeler GUI application. The runtime framework is roughly split
>> into 2 parts - Persistence API (aka Cayenne server) and ROP (aka Cayenne
>> client).
>> 
>> All of these pieces may take advantage from testing.
>> 
>> If you are comfortable writing Java code, we can talk about testing the
>> runtime framework, if not - then CayenneModeler is another option.
>> 
>> Also I'd recommend subscribing to dev list (
>> http://cayenne.apache.org/mailing-lists.html ), and continue this
>> discussion there.
>> 
>> Cheers,
>> Andrus
>> 
>> 
>> 
>> On Mar 17, 2012, at 7:12 AM, Adama Coulibaly wrote:
>>> Hi,
>>> 
>>> I'm new to Cayenne and want to contribute by testing Cayenne and
>> reporting
>>> bugs
>>> For now I read the tutorial. Can anyone propose me simple testing
>>> application so that I can work on it
>>> to fit in Cayenne project.
>>> 
>>> Best,
>>> 
>>> Adama
>> 
>> 

Re: Cayenne QA

[Andrus Adamchik <an...@objectstyle.org>]

> * Testing cross-version upgrade procedures (i.e. checking whether our UPGRADE.txt instructions are adequate, and expanding them as needed)
> * Checking Cayenne behavior in a real app accessed from multiple threads - both thread-safety and performance. 

One more:

* Testing Cayenne behavior in web containers (specifically ensure that shutdown doesn't leave any stuck resources that would prevent webapp hot redeploy (see http://www.infoq.com/presentations/Diagnosing-Memory-Leaks for details).

Andrus


On Mar 21, 2012, at 1:43 PM, Andrus Adamchik wrote:

> Adama's suggestion to help with Cayenne testing raises an interesting question - what is a useful way of "manually" testing Cayenne framework? I am taking "manually" in quotes as any such testing would involve writing Java apps.
> 
> On the one hand we have a pretty comprehensive suite of unit tests, on the other we have the mostly untested Modeler. ObjectStyle QA team is now experimenting with the Modeler testing and has already found a number of bugs. We'll load them to the Apache Jira at some point. 
> 
> So between those two test efforts (unit tests and manual Modeler QA), is there anything else we can do to make sure we do not overlook any issues with Cayenne? My few ideas are:
> 
> * Testing cross-version upgrade procedures (i.e. checking whether our UPGRADE.txt instructions are adequate, and expanding them as needed)
> * Checking Cayenne behavior in a real app accessed from multiple threads - both thread-safety and performance. 
> 
> Thoughts on this?
> 
> Andrus
> 
> 
> 
> On Mar 19, 2012, at 10:55 PM, Adama Coulibaly wrote:
>> Hi Andrus,
>> 
>> Thanks, I am comfortable writing Java. I can work on tetting the runtime
>> framework.
>> 
>> Best,
>> 
>> Adama
>> 
>> On Mon, Mar 19, 2012 at 3:25 AM, Andrus Adamchik <an...@objectstyle.org>wrote:
>> 
>>> Hi Adama,
>>> 
>>> Sounds great. As you may have seen, Cayenne is made of a runtime framework
>>> and CayenneModeler GUI application. The runtime framework is roughly split
>>> into 2 parts - Persistence API (aka Cayenne server) and ROP (aka Cayenne
>>> client).
>>> 
>>> All of these pieces may take advantage from testing.
>>> 
>>> If you are comfortable writing Java code, we can talk about testing the
>>> runtime framework, if not - then CayenneModeler is another option.
>>> 
>>> Also I'd recommend subscribing to dev list (
>>> http://cayenne.apache.org/mailing-lists.html ), and continue this
>>> discussion there.
>>> 
>>> Cheers,
>>> Andrus
>>> 
>>> 
>>> 
>>> On Mar 17, 2012, at 7:12 AM, Adama Coulibaly wrote:
>>>> Hi,
>>>> 
>>>> I'm new to Cayenne and want to contribute by testing Cayenne and
>>> reporting
>>>> bugs
>>>> For now I read the tutorial. Can anyone propose me simple testing
>>>> application so that I can work on it
>>>> to fit in Cayenne project.
>>>> 
>>>> Best,
>>>> 
>>>> Adama
>>> 
>>> 
> 
>