与谷歌测试纠缠在一起

时间:2014-03-03 06:44:09

标签: android c++ unit-testing android-ndk qt-creator

我无法启动并运行Google测试。我已经阅读了Google提供的steps建议,我还查看了之前的post,并阅读了其他一些examples,但这并不清楚。

为了简单起见,我正在尝试使用Android测试中的建议示例,可以从Android ndk目录中获取 - sample1:

// main.cpp

#include <QtGui/QGuiApplication>
#include "qtquick2applicationviewer.h"
#include "gtest/gtest.h"

int main(int argc, char *argv[])
{
    QGuiApplication app(argc, argv);
    testing::InitGoogleTest(&argc, argv);

    QtQuick2ApplicationViewer viewer;
    viewer.setMainQmlFile(QStringLiteral("qml/factorial/main.qml"));
    viewer.showExpanded();

    return RUN_ALL_TESTS();
}

// sample1_unittest.cpp

#include <limits.h>
#include "sample1.h"
#include "gtest/gtest.h"

// Tests factorial of 0.
TEST(FactorialTest, Zero) {
  EXPECT_EQ(1, Factorial(0));
}

文件sample1.h,sample1.cpp也在项目中,其中包含阶乘函数。 Google测试同样通知了项目文件--factial.pro:

INCLUDEPATH += 
/opt/android-studio/ndk/sources/third_party/googletest/googletest/include

当我按[Build&gt;构建项目“factorial”]它收到以下错误:

main.cpp:8: error: undefined reference to 'testing::InitGoogleTest(int*, char**)'
sample1_unittest.cpp:17: error: undefined reference to 'testing::Test::Test()'

我正在使用Ubuntu,QtCreator,Android和C ++。事实上,我已经花了3天时间嘲笑,但到目前为止并没有太多。因此,我在这里发帖,希望有些大师可能对此提出任何暗示。任何帮助都将受到赞赏。

2 个答案:

答案 0 :(得分:10)

您似乎无法根据自己的描述构建Google Test。您需要将项目编译到库中,然后链接它。如果您安装了CMake,那么您有两个选择:

  • 使用CMake的GUI(它非常直观)生成构建系统文件,然后像往常一样使用它们(例如,如果生成Visual Studio解决方案,请打开.sln文件并建立项目)。
  • 使用命令行执行相同的操作;基本上你只需要创建一个新目录并在其中进行cmake <path-to-google-test>。其余的都一样。

您也可以自己构建库。该发行版包含一个名为fused-src的文件夹,该文件夹应包含至少两个文件:gtest_main.cppgtest-all.cpp。编译这些文件,你就完成了。您需要在此处生成两个库:gtest中的gtest-all.cppgtest_main中的gtest_main.cpp

另一种选择是获得已经构建的库。我从未搜索过它们,但它们可能就在那里。

答案 1 :(得分:5)

尝试这样的事情:

$ g++ -I $GTEST_HOME/include -L $GTEST_HOME/lib -lgtest -lgtest_main -lpthread test.cpp

更多详情:

如果它仍然不起作用,可能会觉得有趣的是考虑使用Makefile:

# A sample Makefile for building Google Test and using it in user
# tests.  Please tweak it to suit your environment and project.  You
# may want to move it to your project's root directory.
#
# SYNOPSIS:
#
#   make [all]  - makes everything.
#   make TARGET - makes the given target.
#   make clean  - removes all files generated by make.

# Please tweak the following variable definitions as needed by your
# project, except GTEST_HEADERS, which you can use in your own targets
# but shouldn't modify.

# Points to the root of Google Test, relative to where this file is.
# Remember to tweak this if you move this file.
GTEST_DIR = ..

# Where to find user code.
USER_DIR = ../samples

# Flags passed to the preprocessor.
# Set Google Test's header directory as a system directory, such that
# the compiler doesn't generate warnings in Google Test headers.
CPPFLAGS += -isystem $(GTEST_DIR)/include

# Flags passed to the C++ compiler.
CXXFLAGS += -g -Wall -Wextra -pthread

# All tests produced by this Makefile.  Remember to add new tests you
# created to the list.
TESTS = sample1_unittest

# All Google Test headers.  Usually you shouldn't change this
# definition.
GTEST_HEADERS = $(GTEST_DIR)/include/gtest/*.h \
                $(GTEST_DIR)/include/gtest/internal/*.h

# House-keeping build targets.

all : $(TESTS)

clean :
    rm -f $(TESTS) gtest.a gtest_main.a *.o

# Builds gtest.a and gtest_main.a.

# Usually you shouldn't tweak such internal variables, indicated by a
# trailing _.
GTEST_SRCS_ = $(GTEST_DIR)/src/*.cc $(GTEST_DIR)/src/*.h $(GTEST_HEADERS)

# For simplicity and to avoid depending on Google Test's
# implementation details, the dependencies specified below are
# conservative and not optimized.  This is fine as Google Test
# compiles fast and for ordinary users its source rarely changes.
gtest-all.o : $(GTEST_SRCS_)
    $(CXX) $(CPPFLAGS) -I$(GTEST_DIR) $(CXXFLAGS) -c \
            $(GTEST_DIR)/src/gtest-all.cc

gtest_main.o : $(GTEST_SRCS_)
    $(CXX) $(CPPFLAGS) -I$(GTEST_DIR) $(CXXFLAGS) -c \
            $(GTEST_DIR)/src/gtest_main.cc

gtest.a : gtest-all.o
    $(AR) $(ARFLAGS) $@ $^

gtest_main.a : gtest-all.o gtest_main.o
    $(AR) $(ARFLAGS) $@ $^

# Builds a sample test.  A test should link with either gtest.a or
# gtest_main.a, depending on whether it defines its own main()
# function.

sample1.o : $(USER_DIR)/sample1.cc $(USER_DIR)/sample1.h $(GTEST_HEADERS)
    $(CXX) $(CPPFLAGS) $(CXXFLAGS) -c $(USER_DIR)/sample1.cc

sample1_unittest.o : $(USER_DIR)/sample1_unittest.cc \
                     $(USER_DIR)/sample1.h $(GTEST_HEADERS)
    $(CXX) $(CPPFLAGS) $(CXXFLAGS) -c $(USER_DIR)/sample1_unittest.cc

sample1_unittest : sample1.o sample1_unittest.o gtest_main.a
    $(CXX) $(CPPFLAGS) $(CXXFLAGS) -lpthread $^ -o $@

如果你必须使用Makefile来使gtest工作,你可能需要为你的情况调整给定的template,因为你打算构建它以用于Android。