summary refs log tree commit diff
path: root/library/test/src/formatters
AgeCommit message (Collapse)AuthorLines
2021-07-18Fix compilation errors.Charles Lew-0/+2
2021-06-17Use as_secs_f64 in JunitFormatterDeadbeef-4/+4
2021-06-06Auto merge of #84863 - ABouttefeux:libtest, r=m-ou-sebors-2/+10
Show test type during prints Test output can sometimes be confusing. For example doctest with the no_run argument are displayed the same way than test that are run. During #83857 I got the feedback that test output can be confusing. For the moment test output is ``` test $DIR/test-type.rs - f (line 12) ... ignored test $DIR/test-type.rs - f (line 15) ... ok test $DIR/test-type.rs - f (line 21) ... ok test $DIR/test-type.rs - f (line 6) ... ok ``` I propose to change output by indicating the test type as ``` test $DIR/test-type.rs - f (line 12) ... ignored test $DIR/test-type.rs - f (line 15) - compile ... ok test $DIR/test-type.rs - f (line 21) - compile fail ... ok test $DIR/test-type.rs - f (line 6) ... ok ``` by indicating the test type after the test name (and in the case of doctest after the function name and line) and before the "...". ------------ Note: this is a proof of concept, the implementation is probably not optimal as the properties added in `TestDesc` are only use in the display and does not represent actual change of behavior, maybe `TestType::DocTest` could have fields
2021-05-18change based on reviewAliénore Bouttefeux-8/+6
2021-05-16remove mode for run and ignore testsAliénore Bouttefeux-2/+12
2021-05-09add bootstrap cfgAliénore Bouttefeux-2/+2
2021-05-03change based on reviewAliénore Bouttefeux-2/+2
2021-05-03proof of concept add test type on printsAliénore Bouttefeux-2/+2
2021-04-30Better output for junit formatterAndrey Cherkashin-12/+52
2021-04-26Update junit.rsAndrey Cherkashin-1/+1
2021-04-25feat(libtest): Add JUnit formatterAndrey Cherkashin-0/+136
2021-02-21test: Print test name only once on timeoutTomasz Miąsko-4/+0
Pretty formatter when using multiple test threads displays test name twice on timeout event. This implicitly suggest that those are two different events, while in fact they are always printed together. Print test name only once. Before: ``` running 3 tests test src/lib.rs - c (line 16) ... ok test src/lib.rs - a (line 3) ... ok test src/lib.rs - b (line 9) ... test src/lib.rs - b (line 9) has been running for over 60 seconds test src/lib.rs - b (line 9) ... ok ``` After: ``` running 3 tests test src/lib.rs - c (line 16) ... ok test src/lib.rs - a (line 3) ... ok test src/lib.rs - b (line 9) has been running for over 60 seconds test src/lib.rs - b (line 9) ... ok ```
2020-11-27libtest: Print the total time taken to execute a test suiteJakob Schikowski-8/+29
2020-10-23Rollup merge of #77890 - gilescope:welformed-json-output-from-libtest, r=KodrAusYuki Okushi-4/+10
Fixing escaping to ensure generation of welformed json. doc tests' json name have a filename in them. When json test output is asked for on windows currently produces invalid json. Tracking issue for json test output: #49359
2020-10-13Replace absolute paths with relative onesest31-2/+2
Modern compilers allow reaching external crates like std or core via relative paths in modules outside of lib.rs and main.rs.
2020-10-13Fixing escaping to ensure generation of welformed json.Giles Cope-4/+10
2020-10-01Fix some clippy issuesJoshua Nelson-3/+3
Found while working on https://github.com/rust-lang/rust/pull/77351; these are just the ones that could be fixed automatically.
2020-07-27mv std libs to library/mark-0/+825