gtest如何执行部分测试用例

开发时候,先写测试是个好习惯,就算不是正式意义上的测试驱动开发,也对开发质量有明显提升。C++开发写测试代码,几种工具里面,我最喜欢gTest.   初上手时,以为它不能选择部分用例单独执行,其实它是提供了这功能的,可以先简单的做到。


假定写了下面这样若干测试用例。

------------------------------------------------------

TEST(case1, functionA_test) {

....

}

TEST(case1, functionB_test) {

....

}


TEST(case2,  functionA_test) {

.....

}

TEST(case2, functionB_test){

....

}


TEST(case3, functionA_test) {

....

}

-------------------------------------------------

再假定编译出来的程序名test.exe, 


比如我们现在想要只跑case2这几个测试,那么一个命令行参数就可以搞定:

--gtest_filter=case2.*


如果想在VS集成环境运行,那么就把这一串加进命令参数:

配置属性=〉调试=〉命令参数 设置


---------------------------------

其实在命令行带/?参数执行编译好的测试程序,就知道gTest这些开关:

附在下面

----------------------------------


This program contains tests written using Google Test. You can use the
following command line flags to control its behavior:


Test Selection:
  --gtest_list_tests
      List the names of all tests instead of running them. The name of
      TEST(Foo, Bar) is "Foo.Bar".
  --gtest_filter=POSTIVE_PATTERNS[-NEGATIVE_PATTERNS]
      Run only the tests whose name matches one of the positive patterns but
      none of the negative patterns. '?' matches any single character; '*'
      matches any substring; ':' separates two patterns.
  --gtest_also_run_disabled_tests
      Run all disabled tests too.


Test Execution:
  --gtest_repeat=[COUNT]
      Run the tests repeatedly; use a negative count to repeat forever.
  --gtest_shuffle
      Randomize tests' orders on every iteration.
  --gtest_random_seed=[NUMBER]
      Random number seed to use for shuffling test orders (between 1 and
      99999, or 0 to use a seed based on the current time).


Test Output:
  --gtest_color=(yes|no|auto)
      Enable/disable colored output. The default is auto.
  --gtest_print_time=0
      Don't print the elapsed time of each test.
  --gtest_output=xml[:DIRECTORY_PATH\|:FILE_PATH]
      Generate an XML report in the given directory or with the given file
      name. FILE_PATH defaults to test_details.xml.


Assertion Behavior:
  --gtest_break_on_failure
      Turn assertion failures into debugger break-points.
  --gtest_throw_on_failure
      Turn assertion failures into C++ exceptions.
  --gtest_catch_exceptions=0
      Do not report exceptions as test failures. Instead, allow them
      to crash the program or throw a pop-up (on Windows).


Except for --gtest_list_tests, you can alternatively set the corresponding
environment variable of a flag (all letters in upper-case). For example, to
disable colored text output, you can either specify --gtest_color=no or set
the GTEST_COLOR environment variable to no.


For more information, please read the Google Test documentation at
http://code.google.com/p/googletest/. If you find a bug in Google Test
(not one in your own code or tests), please report it to
<[email protected]>.



猜你喜欢

转载自blog.csdn.net/halfdream/article/details/30490721