fz0x1/jrnl
1
0
Fork 0
mirror of https://github.com/jrnl-org/jrnl.git synced 2025-06-28 21:46:13 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

[GH-614] resolving issues around unreadable dates and unparsed dates

Browse source
This commit is contained in:
Micah Jerome Ellison 2019-07-20 14:42:21 -07:00
parent d3921d9e47
commit f3b9a91c9b
9 changed files with 88 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

19
features/regression.feature
View file

@ -53,3 +53,22 @@ Feature: Zapped bugs should stay dead.
2013-06-10 15:40 He said "[this] is the best time to be alive".
"""
Scenario: Integers in square brackets should not be read as dates
Given we use the config "brackets.yaml"
When we run "jrnl -1"
Then the output should contain "[1] line starting with 1"
Scenario: Journals with unreadable dates should still be viewable
Given we use the config "unreadabledates.yaml"
When we run "jrnl -2"
Then the output should contain "I've lost track of time."
Then the output should contain "Time has no meaning."
Scenario: Journals with readable dates AND unreadable dates should still contain all data.
Given we use the config "mostlyreadabledates.yaml"
When we run "jrnl -3"
Then the output should contain "Time machines are possible."
When we run "jrnl -1"
Then the output should contain "I'm going to activate the machine."
Then the output should contain "I've crossed so many timelines. Is there any going back?"