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

Cannot hide verbose output from test results #615

Open
alerque opened this issue Oct 10, 2019 · 2 comments
Open

Cannot hide verbose output from test results #615

alerque opened this issue Oct 10, 2019 · 2 comments

Comments

@alerque
Copy link
Member

alerque commented Oct 10, 2019

I'm running > 250 tests which compare large table structures (ASTs) using assert.same(expected, actual). The tests work great and the deep compare actually does the correct thing in this case. The problem is the output is so verbose when they fail that it's very difficult to make sense of it.

I've tried running with --no-verbose but large chunks of both the expected and actual tables are still dumped to the output (and as this is the default that wasn't really a surprise). Likewise -o gtest and -o tap both do the same thing as well.

I would like some way to suppress the expected vs. actual output and just note which test failed.

@Tieske
Copy link
Member

Tieske commented Oct 10, 2019

there is no easy fix for this. There have been thoughts to add some sort of diffing output handler to do this, but that was never implemented

@alerque
Copy link
Member Author

alerque commented Oct 11, 2019

@Tieske I'm wondering if I didn't communicate clearly what I was after. In this case I don't care about a nice diffed output, I want no output at all. I just want the name of the failed test (as specified by it(), etc.). I actually have an external tool to do diffs (by dumping all the Lua arrays to JSON, using a special sort algoryth, then comparing the trees). All I want from busted is a pass/fail list without all the noise about what it thinks is different. It actually seems like that should be an easy fix or even something already implemented that I'm just missing.

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

No branches or pull requests

2 participants