1. Download latest framework version.
  2. Prepare the target database. 

Note: For Netezza and SQL Server we recommend to create a separate database and call it "DBTestDriven", in Oracle we recommend to create a separate schema and call it "DBTestDriven".
Isolating DBTestDriven framework into separate database (schema) will force developer to use fully specified object names and make sure that they are testing intended functionality. As a second benefit of isolation is that developers will have an extra step that prevents them from pushing unit test code to production databases, since some of the unit test can be quite invasive and can add/delete data they should not be promoted to production with out extra consideration.  

  1. Create the target database if it does not exist by running "DbTestDriven-CreateDatabase.sql" file 
  2. Back up the target database if it already exists
  3. Remove currently installed framework version by running "DBTestDriven-Remove.sql" script from an older (or the current) version of the framework installation package. 
  1. Run "DbTestDriven-Tools.sql" (Required: Netezza, SQL Server. Optional: Oracle)
  2. Run "DbTestDriven-Install.sql" script to install framework to the target environment
  3. Run "DbTestDriven-InstallCompatibilityPack.sql" script to install the latest Compatibility Pack.
  4. Done.

 

Prerequisites

following basic privileges required in target database (you might need to have elevated privileges if you are creating the separate database) :

  • Create views
  • Create tables
  • Create stored procedures
  • and create Sequences

 

See Also