Laserfiche WebLink
Quality Control TSTool Documentation <br />Special # comment Tags <br /> <br />Parameter Description <br />@expectedStatus Failure <br /> <br />@expectedStatus Warning <br />The RunCommands() command ExpectedStatus <br />parameter is by default Success . However, a different status <br />can be specified if it is expected that a command file will result in <br />Warning or Failure and still be a successful test. For <br />example, if a command is obsolete and should generate a failure, <br />the expected status can be specified as Failure and the test will <br />pass. Another example is to test that the software properly treats <br />a missing file as a failure. <br />@os Windows <br />@os UNIX <br />Using this tag indicates that the test is designed to work only on <br />the specified platform and will be in cluded in the test suite by the <br />CreateRegressionTestCommandFile() command only <br />if the IncludeOS parameter includes the corresponding <br />operating system (OS) type. This is primarily used to test <br />specific features of the OS and similar but separate test cases <br />should be implemented for both OS types. If the OS type is not <br />specified as a tag in a command file, the test is always included. <br />@readOnly Use this tag to indicate that a command file is read-only. This is <br />useful when legacy command f iles are being tested because <br />TSTool will automatically update old syntax to new. <br />Consequently, saving the command file will overwrite the legacy <br />syntax and void the test. If this tag is included, the TSTool <br />interface will warn the user that the file is read-only and will only <br />save if the user indicates to do so. <br />@testSuite ABC Indicate that the command file should be considered part of the <br />specified test suite, as specified with the IncludeTestSuite <br />parameter of the <br />CreateRegressionTestCommandFile() command. Do <br />not specify a test suite tag for general tests. This tag is useful if a <br />group of tests require special setup, for example connecting to a <br />database. The suite names should be decided upon by the test <br />developer. <br /> <br />Using the above special comment tags, it is possible to create test suites that are appropriate for specific <br />environments. For example, using @testSuite HydroBase indicates that a test case should be <br />included in the HydroBase test suite, presumably run in an environment where a connection to HydroBase <br />has been opened. Consequently, multiple test suite s can be created and run as appropriate depending on <br />the system environment. <br /> <br />9.3.4 Verifying TSTool Software Using a Full Dataset <br /> <br />The previous sections described how to test TSTool soft ware using a suite of test cases. This approach <br />can be utilized when performing general tests, for exam ple prior to a normal software release. However, <br />there may be cases where TSTool has been used to produ ce a large data set and it is desirable to confirm <br />that a software release will still create the full dataset without differences. For example, for the State of <br />Colorado’s Decision Support Systems, large basin model data sets are created and are subject to <br />significant scrutiny. Approaches previ ously described in this chapter can be utilized to verify that TSTool <br />is functioning properly and creates the dataset fil es. The following procedure is recommended and uses <br />CDSS as an example: <br />Quality Control - 8 124