qt5base-lts/tests/auto/corelib/time/qtime
Edward Welbourne 52affd322c Be consistent in the RFC2822Date invalid character tests
The ones we reject used a zero offset while the one that does parse
(though it shouldn't - revised comment) has a one hour offset. Made
them all use that offset and added a partner test that has no invalid
characters, so ensure the success of the invalid character tests isn't
due to falsely rejecting the valid date/time text to which the invalid
characters are added.

Task-number: QTBUG-80038
Change-Id: I6e3dd79b981af6803e60877229c56599cfd719cb
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
2019-11-27 18:27:43 +01:00
..
.gitignore Separate out the time, zone, date code from corelib/tools/ 2019-06-06 15:54:32 +02:00
qtime.pro Separate out the time, zone, date code from corelib/tools/ 2019-06-06 15:54:32 +02:00
tst_qtime.cpp Be consistent in the RFC2822Date invalid character tests 2019-11-27 18:27:43 +01:00