gitMirror/googletest
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

removing obsolete language from docs, CMake and Bazel is the only supporeted build methods

Browse Source
This commit is contained in:
Gennadiy Civil
2019-06-10 10:51:41 -04:00
parent 6f79a3b8a7
commit fbcb2eb200
5 changed files with 78 additions and 258 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
googletest/docs/primer.md
View File

@@ -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