2007-01-22 21:25:56 -05:00
|
|
|
<testcase>
|
2014-04-03 05:06:24 -04:00
|
|
|
<info>
|
|
|
|
<keywords>
|
|
|
|
getdate
|
|
|
|
unittest
|
|
|
|
</keywords>
|
|
|
|
</info>
|
2004-11-15 16:49:35 -05:00
|
|
|
#
|
|
|
|
# Server-side
|
|
|
|
<reply>
|
|
|
|
</reply>
|
|
|
|
|
|
|
|
# Client-side
|
|
|
|
<client>
|
|
|
|
<server>
|
|
|
|
none
|
|
|
|
</server>
|
|
|
|
# tool is what to use instead of 'curl'
|
|
|
|
<tool>
|
|
|
|
lib517
|
|
|
|
</tool>
|
|
|
|
|
|
|
|
<name>
|
|
|
|
curl_getdate() testing
|
|
|
|
</name>
|
|
|
|
<command>
|
|
|
|
nothing
|
|
|
|
</command>
|
|
|
|
</client>
|
|
|
|
|
|
|
|
#
|
|
|
|
# Verify data after the test has been "shot"
|
|
|
|
<verify>
|
2014-01-31 18:58:58 -05:00
|
|
|
<stdout>
|
2004-11-15 16:49:35 -05:00
|
|
|
</stdout>
|
2005-03-09 02:56:32 -05:00
|
|
|
|
2012-11-14 06:53:47 -05:00
|
|
|
# This test case previously tested an overflow case ("2094 Nov 6 =>
|
2005-03-09 02:56:32 -05:00
|
|
|
# 2147483647") for 32bit time_t, but since some systems have 64bit time_t and
|
|
|
|
# handles this (returning 3939840000), and some 64bit-time_t systems don't
|
2012-11-14 06:53:47 -05:00
|
|
|
# handle this and return -1 for this, it turned very tricky to write a fine
|
2005-03-09 02:56:32 -05:00
|
|
|
# test case and thus it is now removed until we have a way to write test cases
|
|
|
|
# for this kind of things.
|
|
|
|
|
2004-11-15 16:49:35 -05:00
|
|
|
</verify>
|
2007-01-22 21:25:56 -05:00
|
|
|
</testcase>
|