gecko-dev/security/pkix/test/gtest
Masatoshi Kimura 3b21b7868b Bug 1090497 - Re-enable warnings as errors on clang-cl. r=froydnj
--HG--
extra : rebase_source : c09366fb93e5b0f72abe1e99d3094e3d96a934fb
extra : intermediate-source : 5950c9d63c3b4fd63a25464a7b50944aaec7079f
extra : source : ca1b9a2bcc4381795f556fea2fb59066567c30f3
2018-07-31 22:10:07 +09:00
..
README.txt
moz.build
pkixbuild_tests.cpp
pkixcert_extension_tests.cpp
pkixcert_signature_algorithm_tests.cpp
pkixcheck_CheckExtendedKeyUsage_tests.cpp
pkixcheck_CheckIssuer_tests.cpp
pkixcheck_CheckKeyUsage_tests.cpp
pkixcheck_CheckSignatureAlgorithm_tests.cpp
pkixcheck_CheckValidity_tests.cpp
pkixcheck_ParseValidity_tests.cpp
pkixcheck_TLSFeaturesSatisfiedInternal_tests.cpp
pkixder_input_tests.cpp
pkixder_pki_types_tests.cpp
pkixder_universal_types_tests.cpp
pkixgtest.cpp
pkixgtest.h
pkixnames_tests.cpp
pkixocsp_CreateEncodedOCSPRequest_tests.cpp
pkixocsp_VerifyEncodedOCSPResponse.cpp

README.txt

-------------
Running Tests
-------------

Because of the rules below, you can run all the unit tests in this directory,
and only these tests, with:

  mach gtest "pkix*"

You can run just the tests for functions defined in filename pkixfoo.cpp with:

  mach gtest "pkixfoo*"

If you run "mach gtest" then you'll end up running every gtest in Gecko.



------------
Naming Files
------------

Name files containing tests according to one of the following patterns:

  * <filename>_tests.cpp
  * <filename>_<Function>_tests.cpp
  * <filename>_<category>_tests.cpp

  <filename> is the name of the file containing the definitions of the
             function(s) being tested by every test.
  <Function> is the name of the function that is being tested by every
             test.
  <category> describes the group of related functions that are being
             tested by every test.



------------------------------------------------
Always Use a Fixture Class: TEST_F(), not TEST()
------------------------------------------------

Many tests don't technically need a fixture, and so TEST() could technically
be used to define the test. However, when you use TEST_F() instead of TEST(),
the compiler will not allow you to make any typos in the test case name, but
if you use TEST() then the name of the test case is not checked.

See https://code.google.com/p/googletest/wiki/Primer#Test_Fixtures:_Using_the_Same_Data_Configuration_for_Multiple_Te
to learn more about test fixtures.

---------------
Naming Fixtures
---------------

When all tests in a file use the same fixture, use the base name of the file
without the "_tests" suffix as the name of the fixture class; e.g. tests in
"pkixocsp.cpp" should use a fixture "class pkixocsp" by default.

Sometimes tests in a file need separate fixtures. In this case, name the
fixture class according to the pattern <fixture_base>_<fixture_suffix>, where
<fixture_base> is the base name of the file without the "_tests" suffix, and
<fixture_suffix> is a descriptive name for the fixture class, e.g.
"class pkixocsp_DelegatedResponder".