This commit concentrates on two related issues: - It adds a new command line switch `--exit-threshold` which allows users specify the threshold value (numeric) which is used to filter out tool exit codes: if reported exit code is below the threshold value, tool simply returns 0. - Restructures exit codes values to have higher value representing more severe condition. This plays nicer with previous point. Currently warning has value 1, error 2, fatal 3 (although fatal is not used currently in the tool). Note that it's not possible to suppress crashes, regardless of whether the threshold is set above the value (250 currently)! Also updated build number to 692.
Note that "real-life" is quite simple at this point, but the data will be expanded slowly to get more accurate testing.
…e class for unit cases which need to do these assertions. Note that we couldn't use class methods as we do with GBTestObjectsRegistry as we use SenTest macros which require failWithException: method be declared in the test case class.