diff options
| author | Thiago Macieira <thiago.macieira@intel.com> | 2012-05-02 14:49:31 +0200 |
|---|---|---|
| committer | Qt by Nokia <qt-info@nokia.com> | 2012-06-09 10:45:01 +0200 |
| commit | fbabbe63c5dcf688f38a7c9bf1bae63b19086935 (patch) | |
| tree | d67ceadb22ec11b03b9d84ea1bd203fef831b2d5 /src/testlib/qxunittestlogger.cpp | |
| parent | 693468a54da02ff64b104bae8d3b419253889233 (diff) | |
Use UTF-8 in the QtTest data and benchmark tags
Future-proofing. Since Qt source code is now mandated to be in UTF-8,
it is entirely possible that someone will use non-ASCII in data tags.
Though it would be interesting to see how to access them from the
Windows command-line.
Change-Id: I880fc312432b62143888ff1e1d9abbd54f704601
Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com>
Diffstat (limited to 'src/testlib/qxunittestlogger.cpp')
| -rw-r--r-- | src/testlib/qxunittestlogger.cpp | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/testlib/qxunittestlogger.cpp b/src/testlib/qxunittestlogger.cpp index 5967ccdd4e..4eeb7a0e19 100644 --- a/src/testlib/qxunittestlogger.cpp +++ b/src/testlib/qxunittestlogger.cpp @@ -231,7 +231,7 @@ void QXunitTestLogger::addBenchmarkResult(const QBenchmarkResult &result) benchmarkElement->addAttribute( QTest::AI_Metric, QTest::benchmarkMetricName(QBenchmarkTestMethodData::current->result.metric)); - benchmarkElement->addAttribute(QTest::AI_Tag, result.context.tag.toAscii().data()); + benchmarkElement->addAttribute(QTest::AI_Tag, result.context.tag.toUtf8().data()); benchmarkElement->addAttribute(QTest::AI_Value, QByteArray::number(result.value).constData()); char buf[100]; |