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

Run all tests from a single test runner #2075

Closed
brson opened this issue Mar 29, 2012 · 3 comments
Closed

Run all tests from a single test runner #2075

brson opened this issue Mar 29, 2012 · 3 comments
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot.

Comments

@brson
Copy link
Contributor

brson commented Mar 29, 2012

People see the results of the final test run and think, "oh, good, 71 tests passed", but there are thousands of tests, and it would be nice to see all results at once. Difficult to implement though.

@grahame
Copy link
Contributor

grahame commented Mar 31, 2012

I've been thinking about this one. How about adding an option to the test framework to write out the test results to a file, in some serialised format. "make check" could then write each of these out to a file (which is cleaned by make clean), and then at the end run a python script to read them all in and summarise.

I'm happy to do this work if this design is sound?

@brson
Copy link
Contributor Author

brson commented Apr 2, 2012

I am ok with this.

In the long term I would for it all to be done in rust, but that requires getting dynamic loading working so that we can have one test runner load tests from multiple crates.

brson pushed a commit that referenced this issue Apr 4, 2012
Add an optional --logfile argument to std::test::test_main and to
compiletest.

Use this features and the new 'check-summary.py' script to
summarise all the tests performed by the 'check' target. This is
a short term fix for #2075.
@ghost ghost assigned brson Apr 5, 2012
@z0w0
Copy link
Contributor

z0w0 commented Apr 23, 2013

This appears to have been fixed in said pull request a while ago. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-testsuite Area: The testsuite used to check the correctness of rustc E-hard Call for participation: Hard difficulty. Experience needed to fix: A lot.
Projects
None yet
Development

No branches or pull requests

3 participants