databene

 
  • Increase font size
  • Default font size
  • Decrease font size

DB Sanity Command Line Arguments

Command Line Invocation

    dbsanity [options] <environment_name>

 

Options

Short Option
Long Option
Description
-i <check folder>
--in
read the sanity check definitions from the specified folder (Default: ./test)
-o <report folder>
--out
write the test reports to the specified folder (Default: ./result)
-c --clear
clear the report folder before generating the report (Default: don't clear)
-C
--condensed
creates a report which contains only failed checks
-a <version>
--appversion <version>
only perform checks that relate to the specified version
-b
--buffer
buffer database meta data
-B
--browse
open a browser window with the report when checks are finished
-s <skin>
--skin <arg>
use skin (default: online, optional: offline)
-l <locale>
--locale
render the report using the specified locale (2 letter iso code)
-L <number>
--limit <number>
limits the number of reported defects per check to the specified value
-m
--maxrows
limits the number of listed defect data rows per check to the specified value 
-t <table list>
--tables <table list>
perform checks only for the comma-separated list of tables
-T <tag list>
--tag <tag list>
perform only checks which have one or more of the specified tags
-q
--quiet
quiet mode
-v
--verbose
verbose mode
-V
--version
prints out DB Sanity's version number
-k
--keep
keep the temoporary files (for developers)
-h
--help
print this help
-z
--zip
makes DB Sanity compress the report in a ZIP file

 

Process Exit Code

When calling DB Sanity from another process, e.g. using a script file, you can now evaluate execution success from its process exit code: 0 stands for complete success, -1 signals that checks failed or resulted in an error.

 

Recommended further reading: Versioning DB Sanity Checks.