A command-line interface for executing Regression Testing Test Suites is provided with InRule.
The command-line interface can be used to integrate Regression Testing execution into a build process, for example. The command-line executable is installed with irAuthor and is called irVerify.exe.
Command Line Usage
irVerify.exe /s TestSuitePath [/n TestName[,TestName2,...,TestNameN]] [/f FolderName[,FolderName2,...,FolderNameN]] [/r TestResultsPath] [/l RuleApplicationLocationURI] [/w]
| /s TestSuitePath | Required parameter. Specifies the path to the Test Suite file to be executed. |
| /n TestName | Optional parameter. Comma separated (no spaces) list of test case names to be executed. |
| /f FolderName | Optional parameter. Comma separated (no spaces) list of folder names to be executed. |
| /r TestResultsPath | Optional parameter. Specifies path to test results file to be saved. |
| /l RuleApplicationLocationURI |
Optional parameter. Specifies the location of the Rule Application to be tested. This is a file path for file based rule applications and a URI for irCatalog based rule applications. Note: This parameter is required unless the Test Suite was created via the SDK. If using the SDK, the rule application location can be embedded within the Test Suite file. |
| /w | Optional parameter. Suppresses windows. |
Usage Examples
The following examples will be based on a rule application called ExampleRuleApp. The rest of the information about this rule application is listed in the table below.
| /s TestSuitePath | Example.testsuite |
| /n TestName |
ExampleTestCase1, ExampleTestCase2 Note: These are tests within Example.testsuite |
| /f FolderName |
ValidationTestFolder and PromotionTestFolder Note: These are folders within Example.testsuite that |
| /r TestResultsPath |
Example.testresults Note: This file will be created if this parameter is used. If |
| /l RuleApplicationLocationURI |
If the rule application is saved in irCatalog:
If the rule application is saved to file:
|
Execute a couple of test cases from a Test Suite.
> irVerify /s Example.testsuite /n ExampleTestCase1,ExampleTestCase2 /l ExampleRuleApp.ruleappx
Execute all test cases from a Test Suite and save the results.
> irVerify /s Example.testsuite /r Example.testresults /l ExampleRuleApp.ruleappx
Execute all test cases found in the folders specified and their subfolders.
> irVerify /s Example.testsuite /f ValidationTestFolder,PromotionTestFolder /l ExampleRuleApp.ruleappx
Execute test cases for a Rule Application that is stored in irCatalog.
> irVerify /s Example.testsuite /l catalog://username:password@Server/InRuleCatalog/ Service.svc/ExampleRuleApp
Identical to the command above but uses the explicit form of the scheme to indicate it is using HTTP as opposed to HTTPS.
> irVerify /s Example.testsuite /l catalog.http://username:password@Server/InRuleCatalog/ Service.svc/ExampleRuleApp
Execute test cases for a rule application that is stored in irCatalog that is hosted on a HTTPS host.
> irVerify /s Example.testsuite /l catalog.https://username:password@Server/InRuleCatalog/ Service.svc/ExampleRuleApp
Execute test cases for a rule application that is stored in irCatalog that uses single-sign-on (SSO).
> irVerify /s Example.testsuite /l catalog.http://Server/InRuleCatalog/Service.svc/ ExampleRuleApp
Execute test cases from a Test Suite that was created via the SDK. Using the SDK, you can save the rule application location within the Test Suite file. The rule applicationn must exist on the file system relative to where the Test Suite file was originally saved.
> irVerify /s Example.testsuite
For simplicity, all the examples above assumed that everything is saved within one folder. If this is not the case, you may use the full file path or the relative file path for the Test Suite, test results, and rule application. In the following example, the command is being executed from C:\InRule where irVerify.exe is located. Test Suite uses the full file path and rule application uses the relative file path.
>irVerify /s C:\RuleApps\Example.testsuite /l ..\RuleApps\ExampleRuleApp.ruleappx
Comments
0 comments
Please sign in to leave a comment.