1. 30 Jul, 2018 1 commit
  2. 27 Jul, 2018 2 commits
  3. 25 Jul, 2018 2 commits
  4. 21 Jul, 2018 3 commits
  5. 20 Jul, 2018 1 commit
    • Gennadiy Civil's avatar
      · a02af2f6
      Gennadiy Civil authored
      code merge
      a02af2f6
  6. 18 Jul, 2018 2 commits
    • Gennadiy Civil's avatar
      · d41bfd73
      Gennadiy Civil authored
      Fix link
      d41bfd73
    • Gennadiy Civil's avatar
      · 7e73a7ae
      Gennadiy Civil authored
      Formatting and a link
      7e73a7ae
  7. 17 Jul, 2018 1 commit
  8. 16 Jul, 2018 1 commit
  9. 12 Jul, 2018 1 commit
  10. 11 Jul, 2018 2 commits
    • Gennadiy Civil's avatar
      · 36066cfe
      Gennadiy Civil authored
      more formatting [skip ci]
      36066cfe
    • Gennadiy Civil's avatar
      · 74cccf49
      Gennadiy Civil authored
      formatting, [ci skip]
      74cccf49
  11. 10 Jul, 2018 4 commits
    • Gennadiy Civil's avatar
      Fix heading · 4f919428
      Gennadiy Civil authored
      [skip ci] 
      4f919428
    • Gennadiy Civil's avatar
      Docs sync · 50daf299
      Gennadiy Civil authored
      [ci skip]
      50daf299
    • Derek Mauro's avatar
      Pass the --no_stacktrace_support argument to the CMake tests · d772e203
      Derek Mauro authored
      This does the same thing to the CMake tests that is done to the
      Bazel tests, and now makes the CMake tests pass.
      d772e203
    • Derek Mauro's avatar
      Adds stacktrace support from Abseil to Google Test · 4c417877
      Derek Mauro authored
      This change adds the ability to generate stacktraces in Google Test on
      both failures of assertions/expectations and on crashes. The
      stacktrace support is conditionally available only when using Abseil
      with Google Test.
      
      To use this support, run the test under Bazel with a command like this:
      
      bazel test --define absl=1 --test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1 //path/to/your:test
      
      The "--define absl=1" part enables stacktraces on assertion/expectation
      failures.
      
      The "--test_env=GTEST_INSTALL_FAILURE_SIGNAL_HANDLER=1" part enables
      the signal handler that logs a stacktrace in the event of a crash
      (this also requires the "--define absl=1" part). This is not the
      default since it may interfere with existing tests.
      4c417877
  12. 29 Jun, 2018 1 commit
  13. 14 Jun, 2018 1 commit
    • Rohan Joyce's avatar
      Eliminate GTEST_TEST_FILTER_ENV_VAR_. · 0563b52d
      Rohan Joyce authored
      GTEST_TEST_FILTER_ENV_VAR_ was used to specify an environment variable to obtain
      the default test filter from. By default it was unset which broke
      "--test_filter" for bazel. This CL eliminates GTEST_TEST_FILTER_ENV_VAR_ and
      explicitly obtains the default test filter from the environment variable
      TESTBRIDGE_TEST_ONLY if it exists.
      0563b52d
  14. 13 Jun, 2018 2 commits
  15. 12 Jun, 2018 1 commit
    • Takuto Ikuta's avatar
      Reduce the number of strcmp calling while initialization · f4d0631a
      Takuto Ikuta authored
      When we do parallel test execution with a process for a test,
      initialization of gtest become performance bottleneck when the test
      binary contains many testcases.
      
      Especially, some parameterlized test in chromium browser affected by
      largely when address sanitizer is enabled.
      Address sanitizer does not allow using optimized strcmp function and
      test addition in parameterized test require lookup of test case using
      strcmp.
      
      This patch reduces the number of strcmp, it is called when registering
      parameterized test. Using reverse iterator improves the time to find
      registered tests in such case.
      
      Some tests for chromium browser using address sanitizer finished 2x
      faster with this patch.
      f4d0631a
  16. 11 Jun, 2018 7 commits
  17. 07 Jun, 2018 1 commit
  18. 04 Jun, 2018 1 commit
  19. 31 May, 2018 2 commits
  20. 23 May, 2018 1 commit
  21. 21 May, 2018 2 commits
  22. 11 May, 2018 1 commit