summaryrefslogtreecommitdiff
path: root/tests/validation
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2022-02-04 08:08:27 +0100
committerMariusz Felisiak <felisiak.mariusz@gmail.com>2022-02-07 20:37:05 +0100
commit7119f40c9881666b6f9b5cf7df09ee1d21cc8344 (patch)
treefa50869f5614295f462d9bf77fec59365c621609 /tests/validation
parent9c19aff7c7561e3a82978a272ecdaad40dda5c00 (diff)
Refs #33476 -- Refactored code to strictly match 88 characters line length.
Diffstat (limited to 'tests/validation')
-rw-r--r--tests/validation/test_error_messages.py28
1 files changed, 18 insertions, 10 deletions
diff --git a/tests/validation/test_error_messages.py b/tests/validation/test_error_messages.py
index 470c055eef..ffc660aad6 100644
--- a/tests/validation/test_error_messages.py
+++ b/tests/validation/test_error_messages.py
@@ -52,28 +52,32 @@ class ValidationMessagesTest(TestCase):
f,
"fõo",
[
- "“fõo” value has an invalid date format. It must be in YYYY-MM-DD format."
+ "“fõo” value has an invalid date format. It must be in YYYY-MM-DD "
+ "format."
],
)
self._test_validation_messages(
f,
"aaaa-10-10",
[
- "“aaaa-10-10” value has an invalid date format. It must be in YYYY-MM-DD format."
+ "“aaaa-10-10” value has an invalid date format. It must be in "
+ "YYYY-MM-DD format."
],
)
self._test_validation_messages(
f,
"2011-13-10",
[
- "“2011-13-10” value has the correct format (YYYY-MM-DD) but it is an invalid date."
+ "“2011-13-10” value has the correct format (YYYY-MM-DD) but it is an "
+ "invalid date."
],
)
self._test_validation_messages(
f,
"2011-10-32",
[
- "“2011-10-32” value has the correct format (YYYY-MM-DD) but it is an invalid date."
+ "“2011-10-32” value has the correct format (YYYY-MM-DD) but it is an "
+ "invalid date."
],
)
@@ -84,7 +88,8 @@ class ValidationMessagesTest(TestCase):
f,
"fõo",
[
- "“fõo” value has an invalid format. It must be in YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ] format."
+ "“fõo” value has an invalid format. It must be in "
+ "YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ] format."
],
)
# Correct format but invalid date
@@ -92,7 +97,8 @@ class ValidationMessagesTest(TestCase):
f,
"2011-10-32",
[
- "“2011-10-32” value has the correct format (YYYY-MM-DD) but it is an invalid date."
+ "“2011-10-32” value has the correct format (YYYY-MM-DD) but it is an "
+ "invalid date."
],
)
# Correct format but invalid date/time
@@ -100,8 +106,8 @@ class ValidationMessagesTest(TestCase):
f,
"2011-10-32 10:10",
[
- "“2011-10-32 10:10” value has the correct format (YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ]) "
- "but it is an invalid date/time."
+ "“2011-10-32 10:10” value has the correct format "
+ "(YYYY-MM-DD HH:MM[:ss[.uuuuuu]][TZ]) but it is an invalid date/time."
],
)
@@ -112,7 +118,8 @@ class ValidationMessagesTest(TestCase):
f,
"fõo",
[
- "“fõo” value has an invalid format. It must be in HH:MM[:ss[.uuuuuu]] format."
+ "“fõo” value has an invalid format. It must be in HH:MM[:ss[.uuuuuu]] "
+ "format."
],
)
# Correct format but invalid time
@@ -120,6 +127,7 @@ class ValidationMessagesTest(TestCase):
f,
"25:50",
[
- "“25:50” value has the correct format (HH:MM[:ss[.uuuuuu]]) but it is an invalid time."
+ "“25:50” value has the correct format (HH:MM[:ss[.uuuuuu]]) but it is "
+ "an invalid time."
],
)