Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 40badac

Browse files
committed
Describe the usage of tags in the "Running"-section
Fixes #1003
1 parent f8a3b87 commit 40badac

1 file changed

Lines changed: 17 additions & 0 deletions

File tree

docs/userguide/running-unit-tests.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -282,6 +282,23 @@ select * from table(ut.run('hr.test_apply_bonus', a_random_test_order_seed => 30
282282
**Note**
283283
>Random order seed must be a positive number within range of 1 .. 1 000 000 000.
284284
285+
# Run by Tags
286+
287+
In addition to the path, you can filter the tests to be run by specifying tags. Tags are defined in the test with the `--%tags`-annotation.
288+
Multiple tags are separated by comma. If multiple tags are set, all tests with __any__ of them specified are run.
289+
290+
Example Procedure:
291+
```sql
292+
begin
293+
ut.run('hr.test_apply_bonus', a_tags => 'test1,test2');
294+
end;
295+
```
296+
Example Function:
297+
```sql
298+
select * from table(ut.run('hr.test_apply_bonus', a_tags => 'suite1'))
299+
```
300+
301+
285302
# Keeping uncommitted data after test-run
286303

287304
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

Comments
 (0)