-
Notifications
You must be signed in to change notification settings - Fork 185
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm thinking.
When we use migration (with utassert
and utassert2
rewritten), we face the same issue.
Should we include those two in the stacktrace search?
What do you think @Pazus
Changes Unknown when pulling a326d74 on Pazus:issue-378 into ** on utPLSQL:develop**. |
2 similar comments
@@ -0,0 +1,41 @@ | |||
set termout off |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test is failing on 11g:
https://travis-ci.org/utPLSQL/utPLSQL/jobs/249332892#L3583
And on 12.1:
https://travis-ci.org/utPLSQL/utPLSQL/jobs/249332893#L3565
2 similar comments
1 similar comment
1 similar comment
1 similar comment
2 similar comments
### Documentation #399 Documentation now refers to [migration](https://github.com/utPLSQL/utPLSQL-v2-v3-migration) project #386 Documentation now refers to a valid object name: `ut_file_mapping` #362 Install and Uninstall scripts are now much more readable #361 Install guide now provides snippet on how to download latest release on Windows ### Installation #396 Added override user/password/tablespace for install_headless #384 Installation is now smooth even if profiler tables already exist ### Internal improvements #388 Improved reporting from RunTest #363 Fixed publishing of release documentation history ### Improvements and fixes #407 Fixed rare issue with `ORA-22813: operand value exceeds system limits` #403 Stack trace is now properly parsed on all machines #397 The `--%disabled` annotation on suite level is now reporting all tests as disabled #395 Coverage reporting is now properly filtering test packages on that use suitepath #390 Line of code for failed expectation is now also shown for unit tests owned by other users #380 Line no of failed test is now properly reported when using `ut.fail` #375 Annotation parameter list can now have spaces before/after brackets #373 Warnings in documentation reporter are now properly numbered #372 Documentation reporter is now providing a timing information for each test #370 by xUnit reporter now displays name of the package/procedure if suite/test has no description #369 Fixed errors with multi-byte characters in conversion from/to clob
Fixed stack parsing when test failed with
ut.fail
or by broken expectationAddress #378