diff options
| author | Abseil Team <absl-team@google.com> | 2019-10-22 10:33:51 -0400 |
|---|---|---|
| committer | Gennadiy Civil <misterg@google.com> | 2019-10-22 10:54:55 -0400 |
| commit | f1afeaa6434812276d106c161f09bf9351a47d39 (patch) | |
| tree | 0b1d82d2cb434ad3ffdfad1357404171f3d54133 | |
| parent | 8c91ecef292e963d23cd5b25f01ea1579fbe9aaa (diff) | |
| download | googletest-f1afeaa6434812276d106c161f09bf9351a47d39.tar.gz googletest-f1afeaa6434812276d106c161f09bf9351a47d39.tar.bz2 googletest-f1afeaa6434812276d106c161f09bf9351a47d39.zip | |
Googletest export
Typo in Registering tests programmatically section. Changed "were" to "where".
PiperOrigin-RevId: 276060801
| -rw-r--r-- | googletest/docs/advanced.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/googletest/docs/advanced.md b/googletest/docs/advanced.md index 179118dc..5c34d262 100644 --- a/googletest/docs/advanced.md +++ b/googletest/docs/advanced.md @@ -1803,7 +1803,7 @@ For technical reasons, there are some caveats: ## Registering tests programmatically The `TEST` macros handle the vast majority of all use cases, but there are few -were runtime registration logic is required. For those cases, the framework +where runtime registration logic is required. For those cases, the framework provides the `::testing::RegisterTest` that allows callers to register arbitrary tests dynamically. |