QXcodeTestLogger Class Reference

#include <qxctestlogger_p.h>

Inheritance diagram for QXcodeTestLogger:

Collaboration diagram for QXcodeTestLogger:

Public Member Functions
	QXcodeTestLogger ()
	~QXcodeTestLogger () override
void	startLogging () override
	Called before the start of a test run.
void	stopLogging () override
	Called after the end of a test run.
void	enterTestFunction (const char *function) override
	This virtual method is called before each test function is invoked.
void	leaveTestFunction () override
	This virtual method is called after a test function has completed, to match \l enterTestFunction().
void	addIncident (IncidentTypes type, const char *description, const char *file=nullptr, int line=0) override
	This virtual method is called when an event occurs that relates to the resolution of the test.
void	addMessage (MessageTypes type, const QString &message, const char *file=nullptr, int line=0) override
	This is an overloaded member function, provided for convenience. It differs from the above function only in what argument(s) it accepts.
void	addBenchmarkResult (const QBenchmarkResult &result) override
	This virtual method is called after a benchmark has been run enough times to produce usable data.
Public Member Functions inherited from QAbstractTestLogger
	QAbstractTestLogger (const char *filename)
	Constructs the base-class parts of the logger.
virtual	~QAbstractTestLogger ()
	Destroys the logger object.
virtual void	enterTestData (QTestData *)
	This virtual method is called before and after each call to a test function.
virtual void	addBenchmarkResults (const QList< QBenchmarkResult > &result)
virtual void	addMessage (QtMsgType, const QMessageLogContext &, const QString &)
	This is an overloaded member function, provided for convenience. It differs from the above function only in what argument(s) it accepts.This virtual method is called from the custom message handler QtTest installs in place of Qt's default message handler for the duration of testing, unless QTest::ignoreMessage() was used to ignore it, or too many messages have previously been processed.
virtual bool	isRepeatSupported () const
	Returns true if the logger supports repeated test runs.
bool	isLoggingToStdout () const
	Returns true if the output stream is standard output.
void	outputString (const char *msg)
	Convenience method to write msg to the output stream.

Static Public Member Functions
static bool	canLogTestProgress ()
static int	parseCommandLineArgument (const char *argument)
static bool	isActive ()

Additional Inherited Members
Public Types inherited from QAbstractTestLogger
enum	IncidentTypes {   Skip , Pass , XFail , Fail ,   XPass , BlacklistedPass , BlacklistedFail , BlacklistedXPass ,   BlacklistedXFail }
	\value Pass The test ran to completion successfully. More...
enum	MessageTypes {   QDebug , QInfo , QWarning , QCritical ,   QFatal , Info , Warn }
	The members whose names begin with Q describe messages that originate in calls, by the test or code under test, to Qt logging functions (implemented as macros) whose names are similar, with a q in place of the leading Q. More...
Protected Member Functions inherited from QAbstractTestLogger
void	filterUnprintable (char *str) const
	Helper utility to blot out unprintable characters in str.
Protected Attributes inherited from QAbstractTestLogger
FILE *	stream

Detailed Description

Definition at line 28 of file qxctestlogger_p.h.

Constructor & Destructor Documentation

QXcodeTestLogger()

QXcodeTestLogger::QXcodeTestLogger

(

)

~QXcodeTestLogger()

QXcodeTestLogger::~QXcodeTestLogger ( )

override

Member Function Documentation

addBenchmarkResult()

void QXcodeTestLogger::addBenchmarkResult ( const QBenchmarkResult & result )

overridevirtual

This virtual method is called after a benchmark has been run enough times to produce usable data.

It is passed the median result from all cycles of the code controlled by the test's QBENCHMARK loop.

Every logging implementation must implement this method.

See also

addIncident(), addMessage()

Implements QAbstractTestLogger.

addIncident()

void QXcodeTestLogger::addIncident ( IncidentTypes type, const char * description, const char * file = nullptr, int line = 0 )

overridevirtual

This virtual method is called when an event occurs that relates to the resolution of the test.

The type indicates whether this was a pass, a fail or a skip, whether a failure was expected, and whether the test being run is blacklisted. The description may be empty (for a pass) or a message describing the nature of the incident. Where the location in code of the incident is known, it is indicated by file and line; otherwise, these are nullptr and 0, respectively.

