|
Home > Archive > Apache JDO Project > September 2007 > JDO TCK 2.0 - Which set of tests to use?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
JDO TCK 2.0 - Which set of tests to use?
|
|
|
|
| Craig L Russell 2007-09-25, 1:11 pm |
| | |
| Ilan Kirsh 2007-09-25, 1:11 pm |
| Is there an approved exclude list for the original JDO 2 TCK 2.0
that is more realistic than the bundled list of 2 enhancement tests?
If not, when ready, I can publish my exclude list as a suggestion.
Regards, Ilan
----- Original Message -----
From: Craig L Russell
To: JDO Expert Group
Cc: Apache JDO project
Sent: Tuesday, September 25, 2007 7:32 PM
Subject: Re: JDO TCK 2.0 - Which set of tests to use?
Hi Ilan,
On Sep 25, 2007, at 10:18 AM, Ilan Kirsh wrote:
Hi,
The JDO 2 TCK 2.0 package that is available for download at:
http://db.apache.org/jdo/releases/release-2.0.cgi
contains many invalid tests that have been fixed since that release.
Correct. The latest trunk has updated tests.
In order to claim compliance with JDO 2 should I use the tests at:
http://svn.apache.org/viewvc/db/jdo/trunk/tck2-legacy/ ?
Well, there's no official release of the JDO 2.1 test suite, so probably to claim compliance with JDO 2.0, you should update the exclude list and run the original tests. And you should take a look at the tck2 project as well.
Should I fill CHALLENGE against tests in that set that IMO are invalid?
Yes. We still have time to fix these before official release.
Thanks,
Thank you for your continued support.
Craig
Ilan Kirsh
ObjectDB Software
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!
| |
| Michelle Caisse 2007-09-25, 7:11 pm |
| Hi Ilan,
There is a source branch 2.01 with changes responsive to some earlier
challenges. There's a wiki page documenting the issues
http://wiki.apache.org/jdo/TCKChallenges. Please get this branch from
svn and let us know if there are remaining issues.
Thanks,
Michelle
Ilan Kirsh wrote:
> Is there an approved exclude list for the original JDO 2 TCK 2.0
> that is more realistic than the bundled list of 2 enhancement tests?
>
> If not, when ready, I can publish my exclude list as a suggestion.
>
> Regards, Ilan
>
> ----- Original Message -----
> From: Craig L Russell
> To: JDO Expert Group
> Cc: Apache JDO project
> Sent: Tuesday, September 25, 2007 7:32 PM
> Subject: Re: JDO TCK 2.0 - Which set of tests to use?
>
>
> Hi Ilan,
>
>
>
>
> On Sep 25, 2007, at 10:18 AM, Ilan Kirsh wrote:
>
>
> Hi,
>
> The JDO 2 TCK 2.0 package that is available for download at:
> http://db.apache.org/jdo/releases/release-2.0.cgi
> contains many invalid tests that have been fixed since that release.
>
>
> Correct. The latest trunk has updated tests.
>
>
> In order to claim compliance with JDO 2 should I use the tests at:
> http://svn.apache.org/viewvc/db/jdo/trunk/tck2-legacy/ ?
>
>
> Well, there's no official release of the JDO 2.1 test suite, so probably to claim compliance with JDO 2.0, you should update the exclude list and run the original tests. And you should take a look at the tck2 project as well.
>
>
> Should I fill CHALLENGE against tests in that set that IMO are invalid?
>
>
> Yes. We still have time to fix these before official release.
>
>
>
> Thanks,
>
>
>
> Thank you for your continued support.
>
>
> Craig
>
>
> Ilan Kirsh
> ObjectDB Software
>
>
>
>
> Craig Russell
>
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
>
> 408 276-5638 mailto:Craig.Russell@sun.com
>
> P.S. A good JDO? O, Gasp!
>
>
>
>
| |
| Ilan Kirsh 2007-09-25, 7:11 pm |
| Hi Michelle,
That was very helpful. Running this branch looks much better.
Still I have problems with the following tests:
1. FetchPlanInterface.testGroups (fixed in JDO-402, after 2.0.1?)
2. ResultClassRequirements.testNegative (fixed in JDO-524)
3. ChangeQuery.testPositive (fixed in JDO-529)
4. ImplicitParameters.testGrouping (fixed in JDO-530)
5. StateTransitionsReturnedObjects (JDO-513, JDO-514).
Please advise.
Thanks, Ilan
----- Original Message -----
From: "Michelle Caisse" <Michelle.Caisse@Sun.COM>
To: <jdo-dev@db.apache.org>
Cc: "JDO Expert Group" <jdo-experts-ext@Sun.COM>
Sent: Tuesday, September 25, 2007 8:46 PM
Subject: Re: JDO TCK 2.0 - Which set of tests to use?
> Hi Ilan,
>
> There is a source branch 2.01 with changes responsive to some earlier
> challenges. There's a wiki page documenting the issues
> http://wiki.apache.org/jdo/TCKChallenges. Please get this branch from svn
> and let us know if there are remaining issues.
>
> Thanks,
> Michelle
>
> Ilan Kirsh wrote:
>
| |
| Michelle Caisse 2007-09-25, 7:11 pm |
| You'll have to enter a challenge on those and we'll back port the
changes to a 2.0.x branch or add the test to the exclude list.
To initiate a challenge "send email to: jdo-dev@db.apache.org
<mailto:jdo-dev@db.apache.org> with a subject line containing
"CHALLENGE" and the name of the test program, e.g.
org.apache.jdo.tck.api.persistencemanager.ThreadSafe.java; and the body
of the email containing the details of the challenge." You can just
reference the JIRAs for the details.
Thanks,
Michelle
Ilan Kirsh wrote:
> Hi Michelle,
>
> That was very helpful. Running this branch looks much better.
>
> Still I have problems with the following tests:
>
> 1. FetchPlanInterface.testGroups (fixed in JDO-402, after 2.0.1?)
> 2. ResultClassRequirements.testNegative (fixed in JDO-524)
> 3. ChangeQuery.testPositive (fixed in JDO-529)
> 4. ImplicitParameters.testGrouping (fixed in JDO-530)
> 5. StateTransitionsReturnedObjects (JDO-513, JDO-514).
>
> Please advise.
>
> Thanks, Ilan
>
>
> ----- Original Message ----- From: "Michelle Caisse"
> <Michelle.Caisse@Sun.COM>
> To: <jdo-dev@db.apache.org>
> Cc: "JDO Expert Group" <jdo-experts-ext@Sun.COM>
> Sent: Tuesday, September 25, 2007 8:46 PM
> Subject: Re: JDO TCK 2.0 - Which set of tests to use?
>
>
>
>
| |
| Michelle Caisse 2007-09-26, 7:11 pm |
| Hi Ilan,
It looks like there are 49 cases in which this test is not finding the
expected method signature in your implementation. Within this group,
there are three cases.
- There are 26 instances in which the impl declares a method abstract
and the test expects a concrete method.
- There are 21 cases where the test finds a fully qualified method name
and is expecting an unqualified name, as in:
|
|
|
|
|