vb-test
Runs the action chain tests that you have defined in your visual application for web (and mobile) apps, as well as for Oracle Cloud Application extensions.
The tests runs on built application sources, with the test results stored in the
build/tests/results directory as follows:
- jUnit tests:
[web|mobile]Apps/<appId>/<browserId>test-results.xml - Tests coverage report:
[web|mobile]Apps/<appId>/vbCoverage.json
(For extensions, the test results are stored directly in the build/tests/results directory.)
For more information, see Test Action Chains Using the vb-test Grunt Task .
Note:
Using the
vb-test to test an extension requires details about the platform dependencies of the base application. The VB runtime and JET URLs are obtained from following descriptors (in this order):
private/cache/base-application-config.jsonsettings/base-application-config.json- dependencies of the stripe matching the
source.versionproperty of the extension (defined inextension1/sources/vb-extension.json)
The following table describes the subtasks, hooks, and inputs and outputs of the vb-test task:
| Detail | Description |
|---|---|
| subtasks | n/a |
| multitask | config generator task: _vb-test-generate-configuration |
| hooks | n/a |
| input | build/processed |
| output | build/tests/results |
The following table describes the options for the vb-test task:
| Name | Mandatory | Default Value | Description |
|---|---|---|---|
| target | no | build | Name of build directory. |
| karma-debug | no | false | Enables unit test debugging. When Chrome open, you'll need to manually click DEBUG button in the window for the tests to run. You can open the Chrome Dev Tools, set some breakpoints, and reload the page to re-run the tests. |
| karma-log-level | no | INFO | Karma log level, which you can set to DEBUG for verbose logging. |
| karma-browser | no | ChromeHeadless | Browser mode to use. Use "Chrome" to run tests in UI (window) mode. |
| mocha-timeout | no | Timeout of Mocha tests (in milliseconds). |