Every logging implementation must implement this method. Note that there are circumstances where more than one incident may be reported, in this way, for a single run of a test on a single dataset. It is the implementation's responsibility to recognize such cases and decide what to do about them. For purposes of counting resolutions of tests in the "Totals" report at the end of a test run, QtTest considers the first incident (excluding XFail and its blacklisted variant) decisive.

See also

addMessage(), addBenchmarkResult()

Implements QAbstractTestLogger.

addMessage()

void QXcodeTestLogger::addMessage ( MessageTypes type, const QString & message, const char * file = nullptr, int line = 0 )

overridevirtual

This is an overloaded member function, provided for convenience. It differs from the above function only in what argument(s) it accepts.

This virtual method is called, via its QtMsgType overload, from the custom message handler QtTest installs. It is also used to warn about various situations detected by QtTest itself, such as failure to see a message anticipated by QTest::ignoreMessage() and, particularly when verbosity options have been enabled via the command-line, to log some extra information.

Every logging implementation must implement this method. The type indicates the category of message and the message is the content to be reported. When the message is associated with specific code, the name of the file and line number within it are also supplied; otherwise, these are \nullptr and 0, respectively.

See also

QTest::ignoreMessage(), addIncident()

Implements QAbstractTestLogger.

canLogTestProgress()

bool QXcodeTestLogger::canLogTestProgress ( )

static

Definition at line 265 of file qxctestlogger.mm.

Referenced by QTest::qtest_qParseArgs().

Here is the caller graph for this function:

enterTestFunction()

void QXcodeTestLogger::enterTestFunction ( const char * function )

overridevirtual

This virtual method is called before each test function is invoked.

It is passed the name of the test function (without its class prefix) as function. It is likewise called for {initTestCase()} at the start of testing, after \l startLogging(), and for {cleanupTestCase()} at the end of testing, in each case passing the name of the function. It is also called with \nullptr as function after the last of these functions, or in the event of an early end to testing, before \l stopLogging().

For data-driven test functions, this is called only once, before the data function is called to set up the table of datasets and the test is run with its first dataset.

Every logging implementation must implement this method. It shall typically need to record the name of the function for later use in log messages.

See also

leaveTestFunction(), enterTestData()

Implements QAbstractTestLogger.

isActive()

static bool QXcodeTestLogger::isActive ( )

static

leaveTestFunction()

void QXcodeTestLogger::leaveTestFunction ( )

overridevirtual

This virtual method is called after a test function has completed, to match \l enterTestFunction().

For data-driven test functions, this is called only once, after the test is run with its last dataset.

Every logging implementation must implement this method. In some cases it may be called more than once without an intervening call to \l enterTestFunction(). In such cases, the implementation should ignore these later calls, until the next call to enterTestFunction().

See also

enterTestFunction(), enterTestData()

Implements QAbstractTestLogger.

parseCommandLineArgument()

int QXcodeTestLogger::parseCommandLineArgument ( const char * argument )

static

Definition at line 270 of file qxctestlogger.mm.

References argument.

Referenced by QTest::qtest_qParseArgs().

Here is the caller graph for this function:

startLogging()

void QXcodeTestLogger::startLogging ( )

overridevirtual

Called before the start of a test run.

This virtual method is called before the first tests are run. A logging implementation might open a file, write some preamble, or prepare in other ways, such as setting up initial values of variables. It can use the usual Qt logging infrastucture, since it is also called before QtTest installs its own custom message handler.

See also

stopLogging()

Reimplemented from QAbstractTestLogger.

stopLogging()

void QXcodeTestLogger::stopLogging ( )

overridevirtual

Called after the end of a test run.

This virtual method is called after all tests have run. A logging implementation might collate information gathered from the run, write a summary, or close a file. It can use the usual Qt logging infrastucture, since it is also called after QtTest has restored the default message handler it replaced with its own custom message handler.

See also

startLogging()

Reimplemented from QAbstractTestLogger.

---

The documentation for this class was generated from the following files:

• qtbase/src/testlib/qxctestlogger_p.h (05fc3aef53348fb58be6308076e000825b704e58)
• qtbase/src/testlib/qxctestlogger.mm (05fc3aef53348fb58be6308076e000825b704e58)