...
Download the Plugin Update Site at
View file | ||
---|---|---|
|
Start the Progress Developer Studio for OpenEdge
Go to Help → Install New Software … → Add … → Archive …
Navigate to the plugins zip-file and click open
Entering a name is optional but helps finding the repository later on
...
It has two targets to run tests.
Target | Description |
execute-unit-test | Used to run SmartUnit test classes (.cls files). |
execute-scenario-test | Used to run SmartUnit test scenarios (.scenario files). |
The sample also requires two additional ANT arguments to run.
The path to a PCT.jar, passed as -lib.
The path to the DLC, passed as -Ddlc.
Those can be set in the preferences or the SmartUnit run configurations.The sample-file as well as its targets and arguments can be specified in the preferences and for specific SmartUnit run configurations
ANT arguments
The plugin passes arguments based on either the selected file or settings (preferences or run configuration).
Argument | Description | Set by | Notes |
---|---|---|---|
-Dsmartunit.testclass | Path to the class file to run | Either selected by running the test from its context menu or set in the run configuration. | Only passed when running test classes |
-Dsmartunit.testmethod | Test-method in the test class | Can be set in the run configuration. | Execution of individual test-methods is not yet supported by SmartUnit |
-Dsmartunit.testscenario | Path to the scenario file to run | Either selected by running the test from its context menu or set in the run configuration. | Only passed when running test scenarios |
-Dsmartunit.output | Path to an XML file for the test results | Can be set in either the preferences or the SmartUnit run configurations. | Required |
-Dsmartunit.services | List of service definition files that should be loaded prior to the test run | Can be set in either the preferences or the SmartUnit run configurations. | Optional |
-Dsmartunit.profiler | Whether the ABL performance profiler should be enabled through PCTRun | Can be set in either the preferences or the SmartUnit run configurations. | Defaults to false |
Any other arguments required to run custom build files can be added to “Additional ANT Arguments” in either the preferences or a specific SmartUnit run configuration.
Preferences
The prefrences can be found at Window → Preferences → SmartUnit. They are used as default values to run SmartUnit tests from the context menu and to initialize run configurations.
...
Preference | Description |
ANT Executable | The ANT executable to run the build-file with. |
Build File | The ANT build file that runs the tests (see sample “unittest-runner.xml” above). |
Output File | The xml file for the test results. |
Test Class ANT Target | The target in the Build File that should be executed for .cls files. |
Scenario ANT Target | The target in the Build File that should be executed for .scenario files. |
Services | The value for the “Services” parameter passed to SmartUnit. |
Additional ANT Arguments | Additional arguments required by the specified Build File. |
Output in console | Whether the Build Files output should be displayed in a console. The SmartUnit View is opened regardless. |
Enable Profiler | Whether PCTRun should be executed with an enabled profiler. |
The SmartUnit preferences also contain a link back to this page.
...
SmartUnit tests can be run from the Run As… context menu by right clicking the test-file (.cls or .scenario) in either the Project Explorer or inside a an opened text editor (e.g. OpenEdge ABL Editor).
...