From 0eb95222acbd73713a934f0e1d2b291e858ec471 Mon Sep 17 00:00:00 2001 From: Jason McDonald Date: Mon, 20 Feb 2012 14:45:50 +1000 Subject: testlib: Document a known limitation of QFINDTESTDATA. Change-Id: I72740e394bfe2a95f5b48566b29c9ef9200a8035 Reviewed-by: Rohan McGovern --- src/testlib/qtestcase.cpp | 6 ++++++ 1 file changed, 6 insertions(+) (limited to 'src') diff --git a/src/testlib/qtestcase.cpp b/src/testlib/qtestcase.cpp index 5aac97cfab..ace080ef94 100644 --- a/src/testlib/qtestcase.cpp +++ b/src/testlib/qtestcase.cpp @@ -410,6 +410,12 @@ QT_BEGIN_NAMESPACE point to the working directory from which the compiler is invoked, or only absolute paths to the source files are passed to the compiler. Otherwise, the absolute path of the source directory cannot be determined. + + \bold {Note:} For tests that use the \l QTEST_APPLESS_MAIN() macro to generate a + \c{main()} function, \c{QFINDTESTDATA} will not attempt to find test data + relative to QCoreApplication::applicationDirPath(). In practice, this means that + tests using \c{QTEST_APPLESS_MAIN()} will fail to find their test data + if run from a shadow build tree. */ /*! \macro QTEST_MAIN(TestClass) -- cgit v1.2.3