Skip to content
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

Do not modify stack trace of JestAssertionError #4516

Merged
merged 4 commits into from
Sep 20, 2017

Conversation

denniske
Copy link
Contributor

@denniske denniske commented Sep 20, 2017

Summary
Fixes #4515

Test plan

No test plan yet.

@denniske denniske changed the title Do not modify stack trace of JestAssertionError. Do not modify stack trace of JestAssertionError Sep 20, 2017
@codecov-io
Copy link

codecov-io commented Sep 20, 2017

Codecov Report

Merging #4516 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master    #4516   +/-   ##
=======================================
  Coverage   56.83%   56.83%           
=======================================
  Files         186      186           
  Lines        6306     6306           
  Branches        3        3           
=======================================
  Hits         3584     3584           
  Misses       2721     2721           
  Partials        1        1

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 246da7f...7433b98. Read the comment docs.

@denniske
Copy link
Contributor Author

Added tests.

@cpojer cpojer merged commit fbacd19 into jestjs:master Sep 20, 2017
@cpojer
Copy link
Member

cpojer commented Sep 20, 2017

Thanks for sending a PR!

tabrindle pushed a commit to tabrindle/jest that referenced this pull request Oct 2, 2017
* Do not modify stack trace of JestAssertionError.

* Added test for stack trace of nested matchers.

* Fixed test for nested matcher and added test for normal matchers.

* Only comparing line numbers in test because function names in stack trace seem to be platform dependent.
@github-actions
Copy link

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

StackTrace is cut when nesting matchers
4 participants