Tree [2ec31b] squirrel-root-pom-3.3.0-rc1 / test /
 History



File Date Author Commit
 adhoc 2010-04-24 Robert Manning Robert Manning [16e727] Command-line utility to determine version info ...
 docs 2010-09-03 Robert Manning Robert Manning [56883f] removed readme which only served a purpose when...
 jfctests 2011-03-19 Robert Manning Robert Manning [4c67b6] Relocated uitests profile to root so that it ca...
 mockobjects 2009-12-19 Robert Manning Robert Manning [2ff496] Aliases now have the ability to setup keep-aliv...
 proxydriver 2009-01-24 Robert Manning Robert Manning [31b694] relocated the test proxy driver out of the main...
 scripts 2009-04-18 Robert Manning Robert Manning [f205f8] test script for db2 UDTs.
 sql 2010-02-27 Robert Manning Robert Manning [ed4bee] script that demonstrates issue with long lines.
 readme.txt 2010-09-03 Robert Manning Robert Manning [ce7ffa] Removed no longer required external integration...

Read Me

This test directory contains all of the code and scripts that are required to 
test SQuirreL.  All JUnit tests (internal and external) are stored here in the 
same package structure of the classes that they test.  The directories found 
here are:

 * adhoc - test drivers that are used to connect to a specific database for 
           performing some integration test.
           
 * docs - documents that describe the testing process and testing results
            
 * jfctests - integration tests that run a particular GUI component for the 
              purpose of testing that component in isolation from SQuirreL.  
              This speeds the iterative process of customizing view components.

 * lib - libraries that are required to execute the code here.(e.g. JUnit)
 
 * mockobjects - some early attempts to provide fixtures for various key objects
                 used in SQuirreL by some JUnit tests.  EasyMock has been 
                 chosen to supercede the use of these mocks, and a class called
                 TestUtilities provides EasyMock factory methods for many of 
                 the classes held here.  These classes may still be used by some
                 integration tests.
                 
 * scripts - various scripts that have been used to perform adhoc or integration
             tests against particular databases.
             
 * src - All JUnit tests that are unit tests (completely self-contained tests 
         that do not require external resources like filesystems or databases.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks