You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/userguide/running-unit-tests.md
+75Lines changed: 75 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -325,6 +325,8 @@ Multiple tags are separated by comma.
325
325
326
326
Tag expressions are boolean expressions created by combining tags with the `!`, `&`, `|` operators. Tag expressions can be grouped using `(` and `)` braces. Grouping tag expressions affects operator precedence.
327
327
328
+
Two special expressions are supported, `any` and `none`, which select all tests with any tags at all, and all tests without any tags, respectively. These special expressions may be combined with other expressions just like normal tags. When using `none` be aware that if the suite is tagged it will exclude any tests and children belonging to that suite.
329
+
328
330
| Operator | Meaning |
329
331
| -------- | --------|
330
332
| ! | not |
@@ -450,6 +452,79 @@ The above calls will execute all suites/contexts/tests that are marked with any
450
452
Given the above example package `ut_sample_test`, only `ut_sample_test.ut_test` will be executed.
The above call will execute tests `ut_test_no_tag` and `ut_refcursors1`
527
+
453
528
## Keeping uncommitted data after test-run
454
529
455
530
utPLSQL by default runs tests in autonomous transaction and performs automatic rollback to assure that tests do not impact one-another and do not have impact on the current session in your IDE.
0 commit comments