Details
-
Type:
Bug
-
Status: Open
-
Priority:
P3: Somewhat important
-
Resolution: Unresolved
-
Affects Version/s: Some future release
-
Fix Version/s: None
-
Component/s: Testing: qtestlib
-
Labels:None
Description
If the message contains UTF-8 characters (such as the degree symbol of QTBUG-80527) then qtestlib should be able to receive the whole QString, in order to decode it depending on the output. For example:
- console output in the local locale, maybe ISO-8859-1
- XML output in UTF-8
Currently the message string is just a const char * and nobody knows what is its real encoding. I'm talking about macros QVERIFY2(), QSKIP() etc and functions QTestResult::verify() etc.
Edward Welbourne Tor Arne Vestbø like we discussed today.
Attachments
Issue Links
- relates to
-
QTBUG-101180 As a user of QTestLib, I'm concerned about the runtime effects of the unconditional message formatting in QVERIFY2
-
- Open
-
- resulted from
-
QTBUG-80527 qt/qtlocation autotests fail occasionally on MacOS 10.13
-
- Closed
-