Menu
▾
▴
springframework-developer
|
From: Colin S. <col...@ex...> - 2004-02-18 04:20:30
|
Testsuite: org.springframework.jdbc.object.SqlQueryTestSuite
Tests run: 4, Failures: 1, Errors: 0, Time elapsed: 1.282 sec
------------- Standard Output ---------------
2004-02-17 23:12:05,937 WARN
org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
from connection when trying to create exception translator
2004-02-17 23:12:05,968 WARN
org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
from connection when trying to create exception translator
2004-02-17 23:12:05,968 WARN
org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
from connection when trying to create exception translator
2004-02-17 23:12:05,984 WARN
org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
from connection when trying to create exception translator
2004-02-17 23:12:05,984 WARN
org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
from connection when trying to create exception translator
------------- ---------------- ---------------
Testcase: testQueryWithoutParams took 1.25 sec
Testcase: testQueryWithoutEnoughParams took 0 sec
Testcase: testBindVariableCountWrong took 0 sec
Testcase: testStringQueryWithResults took 0.032 sec
FAILED
Expectation failure on verify:
prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
FORENAME='beta'"): expected: 1, actual: 0
prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
FORENAME='charlie'"): expected: 1, actual: 0
junit.framework.AssertionFailedError:
Expectation failure on verify:
prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
FORENAME='beta'"): expected: 1, actual: 0
prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
FORENAME='charlie'"): expected: 1, actual: 0
at
org.easymock.internal.AbstractBehavior.verify(AbstractBehavior.java:77)
at org.easymock.internal.PlayState.verify(PlayState.java:25)
at org.easymock.MockControl.verify(MockControl.java:188)
at org.springframework.jdbc.JdbcTestCase.tearDown(JdbcTestCase.java:79)
at
org.springframework.jdbc.object.SqlQueryTestSuite.tearDown(SqlQueryTestSuite.java:54)
|
|
From: Thomas R. <tri...@tr...> - 2004-02-18 13:06:57
|
Colin,
I modifed JdbcTemplate and that broke this test - it's now fixed.
This brings up a couple of issues for out test suite:
- Running the entire test suite in Eclipse JUnit no longer runs without
errors (got 99 last run)
- Running the tests with Ant takes 4-5 minutes on my laptop
- A single package test usually works fine in Eclipse JUnit, but that
does not detect cross package dependencies
- EasyMock doesn't excatly give you a good idea of what the issue is
- Should the jdbc.object test suite mock JdbcTemplate instead of mocking
the JDBC classes - that way a change to the internal implementation of
JdbcTemplate would not throw off other tests.
Thomas
Colin Sampaleanu wrote:
> Testsuite: org.springframework.jdbc.object.SqlQueryTestSuite
> Tests run: 4, Failures: 1, Errors: 0, Time elapsed: 1.282 sec
> ------------- Standard Output ---------------
> 2004-02-17 23:12:05,937 WARN
> org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
> from connection when trying to create exception translator
> 2004-02-17 23:12:05,968 WARN
> org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
> from connection when trying to create exception translator
> 2004-02-17 23:12:05,968 WARN
> org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
> from connection when trying to create exception translator
> 2004-02-17 23:12:05,984 WARN
> org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
> from connection when trying to create exception translator
> 2004-02-17 23:12:05,984 WARN
> org.springframework.jdbc.support.SQLErrorCodesFactory - Null meta data
> from connection when trying to create exception translator
> ------------- ---------------- ---------------
>
> Testcase: testQueryWithoutParams took 1.25 sec
> Testcase: testQueryWithoutEnoughParams took 0 sec
> Testcase: testBindVariableCountWrong took 0 sec
> Testcase: testStringQueryWithResults took 0.032 sec
> FAILED
>
> Expectation failure on verify:
> prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
> FORENAME='beta'"): expected: 1, actual: 0
> prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
> FORENAME='charlie'"): expected: 1, actual: 0
> junit.framework.AssertionFailedError:
> Expectation failure on verify:
> prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
> FORENAME='beta'"): expected: 1, actual: 0
> prepareStatement("SELECT COUNT(FORENAME) FROM CUSTMR WHERE
> FORENAME='charlie'"): expected: 1, actual: 0
> at
> org.easymock.internal.AbstractBehavior.verify(AbstractBehavior.java:77)
> at org.easymock.internal.PlayState.verify(PlayState.java:25)
> at org.easymock.MockControl.verify(MockControl.java:188)
> at
> org.springframework.jdbc.JdbcTestCase.tearDown(JdbcTestCase.java:79)
> at
> org.springframework.jdbc.object.SqlQueryTestSuite.tearDown(SqlQueryTestSuite.java:54)
>
>
>
>
>
>
> -------------------------------------------------------
> SF.Net is sponsored by: Speed Start Your Linux Apps Now.
> Build and deploy apps & Web services for Linux with
> a free DVD software kit from IBM. Click Now!
> http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer
>
>
>
|
|
From: Rod J. <rod...@in...> - 2004-02-18 19:49:53
|
> - Running the entire test suite in Eclipse JUnit no longer runs without > errors (got 99 last run) I think we should fix this as a priority. It takes < 1 min on my laptop to run all tests in Eclipse. Must be a side effect. |
|
From: <tri...@tr...> - 2004-02-18 20:59:10
|
It was because cglib/asm.jar was missing from the classpath. I have added it to the '.classpath' file in CVS. I now get the "green bar" in 81 seconds on a PIII 800MHz - not bad. Thomas Quoting Rod Johnson <rod...@in...>: > > - Running the entire test suite in Eclipse JUnit no longer runs without > > errors (got 99 last run) > > I think we should fix this as a priority. It takes < 1 min on my laptop to > run all tests in Eclipse. > > Must be a side effect. > > > > > ------------------------------------------------------- > SF.Net is sponsored by: Speed Start Your Linux Apps Now. > Build and deploy apps & Web services for Linux with > a free DVD software kit from IBM. Click Now! > http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click > _______________________________________________ > Springframework-developer mailing list > Spr...@li... > https://lists.sourceforge.net/lists/listinfo/springframework-developer > |
