diff options
| author | Gennadiy Civil <misterg@google.com> | 2019-06-10 14:51:41 (GMT) |
|---|---|---|
| committer | Gennadiy Civil <misterg@google.com> | 2019-06-10 14:51:41 (GMT) |
| commit | fbcb2eb2004dcc581e637b14e07cc4ed5820e9f5 (patch) | |
| tree | d80a6430f477bcc25ddacadc9496979f5922466e /googletest/docs/primer.md | |
| parent | 6f79a3b8a7dce9e2fd883ef50c9f36161ff9e9d3 (diff) | |
| download | googletest-fbcb2eb2004dcc581e637b14e07cc4ed5820e9f5.zip googletest-fbcb2eb2004dcc581e637b14e07cc4ed5820e9f5.tar.gz googletest-fbcb2eb2004dcc581e637b14e07cc4ed5820e9f5.tar.bz2 | |
removing obsolete language from docs, CMake and Bazel is the only supporeted build methods
Diffstat (limited to 'googletest/docs/primer.md')
| -rw-r--r-- | googletest/docs/primer.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/googletest/docs/primer.md b/googletest/docs/primer.md index fb96cdf..10284f8 100644 --- a/googletest/docs/primer.md +++ b/googletest/docs/primer.md @@ -24,8 +24,8 @@ So what makes a good test, and how does googletest fit in? We believe: projects and start to work on a new code base. 1. Tests should be *portable* and *reusable*. Google has a lot of code that is platform-neutral, its tests should also be platform-neutral. googletest - works on different OSes, with different compilers (gcc, icc, and MSVC), with - or without exceptions, so googletest tests can easily work with a variety of + works on different OSes, with different compilers, with + or without exceptions, so googletest tests can work with a variety of configurations. 1. When tests fail, they should provide as much *information* about the problem as possible. googletest doesn't stop at the first test failure. Instead, it |