Doc: Fix references to Qt Test

QtTestLib and QTestLib don't exist. The proper name is "QtTest" (code)
or "Qt Test" (English)

http://qt-project.org/wiki/Spelling_Module_Names_in_Qt_Documentation
http://lists.qt-project.org/pipermail/interest/2012-December/005221.html

Files paths in qttestlib.qdocconf can't be changed easily however, as it
breaks things. So, they're left as they are.

Change-Id: Ifbc44ea858c453bedad8cd7723f847e67fc7a85a
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
Reviewed-by: Jerome Pasion <jerome.pasion@digia.com>

3 files changed, 6 insertions, 6 deletions

diff --git a/tests/README b/tests/README
index f94d5a2f13..5a8f2a21cd 100644
--- a/tests/README
+++ b/tests/README
@@ -1,4 +1,4 @@
-This directory contains autotests and benchmarks based on QTestlib. In order
+This directory contains autotests and benchmarks based on Qt Test. In order
 to run the autotests reliably, you need to configure a desktop to match the
 test environment that these tests are written for.
 
diff --git a/tests/auto/corelib/xml/qxmlstream/tst_qxmlstream.cpp b/tests/auto/corelib/xml/qxmlstream/tst_qxmlstream.cpp
index 73f89115af..d2e090bf53 100644
--- a/tests/auto/corelib/xml/qxmlstream/tst_qxmlstream.cpp
+++ b/tests/auto/corelib/xml/qxmlstream/tst_qxmlstream.cpp
@@ -224,7 +224,7 @@ static QString documentElement(const QByteArray &document)
  * Since this suite is fairly large, it runs the tests sequentially in order to not
  * have them all loaded into memory at once. In this way, the maximum memory usage stays
  * low, which means one can run valgrind on this test. However, the drawback is that
- * QTestLib's usual error reporting and testing mechanisms are slightly bypassed.
+ * Qt Test's usual error reporting and testing mechanisms are slightly bypassed.
  *
  * Part of this code is a manual, ad-hoc implementation of xml:base.
  *
@@ -611,11 +611,11 @@ void tst_QXmlStream::reportFailures_data()
     QTest::addColumn<QString>("description");
 
     /* We loop over all our failures(if any!), and output them such
-     * that they appear in the QTestLib log. */
+     * that they appear in the Qt Test log. */
     for(int i = 0; i < len; ++i)
         QTest::newRow(m_handler.failures.at(i).first.toLatin1().constData()) << true << m_handler.failures.at(i).second;
 
-    /* We need to add at least one column of test data, otherwise QTestLib complains. */
+    /* We need to add at least one column of test data, otherwise Qt Test complains. */
     if(len == 0)
         QTest::newRow("Whole test suite passed") << false << QString();
 
@@ -1140,7 +1140,7 @@ void tst_QXmlStream::crashInUTF16Codec() const
 }
 
 /*
-  In addition to QTestLib's flags, one can specify "-c <filename>" and have that file output in its canonical form.
+  In addition to Qt Test's flags, one can specify "-c <filename>" and have that file output in its canonical form.
 */
 int main(int argc, char *argv[])
 {
diff --git a/tests/auto/widgets/widgets/qdatetimeedit/tst_qdatetimeedit.cpp b/tests/auto/widgets/widgets/qdatetimeedit/tst_qdatetimeedit.cpp
index ca2f8e7afc..9ecb0650c5 100644
--- a/tests/auto/widgets/widgets/qdatetimeedit/tst_qdatetimeedit.cpp
+++ b/tests/auto/widgets/widgets/qdatetimeedit/tst_qdatetimeedit.cpp
@@ -3218,7 +3218,7 @@ void tst_QDateTimeEdit::cachedDayTest()
     testWidget->setDate(QDate(2007, 1, 30));
     testWidget->setCurrentSection(QDateTimeEdit::DaySection);
     //QTest::keyClick(testWidget->lineEdit(), Qt::Key_Up); // this doesn't work
-    //on Mac. QTestLib bug? ###
+    //on Mac. Qt Test bug? ###
     QTest::keyClick(testWidget, Qt::Key_Up);
     testWidget->setCurrentSection(QDateTimeEdit::MonthSection);
     QTest::keyClick(testWidget, Qt::Key_Up);