Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
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
%endcontext
The text was updated successfully, but these errors were encountered:
I think I can fix this.
Sorry, something went wrong.
Skip as many %endcontext as nested %context annotations
e8f4532
We need to make sure to calculate the corrent %endcontext annotation, not just the first that is greater than the next nested %context. To operate correctly during recursion we also need information about the parent %endcontext position Fixes #1034
pesse
Successfully merging a pull request may close this issue.
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
%endcontext
are not interpreted correctly so that termination doesn't happen at the correct time/placeThe text was updated successfully, but these errors were encountered: