testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
/****************************************************************************
|
|
|
|
**
|
2016-01-15 12:36:27 +00:00
|
|
|
** Copyright (C) 2016 The Qt Company Ltd.
|
|
|
|
** Contact: https://www.qt.io/licensing/
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
**
|
|
|
|
** This file is part of the test suite of the Qt Toolkit.
|
|
|
|
**
|
2016-01-15 12:36:27 +00:00
|
|
|
** $QT_BEGIN_LICENSE:GPL-EXCEPT$
|
2012-09-19 12:28:29 +00:00
|
|
|
** Commercial License Usage
|
|
|
|
** Licensees holding valid commercial Qt licenses may use this file in
|
|
|
|
** accordance with the commercial license agreement provided with the
|
|
|
|
** Software or, alternatively, in accordance with the terms contained in
|
2015-01-28 08:44:43 +00:00
|
|
|
** a written agreement between you and The Qt Company. For licensing terms
|
2016-01-15 12:36:27 +00:00
|
|
|
** and conditions see https://www.qt.io/terms-conditions. For further
|
|
|
|
** information use the contact form at https://www.qt.io/contact-us.
|
2012-09-19 12:28:29 +00:00
|
|
|
**
|
2016-01-15 12:36:27 +00:00
|
|
|
** GNU General Public License Usage
|
|
|
|
** Alternatively, this file may be used under the terms of the GNU
|
|
|
|
** General Public License version 3 as published by the Free Software
|
|
|
|
** Foundation with exceptions as appearing in the file LICENSE.GPL3-EXCEPT
|
|
|
|
** included in the packaging of this file. Please review the following
|
|
|
|
** information to ensure the GNU General Public License requirements will
|
|
|
|
** be met: https://www.gnu.org/licenses/gpl-3.0.html.
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
**
|
|
|
|
** $QT_END_LICENSE$
|
|
|
|
**
|
|
|
|
****************************************************************************/
|
|
|
|
|
|
|
|
|
2012-01-10 00:28:42 +00:00
|
|
|
#include <QtCore/QCoreApplication>
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
#include <QtTest/QtTest>
|
|
|
|
|
|
|
|
#define TESTFILE "testfile"
|
|
|
|
|
|
|
|
class FindTestData: public QObject
|
|
|
|
{
|
|
|
|
Q_OBJECT
|
|
|
|
private slots:
|
|
|
|
void initTestCase();
|
|
|
|
void cleanupTestCase();
|
|
|
|
|
|
|
|
void paths();
|
|
|
|
|
|
|
|
private:
|
|
|
|
bool touch(QString const&);
|
|
|
|
};
|
|
|
|
|
|
|
|
void FindTestData::initTestCase()
|
|
|
|
{
|
|
|
|
// verify that our qt.conf is working as expected.
|
|
|
|
QString app_path = QCoreApplication::applicationDirPath();
|
2012-01-11 05:40:24 +00:00
|
|
|
QString install_path = app_path
|
|
|
|
#ifdef Q_OS_MAC
|
|
|
|
+ "/Contents"
|
|
|
|
#endif
|
|
|
|
+ "/tests";
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
QVERIFY(QDir("/").mkpath(install_path));
|
|
|
|
QVERIFY(QDir("/").mkpath(install_path + "/findtestdata"));
|
|
|
|
QCOMPARE(QLibraryInfo::location(QLibraryInfo::TestsPath), install_path);
|
|
|
|
|
|
|
|
// make fake source and build directories
|
|
|
|
QVERIFY(QDir("/").mkpath(app_path + "/fakesrc"));
|
|
|
|
QVERIFY(QDir("/").mkpath(app_path + "/fakebuild"));
|
|
|
|
}
|
|
|
|
|
|
|
|
void FindTestData::cleanupTestCase()
|
|
|
|
{
|
|
|
|
QString app_path = QCoreApplication::applicationDirPath();
|
|
|
|
QFile(app_path + "/tests/findtestdata/" TESTFILE).remove();
|
|
|
|
QFile(app_path + "/tests/" TESTFILE).remove();
|
|
|
|
QFile(app_path + "/fakesrc/" TESTFILE).remove();
|
|
|
|
QDir("/").rmpath(app_path + "/tests/findtestdata");
|
|
|
|
QDir("/").rmpath(app_path + "/fakesrc");
|
|
|
|
QDir("/").rmpath(app_path + "/fakebuild");
|
|
|
|
}
|
|
|
|
|
|
|
|
// Create an empty file at the specified path (or return false)
|
|
|
|
bool FindTestData::touch(QString const& path)
|
|
|
|
{
|
|
|
|
QFile file(path);
|
|
|
|
if (!file.open(QIODevice::WriteOnly)) {
|
|
|
|
qWarning("Failed to create %s: %s", qPrintable(path), qPrintable(file.errorString()));
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
void FindTestData::paths()
|
|
|
|
{
|
|
|
|
// There are three possible locations for the testdata.
|
|
|
|
// In this test, we will put the testdata at all three locations,
|
|
|
|
// then remove it from one location at a time and verify that
|
|
|
|
// QFINDTESTDATA correctly falls back each time.
|
|
|
|
|
|
|
|
// 1. relative to test binary.
|
|
|
|
QString app_path = QCoreApplication::applicationDirPath();
|
|
|
|
QString testfile_path1 = app_path + "/" TESTFILE;
|
|
|
|
QVERIFY(touch(testfile_path1));
|
|
|
|
|
|
|
|
// 2. at the test install path (faked via qt.conf)
|
2012-01-11 05:40:24 +00:00
|
|
|
QString testfile_path2 = app_path
|
|
|
|
#ifdef Q_OS_MAC
|
|
|
|
+ "/Contents"
|
|
|
|
#endif
|
|
|
|
+ "/tests/findtestdata/" TESTFILE;
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
QVERIFY(touch(testfile_path2));
|
|
|
|
|
|
|
|
// 3. at the source path (which we will fake later on)
|
|
|
|
QString testfile_path3 = app_path + "/fakesrc/" TESTFILE;
|
|
|
|
QVERIFY(touch(testfile_path3));
|
|
|
|
|
|
|
|
// OK, all testdata created. Verify that they are found in correct priority order.
|
|
|
|
|
|
|
|
QCOMPARE(QFINDTESTDATA(TESTFILE), testfile_path1);
|
|
|
|
QVERIFY(QFile(testfile_path1).remove());
|
|
|
|
|
|
|
|
QCOMPARE(QFINDTESTDATA(TESTFILE), testfile_path2);
|
|
|
|
QVERIFY(QFile(testfile_path2).remove());
|
|
|
|
|
|
|
|
// We cannot reasonably redefine __FILE__, so we call the underlying function instead.
|
|
|
|
// __FILE__ may be absolute or relative path; test both.
|
|
|
|
|
|
|
|
// absolute:
|
2012-02-01 02:03:59 +00:00
|
|
|
#if defined(Q_OS_WIN)
|
|
|
|
QCOMPARE(QTest::qFindTestData(TESTFILE, qPrintable(app_path + "/fakesrc/fakefile.cpp"), __LINE__).toLower(), testfile_path3.toLower());
|
|
|
|
#else
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
QCOMPARE(QTest::qFindTestData(TESTFILE, qPrintable(app_path + "/fakesrc/fakefile.cpp"), __LINE__), testfile_path3);
|
2012-02-01 02:03:59 +00:00
|
|
|
#endif
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
// relative: (pretend that we were compiled within fakebuild directory, pointing at files in ../fakesrc)
|
2012-02-01 02:03:59 +00:00
|
|
|
#if defined(Q_OS_WIN)
|
|
|
|
QCOMPARE(QTest::qFindTestData(TESTFILE, "../fakesrc/fakefile.cpp", __LINE__, qPrintable(app_path + "/fakebuild")).toLower(), testfile_path3.toLower());
|
|
|
|
#else
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
QCOMPARE(QTest::qFindTestData(TESTFILE, "../fakesrc/fakefile.cpp", __LINE__, qPrintable(app_path + "/fakebuild")), testfile_path3);
|
2012-02-01 02:03:59 +00:00
|
|
|
#endif
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
QVERIFY(QFile(testfile_path3).remove());
|
|
|
|
|
2018-06-18 13:14:19 +00:00
|
|
|
#if !defined(Q_OS_WIN)
|
|
|
|
struct ChdirOnReturn
|
|
|
|
{
|
|
|
|
~ChdirOnReturn() { QDir::setCurrent(dir); }
|
|
|
|
QString dir;
|
|
|
|
};
|
|
|
|
|
|
|
|
// When cross-compiling from Windows to a *nix system the __FILE__ path's canonical path is an
|
|
|
|
// empty string, which, when used as a prefix, would cause QFINDTESTDATA to look for files in
|
|
|
|
// root ('/') when trying to look for files relative to the test source.
|
|
|
|
QString usrPath = app_path + "/temp/usr/";
|
|
|
|
QVERIFY(QDir().mkpath(usrPath));
|
|
|
|
{
|
|
|
|
ChdirOnReturn chdirObject{QDir::currentPath()};
|
|
|
|
QDir::setCurrent(app_path + "/temp");
|
|
|
|
QCOMPARE(QTest::qFindTestData("usr/",
|
|
|
|
"C:\\path\\to\\source\\source.cpp",
|
|
|
|
__LINE__,
|
|
|
|
"C:\\path\\to\\build\\").toLower(),
|
|
|
|
usrPath.toLower());
|
|
|
|
}
|
|
|
|
QVERIFY(QDir().rmpath(usrPath));
|
|
|
|
#endif
|
|
|
|
|
testlib: add QFINDTESTDATA macro for finding testdata files
Automated tests often need to load some data from external files.
Currently, a wide variety of approaches for this have been used in Qt
autotests, including:
- embed the source directory into the test binary at compile time, and
find the testdata relative to that; this fails when the source tree
is no longer available (e.g. when the tests are deployed to a device).
- use a path relative to the current working directory, and trust that
the caller always sets the current working directory such that the
testdata can be found; this fails when the caller uses a different
working directory than expected.
- use a path relative to QCoreApplication::applicationDirPath();
this fails when source tree != build tree (since testdata is not
automatically copied into the build tree).
- compile the files into the binary using the Qt resource system; this
should work, but does not allow for testing of code which genuinely
needs external files.
It seems that there is not a simple method for determining the testdata
path which can be reliably used in all circumstances, so various tests
have reinvented the testdata location method in different ways.
Therefore, this is a good candidate for an addition to the testlib API.
The current implementation of QFINDTESTDATA is able to find testdata
in all three of (build tree, install tree, source tree), in that order.
Change-Id: Ib2fed860723ccf437240da3b00db22dfe1a6b56c
Reviewed-by: Jason McDonald <jason.mcdonald@nokia.com>
2011-11-29 06:45:52 +00:00
|
|
|
// Note, this is expected to generate a warning.
|
|
|
|
// We can't use ignoreMessage, because the warning comes from testlib,
|
|
|
|
// not via a "normal" qWarning. But it's OK, our caller (tst_selftests)
|
|
|
|
// will verify that the warning is printed.
|
|
|
|
QCOMPARE(QFINDTESTDATA(TESTFILE), QString());
|
|
|
|
}
|
|
|
|
|
|
|
|
QTEST_MAIN(FindTestData)
|
|
|
|
#include "findtestdata.moc"
|