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 UX: High noise to signal ratio in test output for large workspaces. #9952

Closed
gilescope opened this issue Oct 1, 2021 · 2 comments
Closed
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`

Comments

@gilescope
Copy link
Contributor

rust workspaces are getting bigger and if I run a named test I get this kind of thing:

<snip>
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 3 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_consensus_pow-ebde30e7fc601f52)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_consensus_slots-8c4f89b5b5023e60)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 12 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_consensus_uncles-ccf4803c4c0275c7)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_executor-f162d5c03810b699)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 81 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_executor_common-b31f7a1b0538b32d)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_executor_wasmi-26dded16175b1765)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_executor_wasmtime-aafc61ecf1051687)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 3 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_finality_grandpa-5e29a0a4b6779109)

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 78 filtered out; finished in 0.00s

     Running unittests (target/debug/deps/sc_finality_grandpa_rpc-0cf104be186ce752)

running 0 tests
<snip>

There's screen fulls of this.

Somewhere in the pages of output is my test that was run....

The feature request: Can we have a better UX please?

E.g. could we have a --condenced flag we could use to see more consolidated results because we like tests, lots of tests are good, but the UX could be improved.

Requests like this are what success looks like - it's a good thing :-)

@gilescope gilescope added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Oct 1, 2021
@Eh2406
Copy link
Contributor

Eh2406 commented Oct 1, 2021

I'd love to see experimentation with this in a third party sub command. When there is a format that is widely used, we can bring it into Cargo.

@ehuss
Copy link
Contributor

ehuss commented Oct 1, 2021

Yea, I agree it would be nice to have a cleaner summary and output. I'm going to close this as a duplicate of #4324 and #2832.

@ehuss ehuss closed this as completed Oct 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted`
Projects
None yet
Development

No branches or pull requests

3 participants