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

test: use verbose spec reporter #778

Merged
merged 1 commit into from
Jul 14, 2019

Conversation

brodybits
Copy link
Contributor

No description provided.

Co-authored-by: Christopher J. Brody <chris@brody.consulting>
Co-authored-by: Raphael von der Grün <raphinesse@users.noreply.github.com>
@codecov-io
Copy link

codecov-io commented Jul 14, 2019

Codecov Report

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

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #778   +/-   ##
=======================================
  Coverage   66.57%   66.57%           
=======================================
  Files          18       18           
  Lines        1822     1822           
=======================================
  Hits         1213     1213           
  Misses        609      609

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 38c6627...0b50f78. Read the comment docs.

@brodybits brodybits marked this pull request as ready for review July 14, 2019 19:02
@brodybits brodybits changed the title test: use verbose spec reporter [WIP] test: use verbose spec reporter Jul 14, 2019
@brodybits brodybits changed the title [WIP] test: use verbose spec reporter test: use verbose spec reporter Jul 14, 2019
@brodybits brodybits merged commit 989b4cc into apache:master Jul 14, 2019
@brodybits brodybits deleted the verbose-spec-reporter branch July 14, 2019 19:36
@brodybits
Copy link
Contributor Author

Now merged. The one thing is that for some reason, I do not see the details in case of any test failures. The workaround is to remove the “helpers” item from a JSON file if I need to see such error details. Any input would be much appreciated.

@raphinesse
Copy link
Contributor

raphinesse commented Jul 16, 2019

@brodybits I could reproduce the described behavior and I think I have isolated the cause. Working on a fix for it now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants