2022-05-13 13:12:05 +00:00
|
|
|
// Copyright (C) 2016 The Qt Company Ltd.
|
|
|
|
// SPDX-License-Identifier: LicenseRef-Qt-Commercial OR LGPL-3.0-only OR GPL-2.0-only OR GPL-3.0-only
|
2011-05-20 01:57:29 +00:00
|
|
|
|
2020-04-03 12:35:11 +00:00
|
|
|
#include "quicktest_p.h"
|
2011-05-20 01:57:29 +00:00
|
|
|
#include "quicktestresult_p.h"
|
|
|
|
#include <QtTest/qtestsystem.h>
|
|
|
|
#include "qtestoptions_p.h"
|
2012-02-16 04:43:03 +00:00
|
|
|
#include <QtQml/qqml.h>
|
|
|
|
#include <QtQml/qqmlengine.h>
|
|
|
|
#include <QtQml/qqmlcontext.h>
|
2018-10-19 12:27:53 +00:00
|
|
|
#include <QtQuick/private/qquickitem_p.h>
|
2021-06-19 09:30:54 +00:00
|
|
|
#include <QtQuick/private/qquickwindow_p.h>
|
2018-10-19 12:27:53 +00:00
|
|
|
#include <QtQuick/qquickitem.h>
|
Say hello to QtQuick module
This change moves the QtQuick 2 types and C++ API (including
SceneGraph) to a new module (AKA library), QtQuick.
99% of this change is moving files from src/declarative to
src/quick, and from tests/auto/declarative to
tests/auto/qtquick2.
The loading of QtQuick 2 ("import QtQuick 2.0") is now delegated to
a plugin, src/imports/qtquick2, just like it's done for QtQuick 1.
All tools, examples, and tests that use QtQuick C++ API have gotten
"QT += quick" or "QT += quick-private" added to their .pro file.
A few additional internal QtDeclarative classes had to be exported
(via Q_DECLARATIVE_PRIVATE_EXPORT) since they're needed by the
QtQuick 2 implementation.
The old header locations (e.g. QtDeclarative/qquickitem.h) will
still be supported for some time, but will produce compile-time
warnings. (To avoid the QtQuick implementation using the
compatibility headers (since QtDeclarative's includepath comes
first), a few include statements were modified, e.g. from
"#include <qsgnode.h>" to "#include <QtQuick/qsgnode.h>".)
There's a change in qtbase that automatically adds QtQuick to the
module list if QtDeclarative is used. Together with the compatibility
headers, this should help reduce the migration pain for existing
projects.
In theory, simply getting an existing QtDeclarative-based project
to compile and link shouldn't require any changes for now -- but
porting to the new scheme is of course recommended, and will
eventually become mandatory.
Task-number: QTBUG-22889
Reviewed-by: Lars Knoll <lars.knoll@nokia.com>
Change-Id: Ia52be9373172ba2f37e7623231ecb060316c96a7
Reviewed-by: Kent Hansen <kent.hansen@nokia.com>
Reviewed-by: Sergio Ahumada <sergio.ahumada@nokia.com>
2011-11-23 14:14:07 +00:00
|
|
|
#include <QtQuick/qquickview.h>
|
2021-06-19 09:30:54 +00:00
|
|
|
#include <QtQuick/qquickwindow.h>
|
2012-02-16 04:43:03 +00:00
|
|
|
#include <QtQml/qjsvalue.h>
|
|
|
|
#include <QtQml/qjsengine.h>
|
2013-08-23 10:57:03 +00:00
|
|
|
#include <QtQml/qqmlpropertymap.h>
|
2018-10-19 13:24:58 +00:00
|
|
|
#include <QtQuick/private/qquickitem_p.h>
|
|
|
|
#include <QtQuick/qquickitem.h>
|
2020-02-03 14:02:31 +00:00
|
|
|
#include <qopengl.h>
|
2011-05-20 01:57:29 +00:00
|
|
|
#include <QtCore/qurl.h>
|
|
|
|
#include <QtCore/qfileinfo.h>
|
|
|
|
#include <QtCore/qdir.h>
|
|
|
|
#include <QtCore/qdiriterator.h>
|
|
|
|
#include <QtCore/qfile.h>
|
|
|
|
#include <QtCore/qdebug.h>
|
|
|
|
#include <QtCore/qeventloop.h>
|
2012-01-06 12:25:51 +00:00
|
|
|
#include <QtCore/qtextstream.h>
|
2019-02-12 13:19:19 +00:00
|
|
|
#include <QtCore/qtimer.h>
|
2011-05-20 01:57:29 +00:00
|
|
|
#include <QtGui/qtextdocument.h>
|
|
|
|
#include <stdio.h>
|
2011-09-09 12:43:33 +00:00
|
|
|
#include <QtGui/QGuiApplication>
|
2011-10-27 06:55:43 +00:00
|
|
|
#include <QtCore/QTranslator>
|
2012-06-12 04:46:12 +00:00
|
|
|
#include <QtTest/QSignalSpy>
|
2017-11-24 15:50:03 +00:00
|
|
|
#include <QtQml/QQmlFileSelector>
|
2012-06-12 04:46:12 +00:00
|
|
|
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
#include <private/qqmlcomponent_p.h>
|
2020-03-24 17:21:15 +00:00
|
|
|
#include <private/qv4resolvedtypereference_p.h>
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
|
2011-05-20 01:57:29 +00:00
|
|
|
QT_BEGIN_NAMESPACE
|
|
|
|
|
2018-10-19 13:24:58 +00:00
|
|
|
/*!
|
|
|
|
\since 5.13
|
|
|
|
|
|
|
|
Returns \c true if \l {QQuickItem::}{updatePolish()} has not been called
|
|
|
|
on \a item since the last call to \l {QQuickItem::}{polish()},
|
|
|
|
otherwise returns \c false.
|
|
|
|
|
2018-10-24 08:17:11 +00:00
|
|
|
When assigning values to properties in QML, any layouting the item
|
|
|
|
must do as a result of the assignment might not take effect immediately,
|
|
|
|
but can instead be postponed until the item is polished. For these cases,
|
|
|
|
you can use this function to ensure that the item has been polished
|
|
|
|
before the execution of the test continues. For example:
|
|
|
|
|
|
|
|
\code
|
|
|
|
QVERIFY(QQuickTest::qIsPolishScheduled(item));
|
|
|
|
QVERIFY(QQuickTest::qWaitForItemPolished(item));
|
|
|
|
\endcode
|
|
|
|
|
|
|
|
Without the call to \c qIsPolishScheduled() above, the
|
|
|
|
call to \c qWaitForItemPolished() might see that no polish
|
|
|
|
was scheduled and therefore pass instantly, assuming that
|
|
|
|
the item had already been polished. This function
|
|
|
|
makes it obvious why an item wasn't polished and allows tests to
|
|
|
|
fail early under such circumstances.
|
|
|
|
|
2018-12-07 15:04:53 +00:00
|
|
|
The QML equivalent of this function is
|
|
|
|
\l {TestCase::}{isPolishScheduled()}.
|
|
|
|
|
2018-10-19 13:24:58 +00:00
|
|
|
\sa QQuickItem::polish(), QQuickItem::updatePolish()
|
|
|
|
*/
|
|
|
|
bool QQuickTest::qIsPolishScheduled(const QQuickItem *item)
|
|
|
|
{
|
|
|
|
return QQuickItemPrivate::get(item)->polishScheduled;
|
|
|
|
}
|
|
|
|
|
2021-06-19 09:30:54 +00:00
|
|
|
/*!
|
|
|
|
\since 6.4
|
|
|
|
\overload qIsPolishScheduled()
|
|
|
|
|
|
|
|
Returns \c true if there are any items managed by this window for
|
|
|
|
which \c qIsPolishScheduled(item) returns \c true, otherwise
|
|
|
|
returns \c false.
|
|
|
|
|
|
|
|
For example, if an item somewhere within the scene may or may not
|
|
|
|
be polished, but you need to wait for it if it is, you can use
|
|
|
|
the following code:
|
|
|
|
|
|
|
|
\code
|
|
|
|
if (QQuickTest::qIsPolishScheduled(window))
|
|
|
|
QVERIFY(QQuickTest::qWaitForPolish(window));
|
|
|
|
\endcode
|
|
|
|
|
2022-05-27 06:57:53 +00:00
|
|
|
The QML equivalent of this function is
|
|
|
|
\l [QML]{TestCase::}{isPolishScheduled()}.
|
|
|
|
|
2021-06-19 09:30:54 +00:00
|
|
|
\sa QQuickItem::polish(), QQuickItem::updatePolish(),
|
|
|
|
QQuickTest::qWaitForPolish()
|
|
|
|
*/
|
|
|
|
bool QQuickTest::qIsPolishScheduled(const QQuickWindow *window)
|
|
|
|
{
|
|
|
|
return !QQuickWindowPrivate::get(window)->itemsToPolish.isEmpty();
|
|
|
|
}
|
|
|
|
|
|
|
|
#if QT_VERSION < QT_VERSION_CHECK(7, 0, 0)
|
|
|
|
#if QT_DEPRECATED_SINCE(6, 4)
|
2018-10-19 12:27:53 +00:00
|
|
|
/*!
|
|
|
|
\since 5.13
|
2021-06-19 09:30:54 +00:00
|
|
|
\deprecated [6.4] Use \l qWaitForPolish() instead.
|
2018-10-19 12:27:53 +00:00
|
|
|
|
|
|
|
Waits for \a timeout milliseconds or until
|
|
|
|
\l {QQuickItem::}{updatePolish()} has been called on \a item.
|
|
|
|
|
|
|
|
Returns \c true if \c updatePolish() was called on \a item within
|
|
|
|
\a timeout milliseconds, otherwise returns \c false.
|
|
|
|
|
2018-12-07 15:04:53 +00:00
|
|
|
The QML equivalent of this function is
|
|
|
|
\l {TestCase::}{waitForItemPolished()}.
|
2018-10-19 12:27:53 +00:00
|
|
|
|
|
|
|
\sa QQuickItem::polish(), QQuickItem::updatePolish(),
|
|
|
|
QQuickTest::qIsPolishScheduled()
|
|
|
|
*/
|
|
|
|
bool QQuickTest::qWaitForItemPolished(const QQuickItem *item, int timeout)
|
2021-06-19 09:30:54 +00:00
|
|
|
{
|
|
|
|
return qWaitForPolish(item, timeout);
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*!
|
|
|
|
\since 6.4
|
|
|
|
|
|
|
|
Waits for \a timeout milliseconds or until
|
|
|
|
\l {QQuickItem::}{updatePolish()} has been called on \a item.
|
|
|
|
|
|
|
|
Returns \c true if \c updatePolish() was called on \a item within
|
|
|
|
\a timeout milliseconds, otherwise returns \c false.
|
|
|
|
|
|
|
|
\sa QQuickItem::polish(), QQuickItem::updatePolish(),
|
|
|
|
QQuickTest::qIsPolishScheduled()
|
|
|
|
*/
|
|
|
|
bool QQuickTest::qWaitForPolish(const QQuickItem *item, int timeout)
|
2018-10-19 12:27:53 +00:00
|
|
|
{
|
|
|
|
return QTest::qWaitFor([&]() { return !QQuickItemPrivate::get(item)->polishScheduled; }, timeout);
|
|
|
|
}
|
|
|
|
|
2021-06-19 09:30:54 +00:00
|
|
|
/*!
|
|
|
|
\since 6.4
|
|
|
|
|
|
|
|
Waits for \a timeout milliseconds or until \c qIsPolishScheduled(item)
|
|
|
|
returns \c false for all items managed by \a window.
|
|
|
|
|
|
|
|
Returns \c true if \c qIsPolishScheduled(item) returns false for all items
|
|
|
|
within \a timeout milliseconds, otherwise returns \c false.
|
|
|
|
|
2022-05-27 06:57:53 +00:00
|
|
|
The QML equivalent of this function is
|
|
|
|
\l [QML]{TestCase::}{waitForPolish()}.
|
|
|
|
|
2021-06-19 09:30:54 +00:00
|
|
|
\sa QQuickItem::polish(), QQuickItem::updatePolish(),
|
|
|
|
QQuickTest::qIsPolishScheduled()
|
|
|
|
*/
|
|
|
|
bool QQuickTest::qWaitForPolish(const QQuickWindow *window, int timeout)
|
|
|
|
{
|
|
|
|
return QTest::qWaitFor([&]() { return QQuickWindowPrivate::get(window)->itemsToPolish.isEmpty(); }, timeout);
|
|
|
|
}
|
|
|
|
|
2011-05-20 01:57:29 +00:00
|
|
|
static inline QString stripQuotes(const QString &s)
|
|
|
|
{
|
2022-10-05 05:29:16 +00:00
|
|
|
if (s.size() >= 2 && s.startsWith(QLatin1Char('"')) && s.endsWith(QLatin1Char('"')))
|
|
|
|
return s.mid(1, s.size() - 2);
|
2011-05-20 01:57:29 +00:00
|
|
|
else
|
|
|
|
return s;
|
|
|
|
}
|
|
|
|
|
2021-11-08 12:53:11 +00:00
|
|
|
static void handleCompileErrors(
|
|
|
|
const QFileInfo &fi, const QList<QQmlError> &errors, QQmlEngine *engine,
|
|
|
|
QQuickView *view = nullptr)
|
2012-01-06 12:25:51 +00:00
|
|
|
{
|
|
|
|
// Error compiling the test - flag failure in the log and continue.
|
|
|
|
QuickTestResult results;
|
|
|
|
results.setTestCaseName(fi.baseName());
|
|
|
|
results.startLogging();
|
|
|
|
results.setFunctionName(QLatin1String("compile"));
|
|
|
|
// Verbose warning output of all messages and relevant parameters
|
|
|
|
QString message;
|
|
|
|
QTextStream str(&message);
|
|
|
|
str << "\n " << QDir::toNativeSeparators(fi.absoluteFilePath()) << " produced "
|
|
|
|
<< errors.size() << " error(s):\n";
|
2016-08-11 14:28:55 +00:00
|
|
|
for (const QQmlError &e : errors) {
|
2012-01-06 12:25:51 +00:00
|
|
|
str << " ";
|
|
|
|
if (e.url().isLocalFile()) {
|
2012-10-18 13:02:36 +00:00
|
|
|
str << QDir::toNativeSeparators(e.url().toLocalFile());
|
2012-01-06 12:25:51 +00:00
|
|
|
} else {
|
|
|
|
str << e.url().toString();
|
|
|
|
}
|
|
|
|
if (e.line() > 0)
|
|
|
|
str << ':' << e.line() << ',' << e.column();
|
|
|
|
str << ": " << e.description() << '\n';
|
|
|
|
}
|
|
|
|
str << " Working directory: " << QDir::toNativeSeparators(QDir::current().absolutePath()) << '\n';
|
2021-11-08 12:53:11 +00:00
|
|
|
if (engine) {
|
|
|
|
str << " ";
|
|
|
|
if (view)
|
|
|
|
str << "View: " << view->metaObject()->className() << ", ";
|
|
|
|
str << "Import paths:\n";
|
2016-08-11 14:28:55 +00:00
|
|
|
const auto importPaths = engine->importPathList();
|
|
|
|
for (const QString &i : importPaths)
|
2012-01-06 12:25:51 +00:00
|
|
|
str << " '" << QDir::toNativeSeparators(i) << "'\n";
|
|
|
|
const QStringList pluginPaths = engine->pluginPathList();
|
|
|
|
str << " Plugin paths:\n";
|
2016-08-11 14:28:55 +00:00
|
|
|
for (const QString &p : pluginPaths)
|
2012-01-06 12:25:51 +00:00
|
|
|
str << " '" << QDir::toNativeSeparators(p) << "'\n";
|
|
|
|
}
|
|
|
|
qWarning("%s", qPrintable(message));
|
|
|
|
// Fail with error 0.
|
|
|
|
results.fail(errors.at(0).description(),
|
|
|
|
errors.at(0).url(), errors.at(0).line());
|
2012-02-07 05:09:44 +00:00
|
|
|
results.finishTestData();
|
2012-02-09 06:17:32 +00:00
|
|
|
results.finishTestDataCleanup();
|
2012-01-06 12:25:51 +00:00
|
|
|
results.finishTestFunction();
|
|
|
|
results.setFunctionName(QString());
|
|
|
|
results.stopLogging();
|
|
|
|
}
|
|
|
|
|
2023-02-09 14:29:58 +00:00
|
|
|
bool qWaitForSignal(QObject *obj, const char* signal, int timeout)
|
2012-06-12 04:46:12 +00:00
|
|
|
{
|
|
|
|
QSignalSpy spy(obj, signal);
|
|
|
|
QElapsedTimer timer;
|
|
|
|
timer.start();
|
|
|
|
|
|
|
|
while (!spy.size()) {
|
|
|
|
int remaining = timeout - int(timer.elapsed());
|
|
|
|
if (remaining <= 0)
|
|
|
|
break;
|
|
|
|
QCoreApplication::processEvents(QEventLoop::AllEvents, remaining);
|
2018-02-21 09:41:54 +00:00
|
|
|
QCoreApplication::sendPostedEvents(nullptr, QEvent::DeferredDelete);
|
2012-06-12 04:46:12 +00:00
|
|
|
QTest::qSleep(10);
|
|
|
|
}
|
|
|
|
|
|
|
|
return spy.size();
|
|
|
|
}
|
|
|
|
|
2022-07-16 19:54:54 +00:00
|
|
|
template <typename... Args>
|
|
|
|
void maybeInvokeSetupMethod(QObject *setupObject, const char *member, Args &&... args)
|
2018-12-06 11:47:30 +00:00
|
|
|
{
|
|
|
|
// It's OK if it doesn't exist: since we have more than one callback that
|
|
|
|
// can be called, it makes sense if the user only implements one of them.
|
|
|
|
// We do this the long way rather than just calling the static
|
|
|
|
// QMetaObject::invokeMethod(), because that will issue a warning if the
|
|
|
|
// function doesn't exist, which we don't want.
|
|
|
|
const QMetaObject *setupMetaObject = setupObject->metaObject();
|
|
|
|
const int methodIndex = setupMetaObject->indexOfMethod(member);
|
|
|
|
if (methodIndex != -1) {
|
|
|
|
const QMetaMethod method = setupMetaObject->method(methodIndex);
|
2022-07-16 19:54:54 +00:00
|
|
|
method.invoke(setupObject, std::forward<Args>(args)...);
|
2018-12-06 11:47:30 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
using namespace QV4::CompiledData;
|
|
|
|
|
|
|
|
class TestCaseCollector
|
|
|
|
{
|
|
|
|
public:
|
|
|
|
typedef QList<QString> TestCaseList;
|
|
|
|
|
|
|
|
TestCaseCollector(const QFileInfo &fileInfo, QQmlEngine *engine)
|
|
|
|
{
|
2018-04-25 15:19:00 +00:00
|
|
|
QString path = fileInfo.absoluteFilePath();
|
|
|
|
if (path.startsWith(QLatin1String(":/")))
|
|
|
|
path.prepend(QLatin1String("qrc"));
|
|
|
|
|
|
|
|
QQmlComponent component(engine, path);
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
m_errors += component.errors();
|
|
|
|
|
|
|
|
if (component.isReady()) {
|
2019-05-07 10:47:33 +00:00
|
|
|
QQmlRefPointer<QV4::ExecutableCompilationUnit> rootCompilationUnit
|
|
|
|
= QQmlComponentPrivate::get(&component)->compilationUnit;
|
2018-04-23 11:28:58 +00:00
|
|
|
TestCaseEnumerationResult result = enumerateTestCases(rootCompilationUnit.data());
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
m_testCases = result.testCases + result.finalizedPartialTestCases();
|
|
|
|
m_errors += result.errors;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
TestCaseList testCases() const { return m_testCases; }
|
|
|
|
QList<QQmlError> errors() const { return m_errors; }
|
|
|
|
|
|
|
|
private:
|
|
|
|
TestCaseList m_testCases;
|
|
|
|
QList<QQmlError> m_errors;
|
|
|
|
|
|
|
|
struct TestCaseEnumerationResult
|
|
|
|
{
|
|
|
|
TestCaseList testCases;
|
|
|
|
QList<QQmlError> errors;
|
|
|
|
|
|
|
|
// Partially constructed test cases
|
|
|
|
bool isTestCase = false;
|
|
|
|
TestCaseList testFunctions;
|
|
|
|
QString testCaseName;
|
|
|
|
|
|
|
|
TestCaseList finalizedPartialTestCases() const
|
|
|
|
{
|
|
|
|
TestCaseList result;
|
|
|
|
for (const QString &function : testFunctions)
|
|
|
|
result << QString(QStringLiteral("%1::%2")).arg(testCaseName).arg(function);
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
|
|
|
|
TestCaseEnumerationResult &operator<<(const TestCaseEnumerationResult &other)
|
|
|
|
{
|
|
|
|
testCases += other.testCases + other.finalizedPartialTestCases();
|
|
|
|
errors += other.errors;
|
|
|
|
return *this;
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2020-03-24 17:21:15 +00:00
|
|
|
TestCaseEnumerationResult enumerateTestCases(
|
|
|
|
const QQmlRefPointer<QV4::ExecutableCompilationUnit> &compilationUnit,
|
|
|
|
const Object *object = nullptr)
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
{
|
|
|
|
QQmlType testCaseType;
|
2018-07-27 09:36:43 +00:00
|
|
|
for (quint32 i = 0, count = compilationUnit->importCount(); i < count; ++i) {
|
|
|
|
const Import *import = compilationUnit->importAt(i);
|
2019-06-11 17:35:19 +00:00
|
|
|
if (compilationUnit->stringAt(import->uriIndex) != QLatin1String("QtTest"))
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
continue;
|
|
|
|
|
|
|
|
QString testCaseTypeName(QStringLiteral("TestCase"));
|
|
|
|
QString typeQualifier = compilationUnit->stringAt(import->qualifierIndex);
|
|
|
|
if (!typeQualifier.isEmpty())
|
|
|
|
testCaseTypeName = typeQualifier % QLatin1Char('.') % testCaseTypeName;
|
|
|
|
|
|
|
|
testCaseType = compilationUnit->typeNameCache->query(testCaseTypeName).type;
|
|
|
|
if (testCaseType.isValid())
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
|
|
|
|
TestCaseEnumerationResult result;
|
|
|
|
|
|
|
|
if (!object) // Start at root of compilation unit if not enumerating a specific child
|
2017-09-20 09:38:16 +00:00
|
|
|
object = compilationUnit->objectAt(0);
|
2022-05-05 10:17:11 +00:00
|
|
|
if (object->hasFlag(Object::IsInlineComponentRoot))
|
2021-01-29 14:50:39 +00:00
|
|
|
return result;
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
|
2020-03-24 17:21:15 +00:00
|
|
|
if (const auto superTypeUnit = compilationUnit->resolvedTypes.value(
|
|
|
|
object->inheritedTypeNameIndex)->compilationUnit()) {
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
// We have a non-C++ super type, which could indicate we're a subtype of a TestCase
|
|
|
|
if (testCaseType.isValid() && superTypeUnit->url() == testCaseType.sourceUrl())
|
|
|
|
result.isTestCase = true;
|
2021-01-29 14:50:39 +00:00
|
|
|
else if (superTypeUnit->url() != compilationUnit->url()) { // urls are the same for inline component, avoid infinite recursion
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
result = enumerateTestCases(superTypeUnit);
|
2021-01-29 14:50:39 +00:00
|
|
|
}
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
|
|
|
|
if (result.isTestCase) {
|
|
|
|
// Look for override of name in this type
|
|
|
|
for (auto binding = object->bindingsBegin(); binding != object->bindingsEnd(); ++binding) {
|
2019-06-11 17:35:19 +00:00
|
|
|
if (compilationUnit->stringAt(binding->propertyNameIndex) == QLatin1String("name")) {
|
2022-05-04 13:26:30 +00:00
|
|
|
if (binding->type() == QV4::CompiledData::Binding::Type_String) {
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
result.testCaseName = compilationUnit->stringAt(binding->stringIndex);
|
|
|
|
} else {
|
|
|
|
QQmlError error;
|
|
|
|
error.setUrl(compilationUnit->url());
|
2022-05-03 12:52:37 +00:00
|
|
|
error.setLine(binding->location.line());
|
|
|
|
error.setColumn(binding->location.column());
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
error.setDescription(QStringLiteral("the 'name' property of a TestCase must be a literal string"));
|
|
|
|
result.errors << error;
|
|
|
|
}
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Look for additional functions in this type
|
|
|
|
auto functionsEnd = compilationUnit->objectFunctionsEnd(object);
|
|
|
|
for (auto function = compilationUnit->objectFunctionsBegin(object); function != functionsEnd; ++function) {
|
|
|
|
QString functionName = compilationUnit->stringAt(function->nameIndex);
|
2019-06-11 17:35:19 +00:00
|
|
|
if (!(functionName.startsWith(QLatin1String("test_")) || functionName.startsWith(QLatin1String("benchmark_"))))
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
continue;
|
|
|
|
|
2019-06-11 17:35:19 +00:00
|
|
|
if (functionName.endsWith(QLatin1String("_data")))
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
continue;
|
|
|
|
|
|
|
|
result.testFunctions << functionName;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
for (auto binding = object->bindingsBegin(); binding != object->bindingsEnd(); ++binding) {
|
2022-05-04 13:26:30 +00:00
|
|
|
if (binding->type() == QV4::CompiledData::Binding::Type_Object) {
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
const Object *child = compilationUnit->objectAt(binding->value.objectIndex);
|
|
|
|
result << enumerateTestCases(compilationUnit, child);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return result;
|
|
|
|
}
|
|
|
|
};
|
|
|
|
|
2012-04-17 05:23:21 +00:00
|
|
|
int quick_test_main(int argc, char **argv, const char *name, const char *sourceDir)
|
2018-01-19 08:02:39 +00:00
|
|
|
{
|
|
|
|
return quick_test_main_with_setup(argc, argv, name, sourceDir, nullptr);
|
|
|
|
}
|
|
|
|
|
|
|
|
int quick_test_main_with_setup(int argc, char **argv, const char *name, const char *sourceDir, QObject *setup)
|
2011-05-20 01:57:29 +00:00
|
|
|
{
|
2021-11-08 12:53:11 +00:00
|
|
|
QScopedPointer<QCoreApplication> app;
|
2021-01-29 16:05:19 +00:00
|
|
|
if (!QCoreApplication::instance())
|
2021-11-08 12:53:11 +00:00
|
|
|
app.reset(new QGuiApplication(argc, argv));
|
2014-03-25 15:22:03 +00:00
|
|
|
|
2018-12-06 11:47:30 +00:00
|
|
|
if (setup)
|
|
|
|
maybeInvokeSetupMethod(setup, "applicationAvailable()");
|
2018-06-12 07:11:17 +00:00
|
|
|
|
2011-05-20 01:57:29 +00:00
|
|
|
// Look for QML-specific command-line options.
|
|
|
|
// -import dir Specify an import directory.
|
2014-12-16 13:55:08 +00:00
|
|
|
// -plugins dir Specify a directory where to search for plugins.
|
2011-05-20 01:57:29 +00:00
|
|
|
// -input dir Specify the input directory for test cases.
|
2011-10-27 06:55:43 +00:00
|
|
|
// -translation file Specify the translation file.
|
2017-11-24 15:50:03 +00:00
|
|
|
// -file-selector Specify a file selector
|
2011-05-20 01:57:29 +00:00
|
|
|
QStringList imports;
|
2014-12-16 13:55:08 +00:00
|
|
|
QStringList pluginPaths;
|
2011-05-20 01:57:29 +00:00
|
|
|
QString testPath;
|
2011-10-27 06:55:43 +00:00
|
|
|
QString translationFile;
|
2017-11-24 15:50:03 +00:00
|
|
|
QStringList fileSelectors;
|
2011-05-20 01:57:29 +00:00
|
|
|
int index = 1;
|
2014-03-06 15:54:32 +00:00
|
|
|
QScopedArrayPointer<char *> testArgV(new char *[argc + 1]);
|
|
|
|
testArgV[0] = argv[0];
|
|
|
|
int testArgC = 1;
|
2011-05-20 01:57:29 +00:00
|
|
|
while (index < argc) {
|
|
|
|
if (strcmp(argv[index], "-import") == 0 && (index + 1) < argc) {
|
|
|
|
imports += stripQuotes(QString::fromLocal8Bit(argv[index + 1]));
|
|
|
|
index += 2;
|
2014-12-16 13:55:08 +00:00
|
|
|
} else if (strcmp(argv[index], "-plugins") == 0 && (index + 1) < argc) {
|
|
|
|
pluginPaths += stripQuotes(QString::fromLocal8Bit(argv[index + 1]));
|
|
|
|
index += 2;
|
2011-05-20 01:57:29 +00:00
|
|
|
} else if (strcmp(argv[index], "-input") == 0 && (index + 1) < argc) {
|
|
|
|
testPath = stripQuotes(QString::fromLocal8Bit(argv[index + 1]));
|
|
|
|
index += 2;
|
|
|
|
} else if (strcmp(argv[index], "-opengl") == 0) {
|
|
|
|
++index;
|
2011-10-27 06:55:43 +00:00
|
|
|
} else if (strcmp(argv[index], "-translation") == 0 && (index + 1) < argc) {
|
|
|
|
translationFile = stripQuotes(QString::fromLocal8Bit(argv[index + 1]));
|
|
|
|
index += 2;
|
2017-11-24 15:50:03 +00:00
|
|
|
} else if (strcmp(argv[index], "-file-selector") == 0 && (index + 1) < argc) {
|
|
|
|
fileSelectors += stripQuotes(QString::fromLocal8Bit(argv[index + 1]));
|
|
|
|
index += 2;
|
2011-05-20 01:57:29 +00:00
|
|
|
} else {
|
2014-03-06 15:54:32 +00:00
|
|
|
testArgV[testArgC++] = argv[index++];
|
2011-05-20 01:57:29 +00:00
|
|
|
}
|
|
|
|
}
|
2014-03-06 15:54:32 +00:00
|
|
|
testArgV[testArgC] = 0;
|
2011-05-20 01:57:29 +00:00
|
|
|
|
2012-02-16 11:18:43 +00:00
|
|
|
// Setting currentAppname and currentTestObjectName (via setProgramName) are needed
|
|
|
|
// for the code coverage analysis. Must be done before parseArgs is called.
|
|
|
|
QuickTestResult::setCurrentAppname(argv[0]);
|
2011-08-08 01:35:48 +00:00
|
|
|
QuickTestResult::setProgramName(name);
|
|
|
|
|
2014-03-06 15:54:32 +00:00
|
|
|
QuickTestResult::parseArgs(testArgC, testArgV.data());
|
2011-11-29 09:48:21 +00:00
|
|
|
|
2016-11-16 13:22:36 +00:00
|
|
|
#if QT_CONFIG(translation)
|
2011-10-27 06:55:43 +00:00
|
|
|
QTranslator translator;
|
|
|
|
if (!translationFile.isEmpty()) {
|
|
|
|
if (translator.load(translationFile)) {
|
|
|
|
app->installTranslator(&translator);
|
|
|
|
} else {
|
2012-01-06 12:25:51 +00:00
|
|
|
qWarning("Could not load the translation file '%s'.", qPrintable(translationFile));
|
2011-10-27 06:55:43 +00:00
|
|
|
}
|
|
|
|
}
|
2012-11-22 19:21:49 +00:00
|
|
|
#endif
|
2011-10-27 06:55:43 +00:00
|
|
|
|
2011-05-20 01:57:29 +00:00
|
|
|
// Determine where to look for the test data.
|
2012-02-27 01:11:10 +00:00
|
|
|
if (testPath.isEmpty() && sourceDir) {
|
|
|
|
const QString s = QString::fromLocal8Bit(sourceDir);
|
|
|
|
if (QFile::exists(s))
|
|
|
|
testPath = s;
|
|
|
|
}
|
2020-08-07 09:32:33 +00:00
|
|
|
|
2022-02-22 09:47:55 +00:00
|
|
|
#if defined(Q_OS_ANDROID) || defined(Q_OS_INTEGRITY)
|
2020-08-07 09:32:33 +00:00
|
|
|
if (testPath.isEmpty())
|
|
|
|
testPath = QLatin1String(":/");
|
|
|
|
#endif
|
|
|
|
|
2012-01-06 12:25:51 +00:00
|
|
|
if (testPath.isEmpty()) {
|
|
|
|
QDir current = QDir::current();
|
|
|
|
#ifdef Q_OS_WIN
|
|
|
|
// Skip release/debug subfolders
|
|
|
|
if (!current.dirName().compare(QLatin1String("Release"), Qt::CaseInsensitive)
|
|
|
|
|| !current.dirName().compare(QLatin1String("Debug"), Qt::CaseInsensitive))
|
|
|
|
current.cdUp();
|
|
|
|
#endif // Q_OS_WIN
|
|
|
|
testPath = current.absolutePath();
|
|
|
|
}
|
2011-05-20 01:57:29 +00:00
|
|
|
QStringList files;
|
2011-10-10 01:30:15 +00:00
|
|
|
|
2012-01-06 12:25:51 +00:00
|
|
|
const QFileInfo testPathInfo(testPath);
|
|
|
|
if (testPathInfo.isFile()) {
|
2020-04-02 16:56:18 +00:00
|
|
|
if (testPath.endsWith(QLatin1String(".qml"))) {
|
|
|
|
files << testPath;
|
|
|
|
} else if (testPath.endsWith(QLatin1String(".qmltests"))) {
|
|
|
|
QFile file(testPath);
|
|
|
|
if (file.open(QIODevice::ReadOnly)) {
|
|
|
|
while (!file.atEnd()) {
|
|
|
|
const QString filePath = testPathInfo.dir()
|
|
|
|
.filePath(QString::fromUtf8(file.readLine()))
|
|
|
|
.trimmed();
|
|
|
|
const QFileInfo f(filePath);
|
|
|
|
if (f.exists())
|
|
|
|
files.append(filePath);
|
|
|
|
else
|
|
|
|
qWarning("The test file '%s' does not exists", qPrintable(filePath));
|
|
|
|
}
|
|
|
|
file.close();
|
|
|
|
files.sort();
|
|
|
|
if (files.isEmpty()) {
|
|
|
|
qWarning("The file '%s' does not contain any tests files",
|
|
|
|
qPrintable(testPath));
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
qWarning("Could not read '%s'", qPrintable(testPath));
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
qWarning("'%s' does not have the suffix '.qml' or '.qmltests'.", qPrintable(testPath));
|
2012-01-06 12:25:51 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
} else if (testPathInfo.isDir()) {
|
2011-10-10 01:30:15 +00:00
|
|
|
// Scan the test data directory recursively, looking for "tst_*.qml" files.
|
2012-01-06 12:25:51 +00:00
|
|
|
const QStringList filters(QStringLiteral("tst_*.qml"));
|
|
|
|
QDirIterator iter(testPathInfo.absoluteFilePath(), filters, QDir::Files,
|
2011-10-10 01:30:15 +00:00
|
|
|
QDirIterator::Subdirectories |
|
|
|
|
QDirIterator::FollowSymlinks);
|
|
|
|
while (iter.hasNext())
|
|
|
|
files += iter.next();
|
|
|
|
files.sort();
|
2012-01-06 12:25:51 +00:00
|
|
|
if (files.isEmpty()) {
|
|
|
|
qWarning("The directory '%s' does not contain any test files matching '%s'",
|
|
|
|
qPrintable(testPath), qPrintable(filters.front()));
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
} else {
|
|
|
|
qWarning("'%s' does not exist under '%s'.",
|
|
|
|
qPrintable(testPath), qPrintable(QDir::currentPath()));
|
2011-05-20 01:57:29 +00:00
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2015-09-09 11:54:03 +00:00
|
|
|
qputenv("QT_QTESTLIB_RUNNING", "1");
|
|
|
|
|
Fix deprecation warnings in 5.14
Libraries:
scenegraph/util/qsgdepthstencilbuffer.cpp:186:57: warning: 'T* QWeakPointer<T>::data() const [with T = QSGDepthStencilBuffer]' is deprecated: Use toStrongRef() instead, and data() on the returned QSharedPointer [-Wdeprecated-declarations]
scenegraph/qsgdefaultcontext.cpp:163:89: warning: 'QList<T> QSet<T>::toList() const [with T = QByteArray]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
util/qquickpath.cpp:573:40: warning: 'QList<T> QSet<T>::toList() const [with T = QString]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
util/qquickpath.cpp:606:29: warning: 'QList<T> QSet<T>::toList() const [with T = QString]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
quicktest.cpp:562:73: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
quicktest.cpp:604:77: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
qquickitemparticle.cpp:233:49: warning: 'static QSet<T> QSet<T>::fromList(const QList<T>&) [with T = QQuickItem*]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
qquickitemparticle.cpp:239:37: warning: 'QList<T> QSet<T>::toList() const [with T = QQuickItem*]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
Tests:
tst_propertyrequirements.cpp:123:58: warning: 'QList<T> QSet<T>::toList() const [with T = QString]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
tst_propertyrequirements.cpp:161:40: warning: 'static QSet<T> QSet<T>::fromList(const QList<T>&) [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_propertyrequirements.cpp:161:77: warning: 'static QSet<T> QSet<T>::fromList(const QList<T>&) [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
/data1/frkleint/qt-dev/qtbase/include/QtCore/../../src/corelib/tools/qset.h:400:23: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
../shared/viewtestutil.cpp:331:26: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
...
tst_qmldiskcache.cpp:651:81: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:663:81: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:693:85: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:918:81: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:940:69: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickgridview.cpp:6437:70: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickgridview.cpp:6438:46: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickgridview.cpp:6440:66: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquicktableview.cpp:53:20: warning: 'kTableViewPropName' defined but not used [-Wunused-variable]
tst_qquicklistview.cpp:7269:70: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquicklistview.cpp:7270:46: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquicklistview.cpp:7272:66: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickpositioners.cpp:4033:70: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickpositioners.cpp:4034:46: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickpositioners.cpp:4036:66: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
Change-Id: I9a177f83f07ae5162f7cc231a8c164ba32ffa5bc
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2019-05-27 13:04:25 +00:00
|
|
|
QSet<QString> commandLineTestFunctions(QTest::testFunctions.cbegin(), QTest::testFunctions.cend());
|
2018-05-09 11:58:36 +00:00
|
|
|
const bool filteringTestFunctions = !commandLineTestFunctions.isEmpty();
|
|
|
|
|
2011-05-20 01:57:29 +00:00
|
|
|
// Scan through all of the "tst_*.qml" files and run each of them
|
2017-09-04 15:42:35 +00:00
|
|
|
// in turn with a separate QQuickView (for test isolation).
|
2022-10-06 09:30:50 +00:00
|
|
|
for (const QString &file : std::as_const(files)) {
|
2012-10-18 13:02:36 +00:00
|
|
|
const QFileInfo fi(file);
|
2012-03-08 04:04:25 +00:00
|
|
|
if (!fi.exists())
|
|
|
|
continue;
|
2011-10-14 03:07:37 +00:00
|
|
|
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
QQmlEngine engine;
|
2022-10-06 09:30:50 +00:00
|
|
|
for (const QString &path : std::as_const(imports))
|
2017-09-15 08:07:32 +00:00
|
|
|
engine.addImportPath(path);
|
2022-10-06 09:30:50 +00:00
|
|
|
for (const QString &path : std::as_const(pluginPaths))
|
2017-09-15 08:07:32 +00:00
|
|
|
engine.addPluginPath(path);
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
|
2017-11-24 15:50:03 +00:00
|
|
|
if (!fileSelectors.isEmpty()) {
|
|
|
|
QQmlFileSelector* const qmlFileSelector = new QQmlFileSelector(&engine, &engine);
|
|
|
|
qmlFileSelector->setExtraSelectors(fileSelectors);
|
|
|
|
}
|
|
|
|
|
2019-03-08 09:51:57 +00:00
|
|
|
// Do this down here so that import paths, plugin paths, file selectors, etc. are available
|
|
|
|
// in case the user needs access to them. Do it _before_ the TestCaseCollector parses the
|
|
|
|
// QML files though, because it attempts to import modules, which might not be available
|
|
|
|
// if qmlRegisterType()/QQmlEngine::addImportPath() are called in qmlEngineAvailable().
|
|
|
|
if (setup)
|
2018-12-06 11:47:30 +00:00
|
|
|
maybeInvokeSetupMethod(setup, "qmlEngineAvailable(QQmlEngine*)", Q_ARG(QQmlEngine*, &engine));
|
2019-03-08 09:51:57 +00:00
|
|
|
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
TestCaseCollector testCaseCollector(fi, &engine);
|
|
|
|
if (!testCaseCollector.errors().isEmpty()) {
|
2021-11-08 12:53:11 +00:00
|
|
|
handleCompileErrors(fi, testCaseCollector.errors(), &engine);
|
|
|
|
continue;
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
TestCaseCollector::TestCaseList availableTestFunctions = testCaseCollector.testCases();
|
|
|
|
if (QTest::printAvailableFunctions) {
|
|
|
|
for (const QString &function : availableTestFunctions)
|
|
|
|
qDebug("%s()", qPrintable(function));
|
|
|
|
continue;
|
|
|
|
}
|
|
|
|
|
Fix deprecation warnings in 5.14
Libraries:
scenegraph/util/qsgdepthstencilbuffer.cpp:186:57: warning: 'T* QWeakPointer<T>::data() const [with T = QSGDepthStencilBuffer]' is deprecated: Use toStrongRef() instead, and data() on the returned QSharedPointer [-Wdeprecated-declarations]
scenegraph/qsgdefaultcontext.cpp:163:89: warning: 'QList<T> QSet<T>::toList() const [with T = QByteArray]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
util/qquickpath.cpp:573:40: warning: 'QList<T> QSet<T>::toList() const [with T = QString]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
util/qquickpath.cpp:606:29: warning: 'QList<T> QSet<T>::toList() const [with T = QString]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
quicktest.cpp:562:73: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
quicktest.cpp:604:77: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
qquickitemparticle.cpp:233:49: warning: 'static QSet<T> QSet<T>::fromList(const QList<T>&) [with T = QQuickItem*]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
qquickitemparticle.cpp:239:37: warning: 'QList<T> QSet<T>::toList() const [with T = QQuickItem*]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
Tests:
tst_propertyrequirements.cpp:123:58: warning: 'QList<T> QSet<T>::toList() const [with T = QString]' is deprecated: Use values() instead. [-Wdeprecated-declarations]
tst_propertyrequirements.cpp:161:40: warning: 'static QSet<T> QSet<T>::fromList(const QList<T>&) [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_propertyrequirements.cpp:161:77: warning: 'static QSet<T> QSet<T>::fromList(const QList<T>&) [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
/data1/frkleint/qt-dev/qtbase/include/QtCore/../../src/corelib/tools/qset.h:400:23: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
../shared/viewtestutil.cpp:331:26: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
...
tst_qmldiskcache.cpp:651:81: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:663:81: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:693:85: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:918:81: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qmldiskcache.cpp:940:69: warning: 'QSet<T> QList<T>::toSet() const [with T = QString]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickgridview.cpp:6437:70: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickgridview.cpp:6438:46: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickgridview.cpp:6440:66: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquicktableview.cpp:53:20: warning: 'kTableViewPropName' defined but not used [-Wunused-variable]
tst_qquicklistview.cpp:7269:70: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquicklistview.cpp:7270:46: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquicklistview.cpp:7272:66: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickpositioners.cpp:4033:70: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickpositioners.cpp:4034:46: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
tst_qquickpositioners.cpp:4036:66: warning: 'QSet<T> QList<T>::toSet() const [with T = int]' is deprecated: Use QSet<T>(list.begin(), list.end()) instead. [-Wdeprecated-declarations]
Change-Id: I9a177f83f07ae5162f7cc231a8c164ba32ffa5bc
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2019-05-27 13:04:25 +00:00
|
|
|
const QSet<QString> availableTestSet(availableTestFunctions.cbegin(), availableTestFunctions.cend());
|
2018-05-09 11:58:36 +00:00
|
|
|
if (filteringTestFunctions && !availableTestSet.intersects(commandLineTestFunctions))
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
continue;
|
2018-05-09 11:58:36 +00:00
|
|
|
commandLineTestFunctions.subtract(availableTestSet);
|
qmltest: Enumerate test cases / functions without evaluating QML
Most, if not all, QML tests are written without any sort of dynamic
instantiation of the test data, so doing view.setSource() will evaluate
the whole source file, compute bindings, create items, windows, etc.
This is less then ideal when all you want is to list the test functions
using -functions, or when running a single test from the command line,
as in both cases we'll still actually evaluate every single QML file.
This makes it really hard to evaluate test output, e.g. from the CI,
especially with logging enabled, as even if a single test is requested,
the logs are filled with results from the loading of the other tests.
To improve the situation we use a non-instantiated QML component that
we then inspect its compilation data, looking for test cases and
functions.
In the future the implementation of TestCase's qtest_run* machinery
should be built on top of QTestLib instead of being reimplemented in
JavaScript, but this is left for later.
Change-Id: Ie5448208daf786e335583ab6bdfbc195891ec1f5
Reviewed-by: Simon Hausmann <simon.hausmann@qt.io>
2017-09-06 10:43:16 +00:00
|
|
|
|
|
|
|
QQuickView view(&engine, nullptr);
|
2017-09-04 15:42:35 +00:00
|
|
|
view.setFlags(Qt::Window | Qt::WindowSystemMenuHint
|
|
|
|
| Qt::WindowTitleHint | Qt::WindowMinMaxButtonsHint
|
|
|
|
| Qt::WindowCloseButtonHint);
|
|
|
|
QEventLoop eventLoop;
|
|
|
|
QObject::connect(view.engine(), SIGNAL(quit()),
|
|
|
|
QTestRootObject::instance(), SLOT(quit()));
|
|
|
|
QObject::connect(view.engine(), SIGNAL(quit()),
|
|
|
|
&eventLoop, SLOT(quit()));
|
|
|
|
view.rootContext()->setContextProperty
|
2021-01-04 17:45:18 +00:00
|
|
|
(QLatin1String("qtest"), QTestRootObject::instance()); // Deprecated. Use QTestRootObject from QtTest instead
|
2017-09-04 15:42:35 +00:00
|
|
|
|
|
|
|
view.setObjectName(fi.baseName());
|
|
|
|
view.setTitle(view.objectName());
|
2013-08-22 11:13:00 +00:00
|
|
|
QTestRootObject::instance()->init();
|
2012-03-08 04:04:25 +00:00
|
|
|
QString path = fi.absoluteFilePath();
|
|
|
|
if (path.startsWith(QLatin1String(":/")))
|
2020-06-16 08:23:19 +00:00
|
|
|
view.setSource(QUrl(QLatin1String("qrc:") + QStringView{path}.mid(1)));
|
2012-03-08 04:04:25 +00:00
|
|
|
else
|
2017-09-04 15:42:35 +00:00
|
|
|
view.setSource(QUrl::fromLocalFile(path));
|
2011-10-24 00:44:16 +00:00
|
|
|
|
2017-09-04 15:42:35 +00:00
|
|
|
while (view.status() == QQuickView::Loading)
|
2015-03-24 01:58:09 +00:00
|
|
|
QTest::qWait(10);
|
2017-09-04 15:42:35 +00:00
|
|
|
if (view.status() == QQuickView::Error) {
|
2021-11-08 12:53:11 +00:00
|
|
|
handleCompileErrors(fi, view.errors(), view.engine(), &view);
|
2012-03-08 04:04:25 +00:00
|
|
|
continue;
|
|
|
|
}
|
2013-08-22 11:13:00 +00:00
|
|
|
if (!QTestRootObject::instance()->hasQuit) {
|
2012-03-08 04:04:25 +00:00
|
|
|
// If the test already quit, then it was performed
|
|
|
|
// synchronously during setSource(). Otherwise it is
|
|
|
|
// an asynchronous test and we need to show the window
|
2012-06-12 04:46:12 +00:00
|
|
|
// and wait for the first frame to be rendered
|
|
|
|
// and then wait for quit indication.
|
2017-09-04 15:42:35 +00:00
|
|
|
view.setFramePosition(QPoint(50, 50));
|
|
|
|
if (view.size().isEmpty()) { // Avoid hangs with empty windows.
|
|
|
|
view.resize(200, 200);
|
2012-10-18 13:02:36 +00:00
|
|
|
}
|
2017-09-04 15:42:35 +00:00
|
|
|
view.show();
|
|
|
|
if (!QTest::qWaitForWindowExposed(&view)) {
|
2015-03-24 01:58:09 +00:00
|
|
|
qWarning().nospace()
|
|
|
|
<< "Test '" << QDir::toNativeSeparators(path) << "' window not exposed after show().";
|
|
|
|
}
|
2017-09-04 15:42:35 +00:00
|
|
|
view.requestActivate();
|
|
|
|
if (!QTest::qWaitForWindowActive(&view)) {
|
2015-03-24 01:58:09 +00:00
|
|
|
qWarning().nospace()
|
|
|
|
<< "Test '" << QDir::toNativeSeparators(path) << "' window not active after requestActivate().";
|
|
|
|
}
|
2017-09-04 15:42:35 +00:00
|
|
|
if (view.isExposed()) {
|
2019-02-12 13:19:19 +00:00
|
|
|
// Defer property update until event loop has started
|
|
|
|
QTimer::singleShot(0, []() {
|
|
|
|
QTestRootObject::instance()->setWindowShown(true);
|
|
|
|
});
|
2015-03-24 01:58:09 +00:00
|
|
|
} else {
|
|
|
|
qWarning().nospace()
|
|
|
|
<< "Test '" << QDir::toNativeSeparators(path) << "' window was never exposed! "
|
|
|
|
<< "If the test case was expecting windowShown, it will hang.";
|
|
|
|
}
|
2013-08-22 11:13:00 +00:00
|
|
|
if (!QTestRootObject::instance()->hasQuit && QTestRootObject::instance()->hasTestCase())
|
2012-03-08 04:04:25 +00:00
|
|
|
eventLoop.exec();
|
2011-05-20 01:57:29 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2018-12-06 11:47:30 +00:00
|
|
|
if (setup)
|
|
|
|
maybeInvokeSetupMethod(setup, "cleanupTestCase()");
|
2018-09-20 08:51:18 +00:00
|
|
|
|
2011-05-20 01:57:29 +00:00
|
|
|
// Flush the current logging stream.
|
2018-02-21 09:41:54 +00:00
|
|
|
QuickTestResult::setProgramName(nullptr);
|
2021-11-08 12:53:11 +00:00
|
|
|
app.reset();
|
2012-01-13 00:47:25 +00:00
|
|
|
|
2018-05-09 11:58:36 +00:00
|
|
|
// Check that all test functions passed on the command line were found
|
|
|
|
if (!commandLineTestFunctions.isEmpty()) {
|
|
|
|
qWarning() << "Could not find the following test functions:";
|
2022-10-06 09:30:50 +00:00
|
|
|
for (const QString &functionName : std::as_const(commandLineTestFunctions))
|
2018-05-09 11:58:36 +00:00
|
|
|
qWarning(" %s()", qUtf8Printable(functionName));
|
2022-10-05 05:29:16 +00:00
|
|
|
return commandLineTestFunctions.size();
|
2018-05-09 11:58:36 +00:00
|
|
|
}
|
|
|
|
|
2011-05-20 01:57:29 +00:00
|
|
|
// Return the number of failures as the exit code.
|
|
|
|
return QuickTestResult::exitCode();
|
|
|
|
}
|
|
|
|
|
|
|
|
QT_END_NAMESPACE
|
2022-04-28 14:29:36 +00:00
|
|
|
|
|
|
|
#include "moc_quicktest_p.cpp"
|