[bind10-dev] reporting disabled tests?

[JINMEI Tatuya / 神明達哉]

At Mon, 19 Jul 2010 17:38:30 -0500 (CDT),
"Jeremy C. Reed" <jreed at isc.org> wrote:

> > > But I don't see any correlation in the "make check" output itself to 
> > > recognize the specific disabled checks.
> > 
> > What do you mean by that?
> 
> It says 8 tests are disabled. It doesn't show which ones.
> 
> > Again, I'm not sure what you mean...oesn't the above pattern suffice?,
> > i.e.,
> > > "[ RUN      ] CacheTest.disabled
> > > [       OK ] CacheTest.disabled (0 ms)"
> > and so on.
> 
> Sorry. I don't see the "so on" part.

Oh, okay, I was totally confused in my previous reply, sorry about
that.

I can think of several options:

- temporarily enable disabled tests (at run time).  this can be done
  run tests with setting the GTEST_ALSO_RUN_DISABLED_TESTS environment
  variable to non zero, e.g.
  % GTEST_ALSO_RUN_DISABLED_TESTS=1 make check
  The disadvantage of this approach is that the test will stop once it
  encounters failed test cases.
- if it's okay to grep sources we can search for "DISABLED_" in
  *_unittest.cc.
- or we can run each test executable (commonly named "run_unittests")
  with --gtest_list_tests and search for DISABLED_* in its output.

---
JINMEI, Tatuya