As for other Qt projects, it is a good idea to start looking at the pro file:
+= means add module to project when compiling. -= means remove module. |
The qt part is removed for this particular project. I assume that it is since no Qt code is to be tested in this project. It is still possible to compile and test when keeping qt in the project (by commenting out the removal clause on line 7). The same is for the app_bundle tag on line 5.
Google Test is added on the first line, using include statement. Let's have a look at the gtest_dependency.pri file.
The syntax is descibedInitially, there are some checks for whether there is a defined GOOGLETEST_DIR on the computer. If not, the compiler will throw an error message to the build console. If there is such a directory, the test project will be compiled for GTest/GMock.
The test cases are listed in tst_firstgoogletestcase.h as separate functions. The tests are sorted into test cases and test sets, making it possible to have several test sets. This will be useful for me, since I want to sort the test cases in TrafficControl.
The cpp main file initiates the test suite.
In the next blog post, I'll try to import the test cases into the TrafficControl project.
Google Test is added on the first line, using include statement. Let's have a look at the gtest_dependency.pri file.
The syntax is described in the Qt documentation |
The test cases are listed in tst_firstgoogletestcase.h as separate functions. The tests are sorted into test cases and test sets, making it possible to have several test sets. This will be useful for me, since I want to sort the test cases in TrafficControl.
The cpp main file initiates the test suite.
In the next blog post, I'll try to import the test cases into the TrafficControl project.
No comments:
Post a Comment