You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Vemund Ostgaard <Ve...@Sun.COM> on 2008/01/18 14:38:45 UTC
Java ME and ToursDB
The new test for ToursDB fails in my phoneME advanced environment, and
as far as I can understand the problem is that the demo uses
PreparedStatement.setBigDecimal() and this method does not exist in jsr169.
Should the demo and test be changed to work in Java ME, or should the
test not be run in that environment?
I looked at the latest nightly results with weme6.1 on windows:
http://people.apache.org/~fuzzylogic/derby_test_results/main/derbymain/testSummary-611996.html
but I am surprised to see that the test hasn't failed there. However,
only 2765 tests were run, when I run suites.All on phoneME advanced I
think I get around 3400 tests executed. Maybe the ToursDB test wasn't
executed on weme6.1? Anyone know why there is a difference in the number
of tests that are run?
Vemund
Re: Java ME and ToursDB
Posted by Myrna van Lunteren <m....@gmail.com>.
On 1/18/08, Vemund Ostgaard <Ve...@sun.com> wrote:
> The new test for ToursDB fails in my phoneME advanced environment, and
> as far as I can understand the problem is that the demo uses
> PreparedStatement.setBigDecimal() and this method does not exist in jsr169.
As of revision 613201 this test should no longer run with JSR169.
Myrna
Re: Java ME and ToursDB
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Vemund Ostgaard <Ve...@Sun.COM> writes:
> No swing in CDC/FP, but my modified textbased testrunner showed:
[...]
> true_hasServer(org.apache.derbyTesting.junit.EnvTest)duration: 0.021
> (+0.002)
Shouldn't Derby.hasServer() return false? Or do we support running the
server on Java ME?
--
Knut Anders
Re: Java ME and ToursDB
Posted by Vemund Ostgaard <Ve...@Sun.COM>.
Daniel John Debrunner wrote:
> I just added a "test" org.apache.derbyTesting.junit.EnvTest that shows
> the environment that the Junit setup sees. It does this by changing
> the name of the fixture, e.g.
>
> public void testJSR169() {
> setName(JDBC.vmSupportsJSR169() + "_vmSupportsJSR169()");
> }
>
> When I run this in the swing ui test runner I see the updated names in
> the test hierarchy window.
>
> I wonder if it would show different settings for weme6.1 and phoneME,
> leading to a different number of tests being run?
No swing in CDC/FP, but my modified textbased testrunner showed:
Test ended:
true_hasTools(org.apache.derbyTesting.junit.EnvTest)duration: 0.014 (+0.014)
Test ended:
true_hasEmbedded(org.apache.derbyTesting.junit.EnvTest)duration: 0.018
(+0.001)
Test ended:
false_hasClient(org.apache.derbyTesting.junit.EnvTest)duration: 0.018 (+0)
Test ended:
true_hasServer(org.apache.derbyTesting.junit.EnvTest)duration: 0.021
(+0.002)
Test ended:
false_vmSupportsJDBC4()(org.apache.derbyTesting.junit.EnvTest)duration:
0.022 (+0)
Test ended:
false_vmSupportsJDBC3()(org.apache.derbyTesting.junit.EnvTest)duration:
0.022 (+0)
Test ended:
true_vmSupportsJSR169()(org.apache.derbyTesting.junit.EnvTest)duration:
0.023 (+0)
Vemund
Re: Java ME and ToursDB
Posted by Daniel John Debrunner <dj...@apache.org>.
Vemund Ostgaard wrote:
> I looked at the latest nightly results with weme6.1 on windows:
> http://people.apache.org/~fuzzylogic/derby_test_results/main/derbymain/testSummary-611996.html
>
> but I am surprised to see that the test hasn't failed there. However,
> only 2765 tests were run, when I run suites.All on phoneME advanced I
> think I get around 3400 tests executed. Maybe the ToursDB test wasn't
> executed on weme6.1? Anyone know why there is a difference in the number
> of tests that are run?
I just added a "test" org.apache.derbyTesting.junit.EnvTest that shows
the environment that the Junit setup sees. It does this by changing the
name of the fixture, e.g.
public void testJSR169() {
setName(JDBC.vmSupportsJSR169() + "_vmSupportsJSR169()");
}
When I run this in the swing ui test runner I see the updated names in
the test hierarchy window.
I wonder if it would show different settings for weme6.1 and phoneME,
leading to a different number of tests being run?
I also added it as the first test in suites.All.
Dan.
Re: Java ME and ToursDB
Posted by Vemund Ostgaard <Ve...@Sun.COM>.
Vemund Ostgaard wrote:
> Myrna van Lunteren wrote:
>> Why there is a difference in the number of tests that are run I can't
>> say off the top...I can look into that next week. Is it possible for
>> you to run with -Dderby.tests.trace=true junit.textui.TestRunner or
>> some other mechanism that gets the list of tests, and attach them (or
>> send them to me)?
>>
> I'll do that.
Myrna discovered that the upgrade tests were not run in the
weme6.1-nightlies, so that explains the difference in the number of
tests run. Case closed.
Vemund
Re: Java ME and ToursDB
Posted by Vemund Ostgaard <Ve...@Sun.COM>.
Myrna van Lunteren wrote:
> Apologies, this test cannot (and thus should not be) run with JSR169.
> I missed the 'runwithfoundation=false' in the _app.properties file for
> the old test harness.
>
> I'll fix this up today.
> Those latest nightly results for j9 you quote (svn updated to revision
> 611996) don't include the new test yet, the check-in of the test
> conversion was done with revision 612218.
>
No apology needed, thank you for the quick reply and explanation.
> Why there is a difference in the number of tests that are run I can't
> say off the top...I can look into that next week. Is it possible for
> you to run with -Dderby.tests.trace=true junit.textui.TestRunner or
> some other mechanism that gets the list of tests, and attach them (or
> send them to me)?
>
I'll do that.
Vemund
Re: Java ME and ToursDB
Posted by Myrna van Lunteren <m....@gmail.com>.
On 1/18/08, Vemund Ostgaard <Ve...@sun.com> wrote:
> The new test for ToursDB fails in my phoneME advanced environment, and
> as far as I can understand the problem is that the demo uses
> PreparedStatement.setBigDecimal() and this method does not exist in jsr169.
>
> Should the demo and test be changed to work in Java ME, or should the
> test not be run in that environment?
>
> I looked at the latest nightly results with weme6.1 on windows:
> http://people.apache.org/~fuzzylogic/derby_test_results/main/derbymain/testSummary-611996.html
> but I am surprised to see that the test hasn't failed there. However,
> only 2765 tests were run, when I run suites.All on phoneME advanced I
> think I get around 3400 tests executed. Maybe the ToursDB test wasn't
> executed on weme6.1? Anyone know why there is a difference in the number
> of tests that are run?
>
> Vemund
>
>
Apologies, this test cannot (and thus should not be) run with JSR169.
I missed the 'runwithfoundation=false' in the _app.properties file for
the old test harness.
I'll fix this up today.
Those latest nightly results for j9 you quote (svn updated to revision
611996) don't include the new test yet, the check-in of the test
conversion was done with revision 612218.
Why there is a difference in the number of tests that are run I can't
say off the top...I can look into that next week. Is it possible for
you to run with -Dderby.tests.trace=true junit.textui.TestRunner or
some other mechanism that gets the list of tests, and attach them (or
send them to me)?
Myrna