GeezerVison

Added ability to run expectations without tests

Expectation, when executed without test, reports results straight to dbms_output.

So it is now possible to execute:
exec ut.expect(1).to_equal(0);

And get result:

FAILURE
  Actual: 1 (number) was expected to equal: 0 (number)

Resolves #956

Improvements to application_info in v$session

utPLSQL is now cleaning up the application_info after run. The module_name, action, client_info` are restored to it's original values after test run. Resolves #951

The following attributes are set in v$session when test suite is running:

• module_name - set to utPLSQL
• action - name of currently executing test suite package
• client_info name of test executable procedure (before.../after.../test) that is currently running

Setting session context during run

It is now possible to access some of utPLSQL info within the test procedures directly.
Resolves #781

The information is provided in sys_context( 'UT3_INFO', attribute ).

Following attributes are getting 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)

Call stack enchancements

utPLSQL will now provide full call stack within the context of the test, not only the stack line where expectation was called.
To minimize overhead on test execution, stack is provided only when expectation fails.

Resolves #967

Improved functionality of reporters

Reporters will now support inline calls for data-retrieval.
References #955