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.

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

Conversation

Pazus
Copy link
Member

@Pazus Pazus commented Jul 1, 2017

Fixed stack parsing when test failed with ut.fail or by broken expectation
Address #378

@Pazus Pazus added the bugfix label Jul 1, 2017
@Pazus Pazus added this to the v3.0.2 milestone Jul 1, 2017
@Pazus Pazus self-assigned this Jul 1, 2017
@coveralls
Copy link

coveralls commented Jul 1, 2017

Coverage Status

Coverage increased (+0.08%) to 91.789% when pulling 40ba680 on Pazus:issue-378 into 021eead on utPLSQL:develop.

Copy link
Member

@jgebal jgebal left a 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

@coveralls
Copy link

coveralls commented Jul 2, 2017

Coverage Status

Changes Unknown when pulling a326d74 on Pazus:issue-378 into ** on utPLSQL:develop**.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling a326d74 on Pazus:issue-378 into ea2573e on utPLSQL:develop.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling a326d74 on Pazus:issue-378 into ea2573e on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling a326d74 on Pazus:issue-378 into ea2573e on utPLSQL:develop.

@@ -0,0 +1,41 @@
set termout off
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 953551c on Pazus:issue-378 into ea2573e on utPLSQL:develop.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 953551c on Pazus:issue-378 into ea2573e on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 953551c on Pazus:issue-378 into ea2573e on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 3, 2017

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 1093394 on Pazus:issue-378 into ce2d8ad on utPLSQL:develop.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 1093394 on Pazus:issue-378 into ce2d8ad on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 3, 2017

Coverage Status

Coverage decreased (-0.2%) to 91.554% when pulling 01b59b4 on Pazus:issue-378 into ce2d8ad on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 3, 2017

Coverage Status

Coverage decreased (-0.2%) to 91.554% when pulling 4ae671f on Pazus:issue-378 into ce2d8ad on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.2%) to 91.626% when pulling 10796ff on Pazus:issue-378 into f92772f on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.2%) to 91.871% when pulling a90a408 on Pazus:issue-378 into f92772f on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 4, 2017

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling a00ba91 on Pazus:issue-378 into f92772f on utPLSQL:develop.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling a00ba91 on Pazus:issue-378 into f92772f on utPLSQL:develop.

@coveralls
Copy link

coveralls commented Jul 4, 2017

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 2c168f2 on Pazus:issue-378 into 15a0922 on utPLSQL:develop.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 2c168f2 on Pazus:issue-378 into 15a0922 on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 6fd6eff on Pazus:issue-378 into 380ff54 on utPLSQL:develop.

2 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 6fd6eff on Pazus:issue-378 into 380ff54 on utPLSQL:develop.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.08%) to 91.799% when pulling 6fd6eff on Pazus:issue-378 into 380ff54 on utPLSQL:develop.

@jgebal jgebal merged commit eab7ad9 into utPLSQL:develop Jul 4, 2017
@jgebal jgebal removed the in progress label Jul 4, 2017
@Pazus Pazus deleted the issue-378 branch July 15, 2017 09:47
Pazus added a commit that referenced this pull request Jul 18, 2017
### 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants