fz0x1/jrnl
1
0
Fork 0
mirror of https://github.com/jrnl-org/jrnl.git synced 2025-05-18 12:08:31 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Uncomment and rework remaining tests for pytest-bdd instead of behave

Browse source
This commit is contained in:
Micah Jerome Ellison 2021-10-09 14:15:06 -07:00
parent fc6d4506cf
commit 66ecdcf48e
1 changed files with 52 additions and 51 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

103
tests/bdd/features/config_file.feature
View file

@ -7,9 +7,6 @@ Feature: Multiple journals
Then the output should not contain "My first entry" # from multiple.yaml Then the output should not contain "My first entry" # from multiple.yaml
And the output should contain "Lorem ipsum" # from basic_onefile.yaml And the output should contain "Lorem ipsum" # from basic_onefile.yaml
# This test is breaking because multiple.yaml is "upgrading" and overwriting basic_onefile.yaml in the process
# Backup your personal config before manually reproducing this! It will replace
# your config file with the upgraded form of multiple.yaml (which is the bug)
Scenario: Write to default journal by default using an alternate config Scenario: Write to default journal by default using an alternate config
Given we use the config "multiple.yaml" Given we use the config "multiple.yaml"
Given we use the config "basic_onefile.yaml" Given we use the config "basic_onefile.yaml"
@ -19,58 +16,62 @@ Feature: Multiple journals
When we run "jrnl --cf multiple.yaml -1" When we run "jrnl --cf multiple.yaml -1"
Then the output should contain "this goes to default" Then the output should contain "this goes to default"
# # The rest of these tests haven't changed except for the given steps. Each needs Scenario: Write to specified journal using an alternate config
# # to be re-worked Given we use the config "multiple.yaml"
# Scenario: Write to specified journal using an alternate config Given we use the config "basic_onefile.yaml"
# Given we use the config "multiple.yaml" When we run "jrnl work --cf multiple.yaml a long day in the office"
# Given we use the config "basic_onefile.yaml" And we run "jrnl default --cf multiple.yaml -1"
# When we run "jrnl work --cf features/data/configs/alternate.yaml a long day in the office" Then the output should contain "But I'm better"
# Then journal "default" should have 2 entries When we run "jrnl work --cf multiple.yaml -1"
# And journal "work" should have 1 entry Then the output should contain "a long day in the office"
# Scenario: Tell user which journal was used using an alternate config Scenario: Tell user which journal was used using an alternate config
# Given we use the config "multiple.yaml" Given we use the config "multiple.yaml"
# Given we use the config "basic_onefile.yaml" Given we use the config "basic_onefile.yaml"
# When we run "jrnl --cf features/data/configs/alternate.yaml work a long day in the office" When we run "jrnl --cf multiple.yaml work a long day in the office"
# Then we should see the message "Entry added to work journal" Then we should see the message "Entry added to work journal"
# Scenario: Write to specified journal with a timestamp using an alternate config Scenario: Write to specified journal with a timestamp using an alternate config
# Given we use the config "multiple.yaml" Given we use the config "multiple.yaml"
# Given we use the config "basic_onefile.yaml" Given we use the config "basic_onefile.yaml"
# When we run "jrnl work --cf features/data/configs/alternate.yaml 23 july 2012: a long day in the office" When we run "jrnl work --cf multiple.yaml 23 july 2012: a long day in the office"
# Then journal "default" should have 2 entries And we run "jrnl --cf multiple.yaml -1"
# And journal "work" should have 1 entry Then the output should contain "But I'm better"
# And journal "work" should contain "2012-07-23" When we run "jrnl --cf multiple.yaml work -1"
Then the output should contain "a long day in the office"
And the output should contain "2012-07-23"
# Scenario: Write to specified journal without a timestamp but with colon using an alternate config Scenario: Write to specified journal without a timestamp but with colon using an alternate config
# Given we use the config "multiple.yaml" Given we use the config "multiple.yaml"
# Given we use the config "basic_onefile.yaml" Given we use the config "basic_onefile.yaml"
# When we run "jrnl work --cf features/data/configs/alternate.yaml : a long day in the office" When we run "jrnl work --cf multiple.yaml : a long day in the office"
# Then journal "default" should have 2 entries And we run "jrnl --cf multiple.yaml -1"
# And journal "work" should have 1 entry Then the output should contain "But I'm better"
# And journal "work" should contain "a long day in the office" When we run "jrnl --cf multiple.yaml work -1"
Then the output should contain "a long day in the office"
# Scenario: Create new journals as required using an alternate config Scenario: Create new journals as required using an alternate config
# Given we use the config "multiple.yaml" Given we use the config "multiple.yaml"
# Given we use the config "basic_onefile.yaml" Given we use the config "basic_onefile.yaml"
# Then journal "ideas" should not exist When we run "jrnl ideas -1"
# When we run "jrnl ideas --cf features/data/configs/alternate.yaml 23 july 2012: sell my junk on ebay and make lots of money" Then the output should be empty
# Then journal "ideas" should have 1 entry When we run "jrnl ideas --cf multiple.yaml 23 july 2012: sell my junk on ebay and make lots of money"
Then the output should contain "Journal 'ideas' created"
When we run "jrnl ideas --cf multiple.yaml -1"
Then the output should contain "sell my junk on ebay and make lots of money"
# Scenario: Don't crash if no default journal is specified using an alternate config Scenario: Don't crash if no default journal is specified using an alternate config
# Given we use the config "multiple.yaml" Given we use the config "bug343.yaml"
# Given we use the config "basic_onefile.yaml" Given we use the config "basic_onefile.yaml"
# When we run "jrnl --cf features/data/configs/bug343.yaml a long day in the office" When we run "jrnl --cf bug343.yaml a long day in the office"
# Then we should see the message "No default journal configured" Then we should see the message "No default journal configured"
# Scenario: Don't crash if no file exists for a configured encrypted journal using an alternate config Scenario: Don't crash if no file exists for a configured encrypted journal using an alternate config
# Given we use the config "multiple.yaml" Given we use the config "multiple.yaml"
# Given we use the config "basic_onefile.yaml" Given we use the config "basic_onefile.yaml"
# When we run "jrnl new_encrypted --cf features/data/configs/alternate.yaml Adding first entry" and enter When we run "jrnl new_encrypted --cf multiple.yaml Adding first entry" and enter
# """ these three eyes
# these three eyes these three eyes
# these three eyes n
# n Then we should see the message "Encrypted journal 'new_encrypted' created"
# """
# Then we should see the message "Encrypted journal 'new_encrypted' created"