aboutsummaryrefslogtreecommitdiff
path: root/tests/date.test
diff options
context:
space:
mode:
authorElliott Hughes <enh@google.com>2015-08-08 13:39:01 -0500
committerRob Landley <rob@landley.net>2015-08-08 13:39:01 -0500
commit400dacdeb69bc13868a625fc2ce8b49b6acd5ae3 (patch)
tree4bb640b14bf3d65d67c20bb3e26587dc6325b42b /tests/date.test
parent1203ddf0e1110a107cbabf4855e07055fabe1e42 (diff)
downloadtoybox-400dacdeb69bc13868a625fc2ce8b49b6acd5ae3.tar.gz
Reject invalid dates in date(1).
Humans get upset when date(1) lets mktime(3) work out what the 99th day of the 99th month would be rather than rejecting the invalid date. For the subtly wrong cases, rather than get into the leap year business, let's rely on localtime_r(3).
Diffstat (limited to 'tests/date.test')
-rw-r--r--tests/date.test10
1 files changed, 10 insertions, 0 deletions
diff --git a/tests/date.test b/tests/date.test
new file mode 100644
index 00000000..d72e50cf
--- /dev/null
+++ b/tests/date.test
@@ -0,0 +1,10 @@
+#!/bin/bash
+
+[ -f testing.sh ] && . testing.sh
+
+#testing "name" "command" "result" "infile" "stdin"
+
+# Accidentally given a Unix time, we should trivially reject that.
+testing "date Unix time" "date 1438053157 2>&1" "date: bad date '1438053157'\n" "" ""
+# But some invalid dates are more subtle, like Febuary 29th in a non-leap year.
+testing "date Feb 29th" "date 022900001975 2>&1" "date: bad date