| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
xunitxml testlog.
`error' in xunit causes many xunit processing tools to consider the test
as failing. This is different semantics from native testlib XML, where
a qDebug is considered a message and not a failure.
Change it to put qDebugs under the "system-err" tag when using xunitxml
to retain semantic compatibility with testlib XML.
Autotest: tst_selftests
|
| |
|
|
|
|
|
|
|
|
|
| |
A few tests use printf, which means they interfere with the XML test
logging. Blacklist them for the XML test.
Note that these tests happened to pass under the old test logger
implementation. That was because the test logger always printed XML
tags on a single line, and the printf calls contained no special XML
characters. The test logs generated were technically valid XML but
contained extraneous text.
|
| |
|
|
|
| |
Previously `-flush' was always passed to the child process, meaning the
old (Qt 4.5) test logger was used exclusively in this test, hiding bugs.
|
| | |
|
| |\
| |
| |
| |
| | |
Conflicts:
tests/auto/selftests/tst_selftests.cpp
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The testlib subtests are conceptually not standalone unit tests, rather
they are helper programs for the real unit test, tst_selftests.
So, as is done for other similar tests (e.g. qprocess), don't name them
with `tst_'.
This makes it easier for automated tools to figure out that they
shouldn't directly run these tests.
Reviewed-by: Shane Bradley
|
| | |
| |
| |
| | |
perforce.
|
| | |
|
| |
|
