2011-04-27 10:05:43 +00:00
|
|
|
/****************************************************************************
|
|
|
|
**
|
2012-01-05 04:03:39 +00:00
|
|
|
** Copyright (C) 2012 Nokia Corporation and/or its subsidiary(-ies).
|
2011-04-27 10:05:43 +00:00
|
|
|
** All rights reserved.
|
2012-01-20 03:06:31 +00:00
|
|
|
** Contact: http://www.qt-project.org/
|
2011-04-27 10:05:43 +00:00
|
|
|
**
|
|
|
|
** This file is part of the QtTest module of the Qt Toolkit.
|
|
|
|
**
|
|
|
|
** $QT_BEGIN_LICENSE:LGPL$
|
|
|
|
** GNU Lesser General Public License Usage
|
2011-05-24 09:34:08 +00:00
|
|
|
** This file may be used under the terms of the GNU Lesser General Public
|
|
|
|
** License version 2.1 as published by the Free Software Foundation and
|
|
|
|
** appearing in the file LICENSE.LGPL included in the packaging of this
|
|
|
|
** file. Please review the following information to ensure the GNU Lesser
|
|
|
|
** General Public License version 2.1 requirements will be met:
|
|
|
|
** http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
|
2011-04-27 10:05:43 +00:00
|
|
|
**
|
|
|
|
** In addition, as a special exception, Nokia gives you certain additional
|
2011-05-24 09:34:08 +00:00
|
|
|
** rights. These rights are described in the Nokia Qt LGPL Exception
|
2011-04-27 10:05:43 +00:00
|
|
|
** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
|
|
|
|
**
|
2011-05-24 09:34:08 +00:00
|
|
|
** GNU General Public License Usage
|
|
|
|
** Alternatively, this file may be used under the terms of the GNU General
|
|
|
|
** Public License version 3.0 as published by the Free Software Foundation
|
|
|
|
** and appearing in the file LICENSE.GPL included in the packaging of this
|
|
|
|
** file. Please review the following information to ensure the GNU General
|
|
|
|
** Public License version 3.0 requirements will be met:
|
|
|
|
** http://www.gnu.org/copyleft/gpl.html.
|
|
|
|
**
|
|
|
|
** Other Usage
|
|
|
|
** Alternatively, this file may be used in accordance with the terms and
|
|
|
|
** conditions contained in a signed written agreement between you and Nokia.
|
2011-04-27 10:05:43 +00:00
|
|
|
**
|
|
|
|
**
|
|
|
|
**
|
|
|
|
**
|
|
|
|
**
|
|
|
|
** $QT_END_LICENSE$
|
|
|
|
**
|
|
|
|
****************************************************************************/
|
|
|
|
|
2011-10-21 00:07:51 +00:00
|
|
|
#include <QtTest/qtestassert.h>
|
2011-04-27 10:05:43 +00:00
|
|
|
|
2011-10-21 00:07:51 +00:00
|
|
|
#include <QtTest/private/qtestlog_p.h>
|
|
|
|
#include <QtTest/private/qtestresult_p.h>
|
|
|
|
#include <QtTest/private/qabstracttestlogger_p.h>
|
|
|
|
#include <QtTest/private/qplaintestlogger_p.h>
|
|
|
|
#include <QtTest/private/qxunittestlogger_p.h>
|
|
|
|
#include <QtTest/private/qxmltestlogger_p.h>
|
2011-04-27 10:05:43 +00:00
|
|
|
#include <QtCore/qatomic.h>
|
|
|
|
#include <QtCore/qbytearray.h>
|
|
|
|
|
|
|
|
#include <stdlib.h>
|
|
|
|
#include <string.h>
|
|
|
|
#include <limits.h>
|
|
|
|
|
|
|
|
QT_BEGIN_NAMESPACE
|
|
|
|
|
|
|
|
namespace QTest {
|
|
|
|
|
2012-01-16 05:12:39 +00:00
|
|
|
int fails = 0;
|
|
|
|
int passes = 0;
|
|
|
|
int skips = 0;
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
struct IgnoreResultList
|
|
|
|
{
|
|
|
|
inline IgnoreResultList(QtMsgType tp, const char *message)
|
|
|
|
: type(tp), next(0)
|
|
|
|
{ msg = qstrdup(message); }
|
|
|
|
inline ~IgnoreResultList()
|
|
|
|
{ delete [] msg; }
|
|
|
|
|
|
|
|
static inline void clearList(IgnoreResultList *&list)
|
|
|
|
{
|
|
|
|
while (list) {
|
|
|
|
IgnoreResultList *current = list;
|
|
|
|
list = list->next;
|
|
|
|
delete current;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
QtMsgType type;
|
|
|
|
char *msg;
|
|
|
|
IgnoreResultList *next;
|
|
|
|
};
|
|
|
|
|
|
|
|
static IgnoreResultList *ignoreResultList = 0;
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
struct LoggerList
|
|
|
|
{
|
|
|
|
QAbstractTestLogger *logger;
|
|
|
|
LoggerList *next;
|
|
|
|
};
|
|
|
|
|
|
|
|
class TestLoggers
|
|
|
|
{
|
|
|
|
public:
|
|
|
|
static void addLogger(QAbstractTestLogger *logger)
|
|
|
|
{
|
|
|
|
LoggerList *l = new LoggerList;
|
|
|
|
l->logger = logger;
|
|
|
|
l->next = loggers;
|
|
|
|
loggers = l;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void destroyLoggers()
|
|
|
|
{
|
|
|
|
while (loggers) {
|
|
|
|
LoggerList *l = loggers;
|
|
|
|
loggers = loggers->next;
|
|
|
|
delete l->logger;
|
|
|
|
delete l;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
#define FOREACH_LOGGER(operation) \
|
|
|
|
LoggerList *l = loggers; \
|
|
|
|
while (l) { \
|
|
|
|
QAbstractTestLogger *logger = l->logger; \
|
|
|
|
Q_UNUSED(logger); \
|
|
|
|
operation; \
|
|
|
|
l = l->next; \
|
|
|
|
}
|
|
|
|
|
|
|
|
static void startLogging()
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->startLogging());
|
|
|
|
}
|
|
|
|
|
|
|
|
static void stopLogging()
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->stopLogging());
|
|
|
|
}
|
|
|
|
|
|
|
|
static void enterTestFunction(const char *function)
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->enterTestFunction(function));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void leaveTestFunction()
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->leaveTestFunction());
|
|
|
|
}
|
|
|
|
|
|
|
|
static void addIncident(QAbstractTestLogger::IncidentTypes type, const char *description,
|
|
|
|
const char *file = 0, int line = 0)
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->addIncident(type, description, file, line));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void addBenchmarkResult(const QBenchmarkResult &result)
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->addBenchmarkResult(result));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void addMessage(QAbstractTestLogger::MessageTypes type, const char *message,
|
|
|
|
const char *file = 0, int line = 0)
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->addMessage(type, message, file, line));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void outputString(const char *msg)
|
|
|
|
{
|
|
|
|
FOREACH_LOGGER(logger->outputString(msg));
|
|
|
|
}
|
|
|
|
|
|
|
|
static int loggerCount()
|
|
|
|
{
|
|
|
|
int count = 0;
|
|
|
|
FOREACH_LOGGER(++count);
|
|
|
|
return count;
|
|
|
|
}
|
|
|
|
|
|
|
|
private:
|
|
|
|
static LoggerList *loggers;
|
|
|
|
};
|
|
|
|
|
|
|
|
#undef FOREACH_LOGGER
|
|
|
|
|
|
|
|
LoggerList *TestLoggers::loggers = 0;
|
|
|
|
static bool loggerUsingStdout = false;
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
static int verbosity = 0;
|
|
|
|
static int maxWarnings = 2002;
|
|
|
|
|
|
|
|
static QtMsgHandler oldMessageHandler;
|
|
|
|
|
|
|
|
static bool handleIgnoredMessage(QtMsgType type, const char *msg)
|
|
|
|
{
|
|
|
|
IgnoreResultList *last = 0;
|
|
|
|
IgnoreResultList *list = ignoreResultList;
|
|
|
|
while (list) {
|
|
|
|
if (list->type == type && strcmp(msg, list->msg) == 0) {
|
|
|
|
// remove the item from the list
|
|
|
|
if (last)
|
|
|
|
last->next = list->next;
|
|
|
|
else if (list->next)
|
|
|
|
ignoreResultList = list->next;
|
|
|
|
else
|
|
|
|
ignoreResultList = 0;
|
|
|
|
|
|
|
|
delete list;
|
|
|
|
return true;
|
|
|
|
}
|
|
|
|
|
|
|
|
last = list;
|
|
|
|
list = list->next;
|
|
|
|
}
|
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void messageHandler(QtMsgType type, const char *msg)
|
|
|
|
{
|
|
|
|
static QBasicAtomicInt counter = Q_BASIC_ATOMIC_INITIALIZER(QTest::maxWarnings);
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
if (!msg || QTest::TestLoggers::loggerCount() == 0) {
|
2011-04-27 10:05:43 +00:00
|
|
|
// if this goes wrong, something is seriously broken.
|
|
|
|
qInstallMsgHandler(oldMessageHandler);
|
|
|
|
QTEST_ASSERT(msg);
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTEST_ASSERT(QTest::TestLoggers::loggerCount() != 0);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
if (handleIgnoredMessage(type, msg))
|
|
|
|
// the message is expected, so just swallow it.
|
|
|
|
return;
|
|
|
|
|
|
|
|
if (type != QtFatalMsg) {
|
2011-07-05 21:46:19 +00:00
|
|
|
if (counter.load() <= 0)
|
2011-04-27 10:05:43 +00:00
|
|
|
return;
|
|
|
|
|
|
|
|
if (!counter.deref()) {
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::QSystem,
|
2011-04-27 10:05:43 +00:00
|
|
|
"Maximum amount of warnings exceeded. Use -maxwarnings to override.");
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
switch (type) {
|
|
|
|
case QtDebugMsg:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::QDebug, msg);
|
2011-04-27 10:05:43 +00:00
|
|
|
break;
|
|
|
|
case QtCriticalMsg:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::QSystem, msg);
|
2011-04-27 10:05:43 +00:00
|
|
|
break;
|
|
|
|
case QtWarningMsg:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::QWarning, msg);
|
2011-04-27 10:05:43 +00:00
|
|
|
break;
|
|
|
|
case QtFatalMsg:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::QFatal, msg);
|
2011-04-27 10:05:43 +00:00
|
|
|
/* Right now, we're inside the custom message handler and we're
|
|
|
|
* being qt_message_output in qglobal.cpp. After we return from
|
|
|
|
* this function, it will proceed with calling exit() and abort()
|
|
|
|
* and hence crash. Therefore, we call these logging functions such
|
|
|
|
* that we wrap up nicely, and in particular produce well-formed XML. */
|
|
|
|
QTestResult::addFailure("Received a fatal error.", "Unknown file", 0);
|
|
|
|
QTestLog::leaveTestFunction();
|
|
|
|
QTestLog::stopLogging();
|
|
|
|
break;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::enterTestFunction(const char* function)
|
|
|
|
{
|
2011-11-01 11:19:39 +00:00
|
|
|
if (printAvailableTags)
|
|
|
|
return;
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
QTEST_ASSERT(function);
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::enterTestFunction(function);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
int QTestLog::unhandledIgnoreMessages()
|
|
|
|
{
|
|
|
|
int i = 0;
|
|
|
|
QTest::IgnoreResultList *list = QTest::ignoreResultList;
|
|
|
|
while (list) {
|
|
|
|
++i;
|
|
|
|
list = list->next;
|
|
|
|
}
|
|
|
|
return i;
|
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::leaveTestFunction()
|
|
|
|
{
|
2011-11-01 11:19:39 +00:00
|
|
|
if (printAvailableTags)
|
|
|
|
return;
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
QTest::IgnoreResultList::clearList(QTest::ignoreResultList);
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::leaveTestFunction();
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::printUnhandledIgnoreMessages()
|
|
|
|
{
|
|
|
|
char msg[1024];
|
|
|
|
QTest::IgnoreResultList *list = QTest::ignoreResultList;
|
|
|
|
while (list) {
|
2011-12-12 02:23:02 +00:00
|
|
|
qsnprintf(msg, 1024, "Did not receive message: \"%s\"", list->msg);
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::Info, msg);
|
2011-04-27 10:05:43 +00:00
|
|
|
|
|
|
|
list = list->next;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::addPass(const char *msg)
|
|
|
|
{
|
2011-11-01 11:19:39 +00:00
|
|
|
if (printAvailableTags)
|
|
|
|
return;
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
QTEST_ASSERT(msg);
|
|
|
|
|
2012-01-16 05:12:39 +00:00
|
|
|
++QTest::passes;
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addIncident(QAbstractTestLogger::Pass, msg);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::addFail(const char *msg, const char *file, int line)
|
|
|
|
{
|
2011-08-24 08:20:44 +00:00
|
|
|
QTEST_ASSERT(msg);
|
2011-04-27 10:05:43 +00:00
|
|
|
|
2012-01-16 05:12:39 +00:00
|
|
|
++QTest::fails;
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addIncident(QAbstractTestLogger::Fail, msg, file, line);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::addXFail(const char *msg, const char *file, int line)
|
|
|
|
{
|
|
|
|
QTEST_ASSERT(msg);
|
|
|
|
QTEST_ASSERT(file);
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addIncident(QAbstractTestLogger::XFail, msg, file, line);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::addXPass(const char *msg, const char *file, int line)
|
|
|
|
{
|
|
|
|
QTEST_ASSERT(msg);
|
|
|
|
QTEST_ASSERT(file);
|
|
|
|
|
2012-01-16 05:12:39 +00:00
|
|
|
++QTest::fails;
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addIncident(QAbstractTestLogger::XPass, msg, file, line);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
2011-08-25 02:53:07 +00:00
|
|
|
void QTestLog::addSkip(const char *msg, const char *file, int line)
|
2011-04-27 10:05:43 +00:00
|
|
|
{
|
|
|
|
QTEST_ASSERT(msg);
|
|
|
|
QTEST_ASSERT(file);
|
|
|
|
|
2012-01-16 05:12:39 +00:00
|
|
|
++QTest::skips;
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::Skip, msg, file, line);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::addBenchmarkResult(const QBenchmarkResult &result)
|
|
|
|
{
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::addBenchmarkResult(result);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::startLogging()
|
|
|
|
{
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::startLogging();
|
2011-04-27 10:05:43 +00:00
|
|
|
QTest::oldMessageHandler = qInstallMsgHandler(QTest::messageHandler);
|
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::stopLogging()
|
|
|
|
{
|
|
|
|
qInstallMsgHandler(QTest::oldMessageHandler);
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTest::TestLoggers::stopLogging();
|
|
|
|
QTest::TestLoggers::destroyLoggers();
|
|
|
|
QTest::loggerUsingStdout = false;
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
void QTestLog::addLogger(LogMode mode, const char *filename)
|
2011-09-02 07:08:20 +00:00
|
|
|
{
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
if (filename && strcmp(filename, "-") == 0)
|
|
|
|
filename = 0;
|
|
|
|
if (!filename)
|
|
|
|
QTest::loggerUsingStdout = true;
|
2011-09-02 07:08:20 +00:00
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QAbstractTestLogger *logger = 0;
|
2011-09-02 07:08:20 +00:00
|
|
|
switch (mode) {
|
|
|
|
case QTestLog::Plain:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
logger = new QPlainTestLogger(filename);
|
2011-09-02 07:08:20 +00:00
|
|
|
break;
|
|
|
|
case QTestLog::XML:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
logger = new QXmlTestLogger(QXmlTestLogger::Complete, filename);
|
2011-09-02 07:08:20 +00:00
|
|
|
break;
|
|
|
|
case QTestLog::LightXML:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
logger = new QXmlTestLogger(QXmlTestLogger::Light, filename);
|
2011-09-02 07:08:20 +00:00
|
|
|
break;
|
|
|
|
case QTestLog::XunitXML:
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
logger = new QXunitTestLogger(filename);
|
2011-09-02 07:08:20 +00:00
|
|
|
break;
|
|
|
|
}
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTEST_ASSERT(logger);
|
|
|
|
QTest::TestLoggers::addLogger(logger);
|
2011-09-02 07:08:20 +00:00
|
|
|
}
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
int QTestLog::loggerCount()
|
2011-04-27 10:05:43 +00:00
|
|
|
{
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
return QTest::TestLoggers::loggerCount();
|
|
|
|
}
|
2011-04-27 10:05:43 +00:00
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
bool QTestLog::loggerUsingStdout()
|
|
|
|
{
|
|
|
|
return QTest::loggerUsingStdout;
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
2011-08-25 05:43:01 +00:00
|
|
|
void QTestLog::warn(const char *msg, const char *file, int line)
|
2011-04-27 10:05:43 +00:00
|
|
|
{
|
|
|
|
QTEST_ASSERT(msg);
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
if (QTest::TestLoggers::loggerCount() > 0)
|
2011-08-25 05:43:01 +00:00
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::Warn, msg, file, line);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
void QTestLog::info(const char *msg, const char *file, int line)
|
2011-04-27 10:05:43 +00:00
|
|
|
{
|
Allow tests to log to multiple destinations
Each destination and the format of output to write there is specified by
adding "-o filename,format" to the command-line. The special filename
"-" indicates that the log output is written to the standard output
stream, though standard output can be used as a destination at most
once.
The old-style testlib output options are still supported, but can only
be used to specify one logging destination, as before.
If no logging options are given on the command-line, a plain text log
will go to the console, as before.
To log to the console in plain text and to the file "test_output" in
xunit format, one would invoke a test in the following way:
tst_foo -o test_output,xunitxml -o -,txt
This commit also enhances the selftests to test with multiple loggers,
but negative tests (e.g. bad combinations of command-line options) are
left for future task QTBUG-21567.
Task-number: QTBUG-20615
Change-Id: If91e752bc7001657e15e427aba9d25ab0a29a0b0
Reviewed-on: http://codereview.qt-project.org/4125
Reviewed-by: Qt Sanity Bot <qt_sanity_bot@ovi.com>
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
2011-09-02 09:08:21 +00:00
|
|
|
QTEST_ASSERT(msg);
|
|
|
|
|
|
|
|
QTest::TestLoggers::addMessage(QAbstractTestLogger::Info, msg, file, line);
|
2011-04-27 10:05:43 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::setVerboseLevel(int level)
|
|
|
|
{
|
|
|
|
QTest::verbosity = level;
|
|
|
|
}
|
|
|
|
|
|
|
|
int QTestLog::verboseLevel()
|
|
|
|
{
|
|
|
|
return QTest::verbosity;
|
|
|
|
}
|
|
|
|
|
2012-01-13 02:55:37 +00:00
|
|
|
void QTestLog::ignoreMessage(QtMsgType type, const char *msg)
|
2011-04-27 10:05:43 +00:00
|
|
|
{
|
2011-08-24 08:20:44 +00:00
|
|
|
QTEST_ASSERT(msg);
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
QTest::IgnoreResultList *item = new QTest::IgnoreResultList(type, msg);
|
|
|
|
|
|
|
|
QTest::IgnoreResultList *list = QTest::ignoreResultList;
|
|
|
|
if (!list) {
|
|
|
|
QTest::ignoreResultList = item;
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
while (list->next)
|
|
|
|
list = list->next;
|
|
|
|
list->next = item;
|
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::setMaxWarnings(int m)
|
|
|
|
{
|
|
|
|
QTest::maxWarnings = m <= 0 ? INT_MAX : m + 2;
|
|
|
|
}
|
|
|
|
|
2011-11-01 11:19:39 +00:00
|
|
|
bool QTestLog::printAvailableTags = false;
|
|
|
|
|
|
|
|
void QTestLog::setPrintAvailableTagsMode()
|
|
|
|
{
|
|
|
|
printAvailableTags = true;
|
|
|
|
}
|
|
|
|
|
2012-01-16 05:12:39 +00:00
|
|
|
int QTestLog::passCount()
|
|
|
|
{
|
|
|
|
return QTest::passes;
|
|
|
|
}
|
|
|
|
|
|
|
|
int QTestLog::failCount()
|
|
|
|
{
|
|
|
|
return QTest::fails;
|
|
|
|
}
|
|
|
|
|
|
|
|
int QTestLog::skipCount()
|
|
|
|
{
|
|
|
|
return QTest::skips;
|
|
|
|
}
|
|
|
|
|
|
|
|
void QTestLog::resetCounters()
|
|
|
|
{
|
|
|
|
QTest::passes = 0;
|
|
|
|
QTest::fails = 0;
|
|
|
|
QTest::skips = 0;
|
|
|
|
}
|
|
|
|
|
2011-04-27 10:05:43 +00:00
|
|
|
QT_END_NAMESPACE
|