summary refs log tree commit diff
path: root/src/libtest
AgeCommit message (Collapse)AuthorLines
2018-09-27Bump to 1.31.0 and bootstrap from 1.30 betaJosh Stone-1/+1
2018-09-24aarch64-pc-windows-msvc: Don't link libpanic_unwind to libtest.Michael Woerister-1/+9
2018-09-15Revert "Auto merge of #53527 - Emerentius:test_all, r=nrc"Eduard-Mihai Burtescu-119/+81
This reverts commit 9f53c87b4b1f097e111c9525d60470ed22631018, reversing changes made to cba0fdf43c22795822e1d7c751a69e6c85007221.
2018-09-15Auto merge of #53527 - Emerentius:test_all, r=nrcbors-81/+119
Add option to run all tests This adds the "--include-ignored" flag to libtest, which allows running ignored and unignored tests in one go. Closes #50363
2018-09-11stabalize infer outlives requirements (RFC 2093).toidiu-1/+0
Co-authored-by: nikomatsakis
2018-09-05rename option to run all tests and make it unstableEmerentius-12/+20
new name: --include-ignored requires -Zunstable-options
2018-09-05Auto merge of #53867 - cwndrws:json-test-formatter-test-count-as-num, r=nrcbors-2/+2
Make json test output formatter represent "test_count" as num fixes #53866
2018-09-04Introduce Custom Test FrameworksJohn Renner-2/+4
2018-08-31Make json test output formatter represent "filtered_out" as numCharlie Andrews-1/+1
2018-08-31Make json test output formatter represent "test_count" as numCharlie Andrews-1/+1
2018-08-29Replace usages of 'bad_style' with 'nonstandard_style'.Corey Farwell-1/+1
`bad_style` is being deprecated in favor of `nonstandard_style`: - https://github.com/rust-lang/rust/issues/41646
2018-08-27Auto merge of #53441 - toidiu:ak-fix53419, r=nikomatsakisbors-0/+1
fix for late-bound regions Fix for https://github.com/rust-lang/rust/issues/53419 r? @nikomatsakis
2018-08-26Rollup merge of #53428 - RalfJung:libtest-terse, r=KodrAusGuillaume Gomez-1/+5
libtest terse format: show how far in we are So for example `./x.py test src/libcore` looks like ``` running 881 tests .................................................................................................... 100/881 .................................................................................................... 200/881 .................................................................................................... 300/881 .............................................................i.i.................................... 400/881 .................................................................................................... 500/881 .................................................................................................... 600/881 .................................................................................................... 700/881 .................................................................................................... 800/881 ................................................................................. test result: ok. 879 passed; 0 failed; 2 ignored; 0 measured; 0 filtered out ``` When I am waiting for 3500 ui tests to complete, I am often missing some sense of how far in these 3500 it is. Getting the total count in `write_run_start` is a bit hacky; I did that to not change the "public interface" of the formatters. I can also give them an extra argument in their constructor so that they know from the beginning how many tests there will be. Would you prefer that? (I think I would, but I wanted to get feedback first.)
2018-08-24check that adding infer-outlives requirement to all crates worksNiko Matsakis-0/+1
2018-08-23use String::new() instead of String::from(""), "".to_string(), "".to_owned() ↵Matthias Krüger-1/+1
or "".into()
2018-08-20commentRalf Jung-1/+1
2018-08-20add option to run all testsEmerentius-46/+96
add --all flag to libtest that runs ignored and not ignored tests
2018-08-20refactor filter_testsEmerentius-43/+23
same behaviour, just shorter
2018-08-16libtest terse format: show how far in we areRalf Jung-1/+5
2018-08-15Rollup merge of #52453 - srijs:fix-52436, r=TimNNGuillaume Gomez-1/+8
improve diagnostics for tests with custom return values This is an attempt at getting the ball rolling to improve the diagnostics for test functions that return custom `impl Termination` values (see #52436). An alternative could be to use `eprintln!`, but including this in the panic message felt nicely consistent with how failing test assertions would be reported. Let me know what you think!
2018-08-11improve diagnostics for tests with custom return valuesSam Rijs-1/+8
fixes #52436
2018-08-09[nll] libtest: enable feature(nll) for bootstrapmemoryruins-0/+1
2018-07-30Auto merge of #52805 - ljedrz:format_str_literal, r=petrochenkovbors-1/+1
Don't format!() string literals Prefer `to_string()` to `format!()` take 2, this time targetting string literals. In some cases (`&format!("...")` -> `"..."`) also removes allocations. Occurences of `format!("")` are changed to `String::new()`.
2018-07-29Auto merge of #52764 - sinkuu:cleanup, r=nikomatsakisbors-2/+1
Misc cleanups
2018-07-28Don't format!() string literalsljedrz-1/+1
2018-07-27Use str::repeatShotaro Yamada-2/+1
2018-07-25Deny bare_trait_objects globallyTatsuyuki Ishi-2/+0
2018-07-12Deny bare trait objects in librustc_target and libtestljedrz-6/+9
2018-05-02Remove leftover tab in libtest outputsPhilipp Hansch-4/+4
Closes #50362
2018-04-16Add rustdoc-ui test suiteGuillaume Gomez-1/+0
2018-04-08Move deny(warnings) into rustbuildMark Simulacrum-1/+0
This permits easier iteration without having to worry about warnings being denied. Fixes #49517
2018-03-21Cargo fmt libtestSeiichi Uchida-233/+182
2018-03-10add stub for retrieving number of CPUsSebastian Humenda-0/+6
2018-02-23re-export `assert_test_result` for use when testing libtest itselfNiko Matsakis-2/+2
2018-02-22move Termination trait to std::processNiko Matsakis-1/+1
2018-02-22put the "unit test" logic into libtestNiko Matsakis-0/+9
Also make `std::termination` module public and rename feature. The lib feature needs a different name from the language feature.
2018-02-04libtest: Replace panics with error messagesGilad Naaman-4/+13
2018-01-26libtest: Failing benchmarks no longer crash the harness.Gilad Naaman-37/+91
2018-01-26libtest: Split-up formatters.rs into smaller modulesGilad Naaman-523/+776
libtest: Split HumanFormatter into {Pretty,Terse} libtest: Fixed padding of benchmarks when not benchmarking libtest: Fixed benchmarks' names not showing in terse-mode libtest: Formatting
2018-01-26libtest: rustfmt runGilad Naaman-576/+747
libtest: Whoops
2018-01-26libtest: Fixed pretty-printing of test names in single-threaded code.Gilad Naaman-36/+69
2018-01-26libtest: JSON formatting is now only available in unstable buildsGilad Naaman-2/+36
libtest: Added the -Z option for unstable options
2018-01-26Added JSON output to libtest.Gilad Naaman-50/+312
libtest: Json format now outputs failed tests' stdouts. libtest: Json format now outputs failed tests' stdouts. libtest: Json formatter now spews individiual events, not as an array libtest: JSON fixes libtest: Better JSON escaping libtest: Test start event is printed on time
2018-01-26Refactoring needed in order to have test json output.Gilad Naaman-232/+308
2018-01-11Make libtest build on CloudABI.Ed Schouten-8/+9
Just like on UNIX systems, we need to use sysconf() to obtain the number of CPUs. Extend the existing cfg()'s to match CloudABI as well.
2018-01-03Restore a FIXME that was removed by one of my previous changes.Ed Schouten-0/+1
Requested by: kennytm
2018-01-02Provide a copy of stdout_isatty() on CloudABI.Ed Schouten-6/+3
CloudABI doesn't make any distinction between TTYs and ordinary pipes. While there, remove the redundant implementation used by Redox. It can use the same stub function.
2018-01-02Auto merge of #47106 - EdSchouten:compiletest-cloudabi, r=alexcrichtonbors-7/+0
Tiny fixes to make compiletest work for CloudABI cross builds I'm currently working toward getting a `src/ci/docker` container working to do isolated/automated builds and testing of `x86_64-unknown-cloudabi`. This is working pretty well, but still requires some fixes to `libtest` and `compiletest`. Here is the first set of fixes that I had to apply.
2018-01-01Move the TestPaths structure from libtest to compiletest.Ed Schouten-7/+0
This structure doesn't seem to be used by libtest itself. It is used by compiletest, but never passed on to anything externally. This makes it easier to get the testing framework to work for CloudABI crossbuilds, as CloudABI currently lacks PathBuf, which is used by TestPaths.
2018-01-01Fix docs for future pulldown migrationMalo Jaffré-9/+9
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-26 19:31:30 +0000