| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
Add --gtest_fail_fast support to googletest.
- Analogous functionality to to golang -test.failfast and python --failfast
- Stops test execution upon first test failure.
- Also add support Bazel equivalent env var (TESTBRIDGE_TEST_RUNNER_FAIL_FAST)
PiperOrigin-RevId: 302488880
|
|
|
|
|
|
| |
Add documentation for ASSERT_DEBUG_DEATH/EXPECT_DEBUG_DEATH
PiperOrigin-RevId: 292138974
|
|
|
|
|
|
| |
Fix SCOPED_TRACE() message header in example
PiperOrigin-RevId: 290800241
|
|
|
|
|
|
| |
Correct the spelling of PARAMETERIZED.
PiperOrigin-RevId: 289897278
|
|
|
|
|
|
|
|
|
|
| |
Add GTEST_ALLOW_UNINSTANTIATED_PARAMTERIZED_TEST to mark a paramaterized test as allowed to be un-instantiated.
This allows test suites, that are defined in libraries and, for other reasons, get linked in (which should probably be avoided, but isn't always possible) to be marked as allowed to go uninstantiated.
This can also be used to grandfather existing issues and expedite adoption of the checks with regards to new cases before they can be fixed.
PiperOrigin-RevId: 289581573
|
|
|
|
|
|
| |
Update example Environment class destructor annotation
PiperOrigin-RevId: 283986183
|
|
|
|
|
|
| |
Fix typo in the predicate assertion table.
PiperOrigin-RevId: 281973457
|
|
|
|
|
|
|
|
| |
Split the scoped trace examples into two snippets.
This doesn't have an effect in the github markdown renderer, but in some other renderers/templates, this leads them to be independently copy-pastable. In particular, the markdown rendering that Google uses internally has a copy button for each code snippet, which, before this change, would copy both lines. Bad copy button, no cookie! After this change, there will be two such buttons, one per line, and clicking a copy button will copy only the one snippet it is next to, and not the other. This is desirable because nobody will ever want to copy both lines, only one or the other.
PiperOrigin-RevId: 276079009
|
|
|
|
|
|
| |
Typo in Registering tests programmatically section. Changed "were" to "where".
PiperOrigin-RevId: 276060801
|
|\
| |
| |
| | |
PiperOrigin-RevId: 273585026
|
| |
| |
| |
| |
| | |
This fixes up f2fb48c3 (a manual merge) that has abandoned some things
from PR #2407.
|
|/ |
|
|
|
|
|
|
|
|
|
| |
Merge 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd into fb49e6c164490a227bbb7cf5223b846c836a0305
Closes #2407
COPYBARA_INTEGRATE_REVIEW=https://github.com/google/googletest/pull/2407 from kuzkry:StaticAssertTypeEq 3bdefdb473d304803d2a38e2a2cd5cdc1827c3bd
PiperOrigin-RevId: 269255328
|
|
|
|
|
|
| |
Internal change, documentation only.
PiperOrigin-RevId: 262554386
|
|\
| |
| |
| | |
PiperOrigin-RevId: 261340959
|
| | |
|
|/
|
|
|
|
| |
Add links to "sampleK_unittest.cc" examples. Fix some broken docs crosslinks.
PiperOrigin-RevId: 261169561
|
|\
| |
| |
| | |
PiperOrigin-RevId: 260782065
|
| | |
|
|\ \
| |/
|/|
| | |
PiperOrigin-RevId: 260559531
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
merge docs internal-OSS
|
|
|
|
| |
merge docs internal-OSS
|
| |
|
| |
|
| |
|
|
|
|
| |
for including documentation in sync process
|
|
|
|
| |
build methods
|
|
|
| |
Adding back section that was lost in merge
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtest prior to this change would completely ignore `GTEST_SKIP()` if
called in `Environment::SetUp()`, instead of bailing out early, unlike
`Test::SetUp()`, which would cause the tests themselves to be skipped.
The only way (prior to this change) to skip the tests would be to
trigger a fatal error via `GTEST_FAIL()`.
Desirable behavior, in this case, when dealing with
`Environment::SetUp()` is to check for prerequisites on a system
(example, kernel supports a particular featureset, e.g., capsicum), and
skip the tests. The alternatives prior to this change would be
undesirable:
- Failing sends the wrong message to the test user, as the result of the
tests is indeterminate, not failed.
- Having to add per-test class abstractions that override `SetUp()` to
test for the capsicum feature set, then skip all of the tests in their
respective SetUp fixtures, would be a lot of human and computational
work; checking for the feature would need to be done for all of the
tests, instead of once for all of the tests.
For those reasons, making `Environment::SetUp()` handle `GTEST_SKIP()`,
by not executing the testcases, is the most desirable solution.
In order to properly diagnose what happened when running the tests if
they are skipped, print out the diagnostics in an ad hoc manner.
Update the documentation to note this change and integrate a new test,
gtest_skip_in_environment_setup_test, into the test suite.
This change addresses #2189.
Signed-off-by: Enji Cooper <yaneurabeya@gmail.com>
|
|
|
| |
Co-Authored-By: antismap <michael.thenault@gmail.com>
|
|
|
| |
See https://github.com/google/googletest/issues/2065
|
|
|
|
|
|
|
| |
This is just a mistake in the document. Google Test doesn't output
such an invalid JSON report.
Signed-off-by: Keiichi Watanabe <keiichiw@chromium.org>
|
|
|
| |
Testing
|
| |
|
|
|
| |
Fixes #1802
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
- Fix some format issue
|
| |
|
| |
|
| |
|
|
|
| |
Part of documentation rationalization
|
|
Part of documentation rationalization work
|