utPLSQL-Version: 3.1.9
Consider the following test-suite with nested-contexts:
create or replace package ut_context_test as
-- %suite(Context Test)
-- %suitepath(context)
-- %context(Level 1)
-- %context(Level 1.1)
-- %test(Test 1.1.1)
procedure test_1_1_1;
-- %test(Test 1.1.2)
procedure test_1_1_2;
-- %endcontext
-- %endcontext
-- %context(Level 2)
-- %test(Test 2.1)
procedure test_2_1;
-- %endcontext
end;
/Expectation would be:
context
Context Test
Level 1
Level 1.1
Test 1.1.1 [,016 sec] (FAILED - 2)
Test 1.1.2 [,005 sec] (FAILED - 3)
Level 2
Test 2.1 [,016 sec] (FAILED - 1)
But at the moment it's interpreted like that:
context
Context Test
Level 1
Level 2
Test 2.1 [,016 sec] (FAILED - 1)
Level 1.1
Test 1.1.1 [,016 sec] (FAILED - 2)
Test 1.1.2 [,005 sec] (FAILED - 3)
It looks like consecutive %endcontext are not interpreted correctly so that termination doesn't happen at the correct time/place
utPLSQL-Version: 3.1.9
Consider the following test-suite with nested-contexts:
Expectation would be:
But at the moment it's interpreted like that:
It looks like consecutive
%endcontextare not interpreted correctly so that termination doesn't happen at the correct time/place