RE: [OJB-developers] quality improvements

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I agree. I think we need some sort of domain to model that lends itself to
testing all the complexities. 

It would be great to come up with a class diagram that showed all the moving
parts that we could agree on first, then start to build a new scenario to
base all test cases on.

I think the general direction has been somewhat of a store (?). Maybe we
build an ecommerce type of application (with no UI) where we have the users
who have carts that contain items. We could also model an administrative
function where admins have roles to manage different stores. The complexity
of an ecommerce model is pretty much unbounded, so I don't think we'll ever
run out of ways to make new test cases. Later if someone wants to use struts
to show how to use OJB in a servlet engine, or in a ejb environment we could
extend it that way.

Either that or we could build the "OJB Petstore" which would be similar to
the above.

Any other recommendations?

m

-----Original Message-----
From: Jakob Braeuchi [mailto:jbr...@ho...] 
Sent: Friday, June 14, 2002 12:16 AM
To: Matthew Baird; Mahler Thomas; Objectbridge (E-Mail)
Subject: Re: [OJB-developers] quality improvements

hi matthew,

imho we need to extend our object model to match the different scenarios. 

the current model with a class and a table for each testcase is getting too
cluttered.

i don't like changing metadata at runtime for testcases.

jakob

----- Original Message ----- 

From: Matthew <mailto:ma...@so...>  Baird 

To: 'Jakob <mailto:jbr...@ho...>  Braeuchi' ; Mahler Thomas
<mailto:tho...@it...>  ; Objectbridge (E-Mail)
<mailto:obj...@li...>  

Cc: Matthew <mailto:Mat...@mo...>  Baird (E-Mail) 

Sent: Friday, June 14, 2002 9:00 AM

Subject: RE: [OJB-developers] quality improvements

I would agree if we had a model for every permutation sometimes to simulate
a complex scenario we need new tables that might not fit into the
person/project/etc. Plus there is the different mappings. I guess we could
change the mapping metadata at runtime, but the test becomes more
complex....

Tough call.

-----Original Message-----
From: Jakob Braeuchi [mailto:jbr...@ho...] 
Sent: Thursday, June 13, 2002 11:29 PM
To: Mahler Thomas; Objectbridge (E-Mail)
Cc: Matthew Baird (E-Mail)
Subject: Re: [OJB-developers] quality improvements

hi,

we already have a lot of test cases (not enough, i know) and we also have a
lot test classes and test tables.

for 1:n we have productGroup - articles, for m:n there are persons -
projects and the graphEdge - graphNode 

and many more all with their own tables.

so i propose to have a common object-model for our test cases. 

this model should contain real-world classes, like persons, projects etc.
that are known by everybody (not A,B etc.). 

these classes could also be useful for examples and tutorials.

what do you think ?

jakob

----- Original Message ----- 

From: Mahler Thomas <mailto:tho...@it...>  

To: Objectbridge (E-Mail)
<mailto:obj...@li...>  

Cc: Matthew <mailto:Mat...@mo...>  Baird (E-Mail) 

Sent: Thursday, June 13, 2002 9:21 AM

Subject: [OJB-developers] quality improvements

Hi all,

OJB is making a lot of progress in the last months. We have tons of new
features and a lot of very good refactorings of the internal mechanisms.

So far so good!

We did not succeed to improve our regression testsuite accordingly. Of
course there a lot of new TestCases. But there are still many things not
covered thoroughly.

Matthew prepared a list of missing testcases, enumerating some of the most
urgent tests:

1. One-To-One test (for both ODMG and PB)

         Create/Read/Update/Delete

         Create/Read/Update/Delete with Proxies

         Create/Read/Update/Delete with class that belongs to set of classes
mapped to same table.

2. One-To-Many test (for both ODMG and PB)

         Create/Read/Update/Delete

         Create/Read/Update/Delete with Proxies

         Create/Read/Update/Delete with class that belongs to set of classes
mapped to same table.

3. Many-To-Many test (for both ODMG and PB) (both types of composition)

         Create/Read/Update/Delete

         Create/Read/Update/Delete with Proxies

         Create/Read/Update/Delete with class that belongs to set of classes
mapped to same table.

4. ODMGCollections test

         Create/Read/Update/Delete

      Create/Read/Update/Delete with proxies

         PerformanceTest

         Empty Collections Test

      Create/Read/Update/Delete with class that belongs to set of classes
mapped to same table.

5. Conversions Tests

6. LockMap performance tests

7. OQL ORDER BY tests

8. Concurrent Update Test

9. Deadlock test

10. Key generation tests

11. Duplicate key insertion test

12. multi-pk's test

13. callbacks test

14. Race Condition tests

15. Lock Modes test

16. CLOB/BLOB/LOB tests.

17. Delete by Query Tests

18. Query By Example tests with multiple classes mapped to same table)

Each of us could easily add at least 5 additional urgent testcases to this
list!

So I'm requesting all to join the OJB quality improvement initiative and
contribute TestCases.

Feel free to implement some of those 18 tests mentioned above or to
contribute your own TestCases.

As I mentioned in my  <http://objectbridge.sourceforge.net/team.html>
http://objectbridge.sourceforge.net/team.html document it's best practice to
add new TestCases with all new features or refactorings!

Thanks for helping to improve code quality,

cheers,

Thomas 