Skip to content

Ability to run expectations without test #963

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jgebal merged 7 commits into from
Jul 13, 2019
Merged

Ability to run expectations without test #963

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
f5fa468
[WIP] Ability to run expectations without test
jgebal Jul 2, 2019
99bae42
Removed `time_in_suite`, `time_in_context`, `time_in_test` as they ar…
jgebal Jul 3, 2019
d932f75
- Fixed minor typos, formatting and issues with expectation results.
jgebal Jul 8, 2019
2206ff9
Fixing failing test.
jgebal Jul 8, 2019
1ea69d8
Updated documentation for expectations.
jgebal Jul 11, 2019
773eae2
Improved functionality of reporters to allow for inline calls.
jgebal Jul 13, 2019
ac4ca00
Added documentation section on `sys_context( 'UT3_INFO', attribute )`.
jgebal Jul 13, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Added documentation section on sys_context( 'UT3_INFO', attribute ).
  • Loading branch information
@jgebal
jgebal committed Jul 13, 2019
commit ac4ca0003cad161836b8ca4ac05625428a6ae5bf
107 changes: 107 additions & 0 deletions docs/userguide/annotations.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1733,6 +1733,113 @@ When processing the test suite `test_employee_pkg` defined in [Example of annota
>
>Order of execution within multiple occurrences of `before`/`after` procedures is determined by the order of annotations in specific block (context/suite) of package specification.

## sys_context

It is possible to access information about currently running suite, test and befire/after procedure form within PLSQL procedure using SYS_CONTEXT.

The information is available by calling `sys_context( 'UT3_INFO', attribute )`.

Following attributes are populated:
- Always:
- `sys_context( 'UT3_INFO', 'RUN_PATHS' );` - list of suitepaths / suitenames used as input parameters for call to `ut.run(...)` or `ut_runner.run(...)`
- `sys_context( 'UT3_INFO', 'SUITE_DESCRIPTION' );` - the description of test suite that is currently being executed
- `sys_context( 'UT3_INFO', 'SUITE_PACKAGE' );` - the owner and name of test suite package that is currently being executed
- `sys_context( 'UT3_INFO', 'SUITE_PATH' );` - the suitepath for the test suite package that is currently being executed
- `sys_context( 'UT3_INFO', 'SUITE_START_TIME' );` - the execution start timestamp of test suite package that is currently being executed
- `sys_context( 'UT3_INFO', 'CURRENT_EXECUTABLE_NAME' );` - the owner.package.procedure of currently running test suite executable
- `sys_context( 'UT3_INFO', 'CURRENT_EXECUTABLE_TYPE' );` - the type of currently running test suite executable (one of: `beforeall`, `beforeeach`, `beforetest`, `test`, `aftertest`, `aftereach`, `afterall`

- When running in suite context
- `sys_context( 'UT3_INFO', 'CONTEXT_DESCRIPTION' );` - the description of test suite context that is currently being executed
- `sys_context( 'UT3_INFO', 'CONTEXT_NAME' );` - the name of test suite context that is currently being executed
- `sys_context( 'UT3_INFO', 'CONTEXT_PATH' );` - the suitepath for the currently executed test suite context
- `sys_context( 'UT3_INFO', 'CONTEXT_START_TIME' );` - the execution start timestamp for the currently executed test suite context
- When running a suite executable procedure that is a `test` or `beforeeach`, `aftereach`, `beforetest`, `aftertest`
- `sys_context( 'UT3_INFO', 'TEST_DESCRIPTION' );` - the description of test for which the current executable is being invoked
- `sys_context( 'UT3_INFO', 'TEST_NAME' );` - the name of test for which the current executable is being invoked
- `sys_context( 'UT3_INFO', 'TEST_START_TIME' );` - the execution start timestamp of test that is currently being executed (the time when first `beforeeach`/`beforetest` was called for that test)

Example:
```sql
create or replace procedure which_procecure_called_me is
begin
dbms_output.put_line(
'Currently running utPLSQL ' ||sys_context( 'ut3_info', 'current_executable_type' )
||' ' ||sys_context( 'ut3_info', 'current_executable_name' )
);
end;
/

create or replace package test_call is

--%suite

--%beforeall
procedure beforeall;

--%beforeeach
procedure beforeeach;

--%test
procedure test1;

--%test
procedure test2;

end;
/

create or replace package body test_call is

procedure beforeall is
begin
which_procecure_called_me();
dbms_output.put_line('Current test procedure is: '||sys_context('ut3_info','test_name'));
end;

procedure beforeeach is
begin
which_procecure_called_me();
dbms_output.put_line('Current test procedure is: '||sys_context('ut3_info','test_name'));
end;

procedure test1 is
begin
which_procecure_called_me();
ut.expect(sys_context('ut3_info','suite_package')).to_equal(user||'.test_call');
end;

procedure test2 is
begin
which_procecure_called_me();
ut.expect(sys_context('ut3_info','test_name')).to_equal(user||'.test_call.test2');
end;

end;
/
```

```sql
exec ut.run('test_call');
```

```
test_call
Currently running utPLSQL beforeall UT3.test_call.beforeall
Current test procedure is:
test1 [.008 sec]
Currently running utPLSQL beforeeach UT3.test_call.beforeeach
Current test procedure is: UT3.test_call.test1
Currently running utPLSQL test UT3.test_call.test1
test2 [.004 sec]
Currently running utPLSQL beforeeach UT3.test_call.beforeeach
Current test procedure is: UT3.test_call.test2
Currently running utPLSQL test UT3.test_call.test2

Finished in .021295 seconds
2 tests, 0 failed, 0 errored, 0 disabled, 0 warning(s)
```


## Annotation cache

Expand Down