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

Update tests to use more scenario outlines

Browse source 
Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>
This commit is contained in:
Jonathan Wren 2021-04-24 15:26:13 -07:00
parent 3d29b6b6a1
commit e0980cf396
2 changed files with 91 additions and 75 deletions
Download patch file Download diff file Expand all files Collapse all files

66
tests/features/multiple_journals.feature
View file

@ -2,20 +2,32 @@ Feature: Multiple journals
Scenario: Loading a config with two journals
Given we use the config "multiple.yaml"
Then journal "default" should have 2 entries
And journal "work" should have 0 entries
When we run "jrnl -99 --short"
Then the output should be
@todo something
When we run "jrnl work -99 --short"
Then the output should be
@todo something
Scenario: Write to default config by default
Given we use the config "multiple.yaml"
When we run "jrnl this goes to default"
Then journal "default" should have 3 entries
And journal "work" should have 0 entries
When we run "jrnl -99 --short"
Then the output should be
@todo something
When we run "jrnl work -99 --short"
Then the output should be
@todo something
Scenario: Write to specified journal
Given we use the config "multiple.yaml"
When we run "jrnl work a long day in the office"
Then journal "default" should have 2 entries
And journal "work" should have 1 entry
When we run "jrnl -99 --short"
Then the output should be
@todo something
When we run "jrnl work -99 --short"
Then the output should be
@todo something
Scenario: Tell user which journal was used
Given we use the config "multiple.yaml"
@ -25,41 +37,49 @@ Feature: Multiple journals
Scenario: Write to specified journal with a timestamp
Given we use the config "multiple.yaml"
When we run "jrnl work 23 july 2012: a long day in the office"
Then journal "default" should have 2 entries
And journal "work" should have 1 entry
And journal "work" should contain "2012-07-23"
When we run "jrnl -99 --short"
Then the output should be
@todo something
When we run "jrnl work -99 --short"
Then the output should be
@todo something
Scenario: Write to specified journal without a timestamp but with colon
Given we use the config "multiple.yaml"
When we run "jrnl work : a long day in the office"
Then journal "default" should have 2 entries
And journal "work" should have 1 entry
And journal "work" should contain "a long day in the office"
Then the output should be
@todo something
When we run "jrnl work -99 --short"
Then the output should be
@todo something
Scenario: Write to specified journal without a timestamp but with colon
Given we use the config "multiple.yaml"
When we run "jrnl work: a long day in the office"
Then journal "default" should have 2 entries
And journal "work" should have 1 entry
And journal "work" should contain "a long day in the office"
When we run "jrnl -99 --short"
Then the output should be
@todo something
When we run "jrnl work -99 --short"
Then the output should be
@todo something
Scenario: Create new journals as required
Given we use the config "multiple.yaml"
Then journal "ideas" should not exist
When we run "jrnl ideas 23 july 2012: sell my junk on ebay and make lots of money"
Then journal "ideas" should have 1 entry
When we run "jrnl ideas -99 --short"
Then the output should be
@todo something
Scenario: Don't crash if no default journal is specified
Given we use the config "bug343.yaml"
When we run "jrnl a long day in the office"
Then we should see the message "No default journal configured"
Then the output should contain "No default journal configured"
Scenario: Don't crash if no file exists for a configured encrypted journal
Given we use the config "multiple.yaml"
When we run "jrnl new_encrypted Adding first entry" and enter
"""
these three eyes
these three eyes
n
"""
Then we should see the message "Encrypted journal 'new_encrypted' created"
these three eyes
these three eyes
n
Then the output should contain "Encrypted journal 'new_encrypted' created"