summaryrefslogtreecommitdiffstats
path: root/googletest/test/gtest_xml_output_unittest.py
Commit message (Collapse)AuthorAgeFilesLines
* Export testsuite properties as XML elements, not attributes.Abseil Team2025-01-311-43/+45
| | | | | | | | With this change, arbitrary property names in the testsuite no longer cause the produced XML output to be ill-formed. PiperOrigin-RevId: 721549090 Change-Id: Iedffa89bf914478f563c8f3b82cd50557762a665
* gtest: Output a canned test case for test suite setup / teardown failures in ↵Abseil Team2024-12-261-13/+52
| | | | | | | | | | | XML/JSON This surfaces useful information about the environment failure in a structured form. As we can see from the updated test, previously unsurfaced information is now present. PiperOrigin-RevId: 709892315 Change-Id: I2656294d50c33f995bef5c96195a66cff3c4b907
* Do not emit stack traces for messages generated by GTEST_SKIP()Abseil Team2024-01-161-6/+9
| | | | | | | | | | | | | | | | | | | | Stack traces in assertion failures are an extremely useful tool for developers tasked with investigating failing tests. It's difficult to understate this. In contrast to ordinary test assertions (e.g., ASSERT_TRUE or EXPECT_FALSE), GTEST_SKIP is a developer-authored directive to skip one or more tests. Stack traces emitted in skip messages do not give the developer useful information, as the skip message itself contains the code location where GTEST_SKIP was used. In addition to being noise in the output, symbolization of stack traces is not free. In some Chromium configurations, symbolization in a skipped test can incur a cost in excess of 25 seconds for a test that otherwise takes 0-1ms; see https://crbug.com/1517343#c9. In this CL, we suppress generation and emission of stack traces for kSkip messages to reduce the output noise and overhead of GTEST_SKIP(). PiperOrigin-RevId: 598899010 Change-Id: I46926fed452c8d7edcb3d636d8fed42cb6c0a9e9
* Add missing std includesTom Hughes2023-04-201-30/+30
| | | | | PiperOrigin-RevId: 525794940 Change-Id: Ib2639058610c91cbffbb0f22a5e71573e0cbd651
* gtest.cc: add a newline after a failure when there is no OS stack trace.Aaron Jacobs2023-03-231-13/+17
| | | | | | | | This makes the behavior consistent when GTEST_STACK_TRACE_DEPTH is set to zero and not: there is always vertical whitespace separating failure messages. PiperOrigin-RevId: 518744611 Change-Id: I5b4af40633849850660504c3f497a76601d4311d
* Fix formatting in Python filesTom Hughes2023-01-261-34/+61
| | | | | PiperOrigin-RevId: 504890435 Change-Id: Ia9a89d0d7a07fe70c12f7f0202c8256c94d2f118
* Fix Python docstrings to match style guideTom Hughes2023-01-261-8/+26
| | | | | | | https://google.github.io/styleguide/pyguide.html#s3.8.3-functions-and-methods PiperOrigin-RevId: 504857416 Change-Id: I7815ce27e454a120b3974ae7e2bea952108b836c
* Use more specific assertLess instead of assertTrueTom Hughes2023-01-251-2/+1
| | | | | PiperOrigin-RevId: 504670738 Change-Id: Ib68b676403204098e89f536f9b8317f9f717c24d
* Replace deprecated python callsTom Hughes2023-01-171-16/+22
| | | | | | | | assert_ -> assertTrue/assertFalse/assertIn/assertNotIn assertEquals -> assertEqual PiperOrigin-RevId: 502654909 Change-Id: I25d30095a83c3806606cb80d676b3c979495e6bd
* Adjust xml and json unit tests to test for source file and line location.Szymon Sobik2022-03-081-30/+30
|
* Makes the Python imports consistently use full paths from the repository root,Derek Mauro2021-12-221-2/+2
| | | | | | | | | unifying the behavior between Bazel and CMake This fixes one of the CI failures on Windows PiperOrigin-RevId: 417872531 Change-Id: I156989323b7e6d4a4420f4f9691b078829db933d
* Googletest exportAbseil Team2021-03-161-6/+16
| | | | | | | | | | gtest: Output a canned test suite for environment failures in XML/JSON This surfaces useful information about the environment failure in a structured form. As we can see from the updated test, previously unsurfaced information is now present. PiperOrigin-RevId: 362292322
* Fix test with stack.refs/pull/2767/headMario Voorsluys2020-04-221-3/+3
|
* Fixed xml unit-tests and added extra testsMario Voorsluys2020-03-261-23/+39
| | | | | The extra tests check that the xml output is correct when a failure occurs before skipping, and that the right skip message is added to the file. The json file had to be fixed because it's the same executable.
* Googletest exportAbseil Team2019-07-261-46/+46
| | | | | | | | Adds ISO8601 timestamps to XML output and RFC3339 timestamps to JSON output. Adds timestamps to testsuites, testsuite and testcases structured JSON/XML output for better reporting how/where time is spent on tests. PiperOrigin-RevId: 260039817
* Googletest exportAbseil Team2019-03-281-29/+31
| | | | | | Update XML and JSON output to be consistent with the standard. PiperOrigin-RevId: 239833242
* Googletest exportmisterg2019-01-111-6/+6
| | | | | | Change tests to use new Test Suite API PiperOrigin-RevId: 228908894
* Googletest exportAbseil Team2018-12-131-8/+11
| | | | | | Support skipped in XML and JSON output PiperOrigin-RevId: 225386540
* Fix Python3 supportPeter Levine2018-09-141-1/+2
|
* Adds stacktrace support from Abseil to Google TestDerek Mauro2018-07-101-1/+6
| | | | | | | | | | | | | | | | | | | This change adds the ability to generate stacktraces in Google Test on both failures of assertions/expectations and on crashes. The stacktrace support is conditionally available only when using Abseil with Google Test. To use this support, run the test under Bazel with a command like this: bazel test --define absl=1 --test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1 //path/to/your:test The "--define absl=1" part enables stacktraces on assertion/expectation failures. The "--test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1" part enables the signal handler that logs a stacktrace in the event of a crash (this also requires the "--define absl=1" part). This is not the default since it may interfere with existing tests.
* Merging, XML testsrefs/pull/1497/headGennadiy Civil2018-03-071-8/+42
|
* more code mergeGennadiy Civil2018-01-221-3/+1
|
* merges, cl/155419551 and otherGennadiy Civil2018-01-221-10/+45
|
* Make the failure messages from EXPECT_EQ and friends actually symmetric,refs/pull/1242/headAlexey Sokolov2017-09-131-9/+12
| | | | | | | instead of reading more like reversing the former "expected" and "actual" roles of the LHS and RHS arguments. This patch is manually applied from internal version (125109873)
* Fixed some typosrefs/pull/1030/headvpfautz2017-02-261-1/+1
|
* Change error message of EXPECT_EQ to treat lhs and rhs equivalently.refs/pull/713/headAlexey Sokolov2016-02-161-9/+9
|
* add python 3 support to testsThomas Amland2016-01-191-1/+2
|
* Move everything in googletest into googletest/googletestBilly Donahue2015-08-251-0/+307
generated by cgit v0.12 at 2025-04-26 05:28:55 (GMT)