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

Skip to content

Fixed stack parsing when test failed with ut.fail #380

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 13 commits into from
Jul 4, 2017
Merged

Fixed stack parsing when test failed with ut.fail #380

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
40ba680
Fixed stack parsing when test failed with `ut.fail` or by broken expe…
Pazus Jul 1, 2017
24ac6dc
Merge branch 'develop' into issue-378
Pazus Jul 2, 2017
a326d74
Merge branch 'develop' into issue-378
Pazus Jul 2, 2017
953551c
fixed pattern for 11g and 12.1
Pazus Jul 3, 2017
1093394
Merge branch 'develop' into issue-378
Pazus Jul 3, 2017
01b59b4
take into account utassert and utassert2 packages from migration project
Pazus Jul 3, 2017
4ae671f
simplified pattern
Pazus Jul 3, 2017
88a0b83
test
Pazus Jul 4, 2017
10796ff
Merge branch 'develop' into issue-378
Pazus Jul 4, 2017
a90a408
try fix
Pazus Jul 4, 2017
a00ba91
removed debugging info
Pazus Jul 4, 2017
2c168f2
Merge branch 'develop' into issue-378
jgebal Jul 4, 2017
6fd6eff
Merge branch 'develop' into issue-378
Pazus Jul 4, 2017
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
Next Next commit
try fix
  • Loading branch information
@Pazus
Pazus authored Jul 4, 2017
commit a90a408db6a896414fd1ef98ff0260945cff8fb7
2 changes: 1 addition & 1 deletion source/core/ut_expectation_processor.pkb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,7 +130,7 @@ create or replace package body ut_expectation_processor as
-- in 12.2 format_call_stack reportes not only package name, but also the procedure name
-- when 11g and 12c reports only package name
c_expectation_search_pattern constant varchar2(500) :=
'(^.*\.(UT_EXPECTATION[A-Z0-9#_$]*|UT|UTASSERT2?)(\.[A-Z0-9#_$]+)?$\s)+(.*)';
'(.*\.(UT_EXPECTATION[A-Z0-9#_$]*|UT|UTASSERT2?)(\.[A-Z0-9#_$]+)?\s+)+(.*)';
begin
dbms_output.put_line(c_call_stack);
l_caller_stack_line := regexp_substr( c_call_stack, c_expectation_search_pattern, 1, 1, 'm', 4);
Expand Down