Re: AW: Testing the release [was: AW: Start release Cycle for Torque 3.2]

2005-07-13 Thread Thomas Fischer

Hi Joerg,

running limited tests is better than running no tests. Also, I would guess 
that the Torque runtime tests are not a complete test of the Torque 
functionality (we are working on it), so it might be that your tests cover 
other areas of the Torque functionality than the Torque tests.


Any suggestion with regard to documentation is appreciated.

Thomas



On Mon, 11 Jul 2005, [iso-8859-1] J?rg Friedrich wrote:


Currently I just have tests for the application itself, so this would cover
only a certain fraction of Torque functionality. I could try to recruit
somebody to run the official Torque test suite against the new release;
however that would probably not be ready before the end of the year.

With regard to documentation, I could try to come up with a suggestion for
discussion.

 Joerg



-Urspr?ngliche Nachricht-
Von: Thomas Fischer [mailto:[EMAIL PROTECTED]
Gesendet: Montag, 11. Juli 2005 14:48
An: Apache Torque Developers List
Betreff: Testing the release [was: AW: Start release Cycle for Torque 3.2]






Hi J?rg,

J?rg Friedrich [EMAIL PROTECTED] schrieb am 11.07.2005
13:09:36:


As PM of the Track+ project I could run our test cases against any new
Torque release. We are supporting MySQL, Firebird/Interbase, HSQLDB,

Oracle

8,9,10, MS SQLServer and PostgreSQL.



Would you run the Torque runtimetest or do you have your own Testcases ? I
cannot test again Oracle 8, Oracle 10, Interbase and MS SQLServer, so I
would highly appreciate if you could run the test against these. If you
would run your own testcases against any database, I would also be
interested in the results.


With regard to documentation, what do you think would be most
important?


Well, it seems most impotant to me to get a structure for a User guide or /
and reference, but this is a really big task. There is a bit of
documentation around, but it is not structured well enough to find much, and
a lot is missing. But once one has a good structure, it would be possible to
fill it in bit after bit.

   Thomas


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

cvs commit: db-torque/src/rttest/org/apache/torque DataTest.java

2005-07-13 Thread tfischer
tfischer2005/07/13 13:34:29

  Modified:src/rttest/org/apache/torque DataTest.java
  Log:
  Corrected typos in testcase BlobTest
  
  Revision  ChangesPath
  1.27  +7 -7  db-torque/src/rttest/org/apache/torque/DataTest.java
  
  Index: DataTest.java
  ===
  RCS file: /home/cvs/db-torque/src/rttest/org/apache/torque/DataTest.java,v
  retrieving revision 1.26
  retrieving revision 1.27
  diff -u -r1.26 -r1.27
  --- DataTest.java 26 Jun 2005 10:46:48 -  1.26
  +++ DataTest.java 13 Jul 2005 20:34:29 -  1.27
  @@ -1031,9 +1031,9 @@
* check that blob cloumns can be read and written correctly
* @throws Exception if the test fails
*/
  -public void testLobs() throws Exception
  +public void testBlobs() throws Exception
   {
  -// clean LobTest table
  +// clean BlobTest table
   {
   Criteria criteria = new Criteria();
   criteria.add(
  @@ -1062,12 +1062,12 @@
   
   // read the BlobTests from the database
   // and check the values against the original values
  -List lobTestList = BlobTestPeer.doSelect(new Criteria());
  +List blobTestList = BlobTestPeer.doSelect(new Criteria());
   assertTrue(blobTestList should contain 1 object but contains  
  -+ lobTestList.size(),
  -lobTestList.size() == 1);
  ++ blobTestList.size(),
  +blobTestList.size() == 1);
   
  -BlobTest readBlobTest = (BlobTest) lobTestList.get(0);
  +BlobTest readBlobTest = (BlobTest) blobTestList.get(0);
   assertTrue(read and written blobs should be equal. 
   + Size of read blob is
   + readBlobTest.getBlobValue().length
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



cvs commit: db-torque/src/rttest/org/apache/torque DataTest.java

2005-07-13 Thread tfischer
tfischer2005/07/13 14:12:07

  Modified:src/rttest/org/apache/torque DataTest.java
  Log:
  added a testcase which does a select for prepared statements
  
  Revision  ChangesPath
  1.28  +35 -2 db-torque/src/rttest/org/apache/torque/DataTest.java
  
  Index: DataTest.java
  ===
  RCS file: /home/cvs/db-torque/src/rttest/org/apache/torque/DataTest.java,v
  retrieving revision 1.27
  retrieving revision 1.28
  diff -u -r1.27 -r1.28
  --- DataTest.java 13 Jul 2005 20:34:29 -  1.27
  +++ DataTest.java 13 Jul 2005 21:12:07 -  1.28
  @@ -918,7 +918,7 @@
*/
   public void testLargePk() throws Exception
   {
  -// clean Date table
  +// clean LargePk table
   Criteria criteria = new Criteria();
   criteria.add(
LargePkPeer.LARGE_PK_ID, 
  @@ -1123,6 +1123,39 @@
   }
   
   /**
  + * Test whether we can execute queries as prepared statements
  + * @throws Exception
  + */
  +public void testPreparedStatements() throws Exception
  +{
  +// clean LargePk table
  +Criteria criteria = new Criteria();
  +criteria.add(
  +LargePkPeer.LARGE_PK_ID, 
  +(Long) null, 
  +Criteria.NOT_EQUAL);
  +LargePkPeer.doDelete(criteria);
  +
  +LargePk largePk = new LargePk();
  +largePk.setLargePkId(1);
  +largePk.setName(testLargePk);
  +largePk.save();
  +
  +largePk = new LargePk();
  +largePk.setLargePkId(2);
  +largePk.setName(testLargePk);
  +largePk.save();
  +
  +criteria = new Criteria();
  +criteria.add(LargePkPeer.LARGE_PK_ID, 2, Criteria.LESS_THAN);
  +LargePkPeer.addSelectColumns(criteria);
  +List result = BasePeer.doPSSelect(criteria);
  +assertTrue(Size of largePk list should be 1 but is  
  ++ result.size(),
  +result.size() == 1);
  +}
  +
  +/**
* Tests whether shutdown complains about anything
* @throws TorqueException if shutdown does not exit cleanly
*/
  
  
  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]