Once you have browsed to the installation directory and entered dbtool, you can enter the parameters for the database actions.
The dbtool uses the parameters described in the table (Table 3.3, “dbtool parameters”):
Detail | Parameter |
---|---|
Help |
-h Gives parameter help |
Delete Project |
-delete <project-name project-version> e.g. -delete "ExampleProject" 1.0 For information on keeping test result summaries, see the section later (Section 3.26.3.1, “Deleting Projects but keeping test result summaries”). For information on how to enter version numbers, see the section below (Section 3.26.3.3, “Entering version numbers in the DB Tool”) |
Delete All |
-deleteall e.g. -deleteall For information on keeping test result summaries, see the section later (Section 3.26.3.1, “Deleting Projects but keeping test result summaries”). |
Keep test result summaries |
-keepsummary (optional) e.g. -keepsummary (Section 3.26.3.1, “Deleting Projects but keeping test result summaries”) |
Directory |
-directory <directory path> e.g. -directory "<pathToQADocs>/projects" The directory for imports and/or exports The directory must already exist |
Export Project |
-export <project-name project-version> e.g. -export "ExampleProject" "1.0" Existing files with the same name will be overwritten. For information on how to enter version numbers, see the section below (Section 3.26.3.3, “Entering version numbers in the DB Tool”). |
Export All |
-exportall e.g. -exportall The directory for the export all must be empty The directory must already exist |
Import Project |
-import <import-file> e.g. -import <ExampleProject.xml> |
Create Version |
-createversion <project-name> <old-version> <new-version> e.g. -createversion "MyProject" "1.0" "1.1" For information on versioning projects, see: Section 3.26.3.2, “Creating new versions of Projects” For information on how to enter version numbers, see the section below (Section 3.26.3.3, “Entering version numbers in the DB Tool”). |
Workspace |
-data <path to workspace> e.g. -data "<pathToQADocs>/workspace" The ITE workspace with the preference settings for the database connection This is optional if you enter the -dburl parameter |
Database scheme |
-dbscheme <scheme> e.g. -dbscheme "Oracle" This is optional if you enter the -dburl parameter |
Database username |
-dbuser <username> e.g. -dbuser "username" Use sa (without quotes) for the embedded database |
Database password |
-dbpw <password> e.g. -dbpw "password" Use <empty> ("") for the embedded database |
Database URL (optional) |
-dburl <URL> e.g. -dburl "db.example.de" If no URL is given, the default will be used. If you enter this, you do not need to enter the -data or -dbscheme parameter You can find the dburl in the database preferences |
You can use the parameter -keepsummary to specify that the test result summaries should not be deleted when the Project or Projects are deleted. This is useful for continuous integration processes, where the test results over time should be kept, but the Projects are reimported into the database (for example from the version control system) each night. If you do not enter this parameter, the summaries will be deleted with the Projects.
You can use the dbtool to create a new version of a Project that already exists in the database. You enter the Project name, the version you want to create a copy of, and the new version number that the Project should be created under. The create new version command functions in the same way as the create new version option in the ITE (Section 3.6.11, “Versioning Projects”). If the Project is not in the database in the specified version, or if the new version already exists, then the action will fail. We recommend using this when you are sure that no-one is working on the Project.
![]() |
If you are using the embedded database, see the section on using the embedded database with the Test Executor for information on which username and password to use (Section 3.25.4, “Using the test executor with the embedded database”). |
Once you have entered all the necessary parameters, press »ENTER«.
You can enter version numbers such as "1.0.0_release" or "1.0".
If your version only uses a qualifier, you can enter it as e.g. "release". If you are using a qualifier-only version that begins with a number, then you must use a preceding underscore (e.g. "_3").