mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-20 21:18:32 +02:00
move tests to be more behavior driven
This commit is contained in:
Jonathan Wren
parent
e3f3904cf7
commit
80bc2ae4ae
12 changed files with 228 additions and 236 deletions
|
|
@ -84,4 +84,25 @@ Feature: Reading and writing to journal with custom date formats
|
||||||
Then the output should contain "I'm going to activate the machine."
|
Then the output should contain "I'm going to activate the machine."
|
||||||
And the output should contain "I've crossed so many timelines. Is there any going back?"
|
And the output should contain "I've crossed so many timelines. Is there any going back?"
|
||||||
|
|
||||||
|
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"
|
||||||
|
|
||||||
|
# broken still
|
||||||
|
@skip
|
||||||
|
Scenario: Dayone entries without timezone information are interpreted in current timezone
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl -until 'feb 2013'"
|
||||||
|
Then we should get no error
|
||||||
|
And the output should contain "2013-01-17T18:37Z" in the local time
|
||||||
|
|
||||||
|
Scenario: Loading entry with ambiguous time stamp
|
||||||
|
#https://github.com/jrnl-org/jrnl/issues/153
|
||||||
|
Given we use the config "bug153.yaml"
|
||||||
|
When we run "jrnl -1"
|
||||||
|
Then we should get no error
|
||||||
|
And the output should be
|
||||||
|
"""
|
||||||
|
2013-10-27 03:27 Some text.
|
||||||
|
"""
|
||||||
|
|
|
||||||
35
features/file_storage.feature
Normal file
35
features/file_storage.feature
Normal file
|
|
@ -0,0 +1,35 @@
|
||||||
|
Feature: Journals iteracting with the file system in a way that users can see
|
||||||
|
|
||||||
|
Scenario: Adding entries to a Folder journal should generate date files
|
||||||
|
Given we use the config "empty_folder.yaml"
|
||||||
|
When we run "jrnl 23 July 2013: Testing folder journal."
|
||||||
|
Then we should see the message "Entry added"
|
||||||
|
When the journal directory is listed
|
||||||
|
Then the output should contain "2013/07/23.txt" or "2013\07\23.txt"
|
||||||
|
|
||||||
|
Scenario: Adding multiple entries to a Folder journal should generate multiple date files
|
||||||
|
Given we use the config "empty_folder.yaml"
|
||||||
|
When we run "jrnl 23 July 2013: Testing folder journal."
|
||||||
|
And we run "jrnl 3/7/2014: Second entry of journal."
|
||||||
|
Then we should see the message "Entry added"
|
||||||
|
When the journal directory is listed
|
||||||
|
Then the output should contain "2013/07/23.txt" or "2013\07\23.txt"
|
||||||
|
Then the output should contain "2014/03/07.txt" or "2014\03\07.txt"
|
||||||
|
|
||||||
|
Scenario: If the journal and it's parent directory don't exist, they should be created
|
||||||
|
Given we use the config "missing_directory.yaml"
|
||||||
|
Then the journal should not exist
|
||||||
|
When we run "jrnl This is a new entry in my journal"
|
||||||
|
Then the journal should exist
|
||||||
|
When we run "jrnl -n 1"
|
||||||
|
Then the output should contain "This is a new entry in my journal"
|
||||||
|
And the journal should have 1 entry
|
||||||
|
|
||||||
|
Scenario: If the journal file doesn't exist, then it should be created
|
||||||
|
Given we use the config "missing_journal.yaml"
|
||||||
|
Then the journal should not exist
|
||||||
|
When we run "jrnl This is a new entry in my journal"
|
||||||
|
Then the journal should exist
|
||||||
|
When we run "jrnl -n 1"
|
||||||
|
Then the output should contain "This is a new entry in my journal"
|
||||||
|
And the journal should have 1 entry
|
||||||
|
|
@ -192,3 +192,29 @@ Feature: Custom formats
|
||||||
tags:
|
tags:
|
||||||
|
|
||||||
"""
|
"""
|
||||||
|
|
||||||
|
Scenario: Printing a journal that has multiline entries
|
||||||
|
Given we use the config "multiline.yaml"
|
||||||
|
When we run "jrnl -n 1"
|
||||||
|
Then we should get no error
|
||||||
|
And the output should be
|
||||||
|
"""
|
||||||
|
2013-06-09 15:39 Multiple line entry.
|
||||||
|
| This is the first line.
|
||||||
|
| This line doesn't have any ending punctuation
|
||||||
|
|
|
||||||
|
| There is a blank line above this.
|
||||||
|
"""
|
||||||
|
|
||||||
|
Scenario: Exporting dayone to json
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl --export json"
|
||||||
|
Then we should get no error
|
||||||
|
And the output should be parsable as json
|
||||||
|
And the json output should contain entries.0.uuid = "4BB1F46946AD439996C9B59DE7C4DDC1"
|
||||||
|
|
||||||
|
Scenario: Empty DayOne entry bodies should not error
|
||||||
|
# https://github.com/jrnl-org/jrnl/issues/780
|
||||||
|
Given we use the config "bug780.yaml"
|
||||||
|
When we run "jrnl --short"
|
||||||
|
Then we should get no error
|
||||||
|
|
|
||||||
34
features/journaltype.feature
Normal file
34
features/journaltype.feature
Normal file
|
|
@ -0,0 +1,34 @@
|
||||||
|
Feature: Tests that don't fit anywhere else
|
||||||
|
|
||||||
|
Scenario: Opening an folder that's not a DayOne folder should treat as folder journal
|
||||||
|
Given we use the config "empty_folder.yaml"
|
||||||
|
When we run "jrnl 23 july 2013: Testing folder journal."
|
||||||
|
Then we should see the message "Entry added"
|
||||||
|
When we run "jrnl -1"
|
||||||
|
Then the output should be "2013-07-23 09:00 Testing folder journal."
|
||||||
|
|
||||||
|
Scenario: Loading a sample journal
|
||||||
|
Given we use the config "basic.yaml"
|
||||||
|
When we run "jrnl -2"
|
||||||
|
Then we should get no error
|
||||||
|
And the output should be
|
||||||
|
"""
|
||||||
|
2013-06-09 15:39 My first entry.
|
||||||
|
| Everything is alright
|
||||||
|
|
||||||
|
2013-06-10 15:40 Life is good.
|
||||||
|
| But I'm better.
|
||||||
|
"""
|
||||||
|
|
||||||
|
Scenario: Loading a DayOne Journal
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl -from 'feb 2013'"
|
||||||
|
Then we should get no error
|
||||||
|
And the output should be
|
||||||
|
"""
|
||||||
|
2013-05-17 11:39 This entry has tags!
|
||||||
|
|
||||||
|
2013-06-17 20:38 This entry has a location.
|
||||||
|
|
||||||
|
2013-07-17 11:38 This entry is starred!
|
||||||
|
"""
|
||||||
|
|
@ -1,109 +0,0 @@
|
||||||
Feature: Dayone specific implementation details.
|
|
||||||
|
|
||||||
Scenario: Loading a DayOne Journal
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl -from 'feb 2013'"
|
|
||||||
Then we should get no error
|
|
||||||
And the output should be
|
|
||||||
"""
|
|
||||||
2013-05-17 11:39 This entry has tags!
|
|
||||||
|
|
||||||
2013-06-17 20:38 This entry has a location.
|
|
||||||
|
|
||||||
2013-07-17 11:38 This entry is starred!
|
|
||||||
"""
|
|
||||||
|
|
||||||
# broken still
|
|
||||||
@skip
|
|
||||||
Scenario: Entries without timezone information will be interpreted as in the current timezone
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl -until 'feb 2013'"
|
|
||||||
Then we should get no error
|
|
||||||
And the output should contain "2013-01-17T18:37Z" in the local time
|
|
||||||
|
|
||||||
Scenario: Writing into Dayone
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl 01 may 1979: Being born hurts."
|
|
||||||
And we run "jrnl -until 1980"
|
|
||||||
Then the output should be "1979-05-01 09:00 Being born hurts."
|
|
||||||
|
|
||||||
Scenario: Loading tags from a DayOne Journal
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl --tags"
|
|
||||||
Then the output should be
|
|
||||||
"""
|
|
||||||
@work : 1
|
|
||||||
@play : 1
|
|
||||||
"""
|
|
||||||
|
|
||||||
Scenario: Saving tags from a DayOne Journal
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl A hard day at @work"
|
|
||||||
And we run "jrnl --tags"
|
|
||||||
Then the output should be
|
|
||||||
"""
|
|
||||||
@work : 2
|
|
||||||
@play : 1
|
|
||||||
"""
|
|
||||||
|
|
||||||
Scenario: Filtering by tags from a DayOne Journal
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl @work"
|
|
||||||
Then the output should be "2013-05-17 11:39 This entry has tags!"
|
|
||||||
|
|
||||||
Scenario: Exporting dayone to json
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl --export json"
|
|
||||||
Then we should get no error
|
|
||||||
And the output should be parsable as json
|
|
||||||
And the json output should contain entries.0.uuid = "4BB1F46946AD439996C9B59DE7C4DDC1"
|
|
||||||
|
|
||||||
Scenario: Writing into Dayone adds extended metadata
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl 01 may 1979: Being born hurts."
|
|
||||||
And we run "jrnl --export json"
|
|
||||||
Then "entries" in the json output should have 5 elements
|
|
||||||
And the json output should contain entries.0.creator.software_agent
|
|
||||||
And the json output should contain entries.0.creator.os_agent
|
|
||||||
And the json output should contain entries.0.creator.host_name
|
|
||||||
And the json output should contain entries.0.creator.generation_date
|
|
||||||
And the json output should contain entries.0.creator.device_agent
|
|
||||||
And "entries.0.creator.software_agent" in the json output should contain "jrnl"
|
|
||||||
|
|
||||||
# fails when system time is UTC (as on Travis-CI)
|
|
||||||
@skip
|
|
||||||
Scenario: DayOne tag searching should work with tags containing a mixture of upper and lower case.
|
|
||||||
# https://github.com/jrnl-org/jrnl/issues/354
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl @plAy"
|
|
||||||
Then the output should contain "2013-05-17 11:39 This entry has tags!"
|
|
||||||
|
|
||||||
# fails when system time is UTC (as on Travis-CI)
|
|
||||||
@skip
|
|
||||||
Scenario: Title with an embedded period on DayOne journal
|
|
||||||
Given we use the config "dayone.yaml"
|
|
||||||
When we run "jrnl 04-24-2014: "Ran 6.2 miles today in 1:02:03. I'm feeling sore because I forgot to stretch.""
|
|
||||||
Then we should see the message "Entry added"
|
|
||||||
When we run "jrnl -1"
|
|
||||||
Then the output should be
|
|
||||||
"""
|
|
||||||
2014-04-24 09:00 Ran 6.2 miles today in 1:02:03.
|
|
||||||
| I'm feeling sore because I forgot to stretch.
|
|
||||||
"""
|
|
||||||
|
|
||||||
Scenario: Loading entry with ambiguous time stamp
|
|
||||||
#https://github.com/jrnl-org/jrnl/issues/153
|
|
||||||
Given we use the config "bug153.yaml"
|
|
||||||
When we run "jrnl -1"
|
|
||||||
Then we should get no error
|
|
||||||
And the output should be
|
|
||||||
"""
|
|
||||||
2013-10-27 03:27 Some text.
|
|
||||||
"""
|
|
||||||
|
|
||||||
Scenario: Empty DayOne entry bodies should not error
|
|
||||||
# https://github.com/jrnl-org/jrnl/issues/780
|
|
||||||
Given we use the config "bug780.yaml"
|
|
||||||
When we run "jrnl --short"
|
|
||||||
Then we should get no error
|
|
||||||
|
|
||||||
|
|
@ -1,51 +0,0 @@
|
||||||
Feature: Loading the default journal type
|
|
||||||
|
|
||||||
Scenario: Loading a sample journal
|
|
||||||
Given we use the config "basic.yaml"
|
|
||||||
When we run "jrnl -2"
|
|
||||||
Then we should get no error
|
|
||||||
And the output should be
|
|
||||||
"""
|
|
||||||
2013-06-09 15:39 My first entry.
|
|
||||||
| Everything is alright
|
|
||||||
|
|
||||||
2013-06-10 15:40 Life is good.
|
|
||||||
| But I'm better.
|
|
||||||
"""
|
|
||||||
|
|
||||||
Scenario: Printing a journal that has multiline entries
|
|
||||||
Given we use the config "multiline.yaml"
|
|
||||||
When we run "jrnl -n 1"
|
|
||||||
Then we should get no error
|
|
||||||
And the output should be
|
|
||||||
"""
|
|
||||||
2013-06-09 15:39 Multiple line entry.
|
|
||||||
| This is the first line.
|
|
||||||
| This line doesn't have any ending punctuation
|
|
||||||
|
|
|
||||||
| There is a blank line above this.
|
|
||||||
"""
|
|
||||||
|
|
||||||
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: If the journal and it's parent directory don't exist, they should be created
|
|
||||||
Given we use the config "missing_directory.yaml"
|
|
||||||
Then the journal should not exist
|
|
||||||
When we run "jrnl This is a new entry in my journal"
|
|
||||||
Then the journal should exist
|
|
||||||
When we run "jrnl -n 1"
|
|
||||||
Then the output should contain "This is a new entry in my journal"
|
|
||||||
And the journal should have 1 entry
|
|
||||||
|
|
||||||
Scenario: If the journal file doesn't exist, then it should be created
|
|
||||||
Given we use the config "missing_journal.yaml"
|
|
||||||
Then the journal should not exist
|
|
||||||
When we run "jrnl This is a new entry in my journal"
|
|
||||||
Then the journal should exist
|
|
||||||
When we run "jrnl -n 1"
|
|
||||||
Then the output should contain "This is a new entry in my journal"
|
|
||||||
And the journal should have 1 entry
|
|
||||||
|
|
@ -1,39 +0,0 @@
|
||||||
Feature: Testing a journal with a root directory and multiple files in the format of yyyy/mm/dd.txt
|
|
||||||
|
|
||||||
Scenario: Opening an folder that's not a DayOne folder should treat as folder journal
|
|
||||||
Given we use the config "empty_folder.yaml"
|
|
||||||
When we run "jrnl 23 july 2013: Testing folder journal."
|
|
||||||
Then we should see the message "Entry added"
|
|
||||||
When we run "jrnl -1"
|
|
||||||
Then the output should be "2013-07-23 09:00 Testing folder journal."
|
|
||||||
|
|
||||||
Scenario: Adding entries to a Folder journal should generate date files
|
|
||||||
Given we use the config "empty_folder.yaml"
|
|
||||||
When we run "jrnl 23 July 2013: Testing folder journal."
|
|
||||||
Then we should see the message "Entry added"
|
|
||||||
When the journal directory is listed
|
|
||||||
Then the output should contain "2013/07/23.txt" or "2013\07\23.txt"
|
|
||||||
|
|
||||||
|
|
||||||
Scenario: Adding multiple entries to a Folder journal should generate multiple date files
|
|
||||||
Given we use the config "empty_folder.yaml"
|
|
||||||
When we run "jrnl 23 July 2013: Testing folder journal."
|
|
||||||
And we run "jrnl 3/7/2014: Second entry of journal."
|
|
||||||
Then we should see the message "Entry added"
|
|
||||||
When the journal directory is listed
|
|
||||||
Then the output should contain "2013/07/23.txt" or "2013\07\23.txt"
|
|
||||||
Then the output should contain "2014/03/07.txt" or "2014\03\07.txt"
|
|
||||||
|
|
||||||
Scenario: Out of order entries to a Folder journal should be listed in date order
|
|
||||||
Given we use the config "empty_folder.yaml"
|
|
||||||
When we run "jrnl 3/7/2014 4:37pm: Second entry of journal."
|
|
||||||
Then we should see the message "Entry added"
|
|
||||||
When we run "jrnl 23 July 2013: Testing folder journal."
|
|
||||||
Then we should see the message "Entry added"
|
|
||||||
When we run "jrnl -2"
|
|
||||||
Then the output should be
|
|
||||||
"""
|
|
||||||
2013-07-23 09:00 Testing folder journal.
|
|
||||||
|
|
||||||
2014-03-07 16:37 Second entry of journal.
|
|
||||||
"""
|
|
||||||
|
|
@ -1,37 +0,0 @@
|
||||||
Feature: Loading the encrypted journal type
|
|
||||||
|
|
||||||
Scenario: Loading an encrypted journal
|
|
||||||
Given we use the config "encrypted.yaml"
|
|
||||||
When we run "jrnl -n 1" and enter "bad doggie no biscuit"
|
|
||||||
Then we should be prompted for a password
|
|
||||||
And the output should contain "2013-06-10 15:40 Life is good"
|
|
||||||
|
|
||||||
Scenario: Mistyping your password
|
|
||||||
Given we use the config "basic.yaml"
|
|
||||||
When we run "jrnl --encrypt" and enter
|
|
||||||
"""
|
|
||||||
swordfish
|
|
||||||
sordfish
|
|
||||||
"""
|
|
||||||
Then we should be prompted for a password
|
|
||||||
And we should see the message "Passwords did not match"
|
|
||||||
And the config for journal "default" should not have "encrypt" set
|
|
||||||
And the journal should have 2 entries
|
|
||||||
|
|
||||||
Scenario: Mistyping your password, then getting it right
|
|
||||||
Given we use the config "basic.yaml"
|
|
||||||
When we run "jrnl --encrypt" and enter
|
|
||||||
"""
|
|
||||||
swordfish
|
|
||||||
sordfish
|
|
||||||
swordfish
|
|
||||||
swordfish
|
|
||||||
n
|
|
||||||
"""
|
|
||||||
Then we should be prompted for a password
|
|
||||||
And we should see the message "Passwords did not match"
|
|
||||||
And we should see the message "Journal encrypted"
|
|
||||||
And the config for journal "default" should have "encrypt" set to "bool:True"
|
|
||||||
When we run "jrnl -n 1" and enter "swordfish"
|
|
||||||
Then we should be prompted for a password
|
|
||||||
And the output should contain "2013-06-10 15:40 Life is good"
|
|
||||||
|
|
@ -45,3 +45,39 @@ Feature: Using the installed keyring
|
||||||
@todo
|
@todo
|
||||||
Scenario: Open encrypted journal when keyring exists but fails
|
Scenario: Open encrypted journal when keyring exists but fails
|
||||||
# This should ask the user for the password after the keyring fails
|
# This should ask the user for the password after the keyring fails
|
||||||
|
|
||||||
|
Scenario: Loading an encrypted journal
|
||||||
|
Given we use the config "encrypted.yaml"
|
||||||
|
When we run "jrnl -n 1" and enter "bad doggie no biscuit"
|
||||||
|
Then we should be prompted for a password
|
||||||
|
And the output should contain "2013-06-10 15:40 Life is good"
|
||||||
|
|
||||||
|
Scenario: Mistyping your password
|
||||||
|
Given we use the config "basic.yaml"
|
||||||
|
When we run "jrnl --encrypt" and enter
|
||||||
|
"""
|
||||||
|
swordfish
|
||||||
|
sordfish
|
||||||
|
"""
|
||||||
|
Then we should be prompted for a password
|
||||||
|
And we should see the message "Passwords did not match"
|
||||||
|
And the config for journal "default" should not have "encrypt" set
|
||||||
|
And the journal should have 2 entries
|
||||||
|
|
||||||
|
Scenario: Mistyping your password, then getting it right
|
||||||
|
Given we use the config "basic.yaml"
|
||||||
|
When we run "jrnl --encrypt" and enter
|
||||||
|
"""
|
||||||
|
swordfish
|
||||||
|
sordfish
|
||||||
|
swordfish
|
||||||
|
swordfish
|
||||||
|
n
|
||||||
|
"""
|
||||||
|
Then we should be prompted for a password
|
||||||
|
And we should see the message "Passwords did not match"
|
||||||
|
And we should see the message "Journal encrypted"
|
||||||
|
And the config for journal "default" should have "encrypt" set to "bool:True"
|
||||||
|
When we run "jrnl -n 1" and enter "swordfish"
|
||||||
|
Then we should be prompted for a password
|
||||||
|
And the output should contain "2013-06-10 15:40 Life is good"
|
||||||
|
|
@ -70,3 +70,24 @@ Feature: Searching in a journal
|
||||||
When we run "jrnl -on 'june 6 2013' --short"
|
When we run "jrnl -on 'june 6 2013' --short"
|
||||||
Then the output should be "2013-06-10 15:40 Life is good."
|
Then the output should be "2013-06-10 15:40 Life is good."
|
||||||
|
|
||||||
|
Scenario: Out of order entries to a Folder journal should be listed in date order
|
||||||
|
Given we use the config "empty_folder.yaml"
|
||||||
|
When we run "jrnl 3/7/2014 4:37pm: Second entry of journal."
|
||||||
|
Then we should see the message "Entry added"
|
||||||
|
When we run "jrnl 23 July 2013: Testing folder journal."
|
||||||
|
Then we should see the message "Entry added"
|
||||||
|
When we run "jrnl -2"
|
||||||
|
Then the output should be
|
||||||
|
"""
|
||||||
|
2013-07-23 09:00 Testing folder journal.
|
||||||
|
|
||||||
|
2014-03-07 16:37 Second entry of journal.
|
||||||
|
"""
|
||||||
|
|
||||||
|
# fails when system time is UTC (as on Travis-CI)
|
||||||
|
@skip
|
||||||
|
Scenario: DayOne tag searching should work with tags containing a mixture of upper and lower case.
|
||||||
|
# https://github.com/jrnl-org/jrnl/issues/354
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl @plAy"
|
||||||
|
Then the output should contain "2013-05-17 11:39 This entry has tags!"
|
||||||
|
|
|
||||||
|
|
@ -119,3 +119,27 @@ Feature: Tagging
|
||||||
| (2) ???
|
| (2) ???
|
||||||
| (3) PROFIT!
|
| (3) PROFIT!
|
||||||
"""
|
"""
|
||||||
|
|
||||||
|
Scenario: Loading tags from a DayOne Journal
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl --tags"
|
||||||
|
Then the output should be
|
||||||
|
"""
|
||||||
|
@work : 1
|
||||||
|
@play : 1
|
||||||
|
"""
|
||||||
|
|
||||||
|
Scenario: Saving tags from a DayOne Journal
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl A hard day at @work"
|
||||||
|
And we run "jrnl --tags"
|
||||||
|
Then the output should be
|
||||||
|
"""
|
||||||
|
@work : 2
|
||||||
|
@play : 1
|
||||||
|
"""
|
||||||
|
|
||||||
|
Scenario: Filtering by tags from a DayOne Journal
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl @work"
|
||||||
|
Then the output should be "2013-05-17 11:39 This entry has tags!"
|
||||||
|
|
|
||||||
|
|
@ -69,3 +69,34 @@ Feature: Writing new entries.
|
||||||
Then we should get no error
|
Then we should get no error
|
||||||
And the journal should contain "[2013-07-25 09:00] I saw Elvis."
|
And the journal should contain "[2013-07-25 09:00] I saw Elvis."
|
||||||
And the journal should contain "He's alive."
|
And the journal should contain "He's alive."
|
||||||
|
|
||||||
|
Scenario: Writing into Dayone
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl 01 may 1979: Being born hurts."
|
||||||
|
And we run "jrnl -until 1980"
|
||||||
|
Then the output should be "1979-05-01 09:00 Being born hurts."
|
||||||
|
|
||||||
|
Scenario: Writing into Dayone adds extended metadata
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl 01 may 1979: Being born hurts."
|
||||||
|
And we run "jrnl --export json"
|
||||||
|
Then "entries" in the json output should have 5 elements
|
||||||
|
And the json output should contain entries.0.creator.software_agent
|
||||||
|
And the json output should contain entries.0.creator.os_agent
|
||||||
|
And the json output should contain entries.0.creator.host_name
|
||||||
|
And the json output should contain entries.0.creator.generation_date
|
||||||
|
And the json output should contain entries.0.creator.device_agent
|
||||||
|
And "entries.0.creator.software_agent" in the json output should contain "jrnl"
|
||||||
|
|
||||||
|
# fails when system time is UTC (as on Travis-CI)
|
||||||
|
@skip
|
||||||
|
Scenario: Title with an embedded period on DayOne journal
|
||||||
|
Given we use the config "dayone.yaml"
|
||||||
|
When we run "jrnl 04-24-2014: "Ran 6.2 miles today in 1:02:03. I'm feeling sore because I forgot to stretch.""
|
||||||
|
Then we should see the message "Entry added"
|
||||||
|
When we run "jrnl -1"
|
||||||
|
Then the output should be
|
||||||
|
"""
|
||||||
|
2014-04-24 09:00 Ran 6.2 miles today in 1:02:03.
|
||||||
|
| I'm feeling sore because I forgot to stretch.
|
||||||
|
"""
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue