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

Explain how to execute a single UI test #2459

Merged
merged 1 commit into from Feb 20, 2018

Conversation

Projects
None yet
3 participants
@phansch
Collaborator

phansch commented Feb 13, 2018

This adds a section to Running test suite that explains how to run a single test file.

On my old machine it took a few minutes for the whole suite to finish and running a single test is useful to have a shorter feedback loop, even on a faster machine.

@phansch

This comment has been minimized.

Collaborator

phansch commented Feb 13, 2018

I'm just not sure if this section should mention that the command doesn't work on files that depend on other crates. For example TESTNAME=ui/regex cargo test --test compile-test would fail.

@bootandy

This comment has been minimized.

Contributor

bootandy commented Feb 16, 2018

This is a good idea. I was wondering how to do that myself. (I was just deleting all the other ui tests in the directory)

@oli-obk

This comment has been minimized.

Collaborator

oli-obk commented Feb 20, 2018

I'm just not sure if this section should mention that the command doesn't work on files that depend on other crates.

Curious. I wonder if anyone ever noticed that in the compiler test suite :D

@oli-obk oli-obk merged commit a7407f9 into rust-lang:master Feb 20, 2018

2 checks passed

continuous-integration/appveyor/pr AppVeyor build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@phansch phansch deleted the phansch:mention_how_to_run_single_test branch Feb 20, 2018

@phansch

This comment has been minimized.

Collaborator

phansch commented Feb 20, 2018

Wait, with the latest Rust release, incremental compilation is now on by default right? There is also rust-lang/cargo#4817 which enabled incremental compilation in cargo by default, so I think CARGO_INCREMENTAL=1 is not needed anymore. I will test it later at home though, and make a PR to remove that part again :)

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