mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-20 21:18:32 +02:00
standardize whitespace in behave tests, take out duplicate test
This commit is contained in:
parent
8483d36208
commit
9116b63d8a
13 changed files with 327 additions and 339 deletions
|
@ -36,22 +36,6 @@ Feature: Tagging
|
||||||
| basic_folder |
|
| basic_folder |
|
||||||
| basic_dayone |
|
| basic_dayone |
|
||||||
|
|
||||||
Scenario Outline: Emails addresses should not be parsed as tags
|
|
||||||
Given we use the config "<config>.yaml"
|
|
||||||
When we run "jrnl 2020-09-26: The email address test@example.com doesn't seem to work for me"
|
|
||||||
When we run "jrnl 2020-09-26: The email address test@example.org also doesn't work for me"
|
|
||||||
When we run "jrnl 2020-09-26: I tried test@example.org and test@example.edu too"
|
|
||||||
Then we flush the output
|
|
||||||
When we run "jrnl --tags -on 2020-09-26"
|
|
||||||
Then we should get no error
|
|
||||||
And the output should be "[No tags found in journal.]"
|
|
||||||
|
|
||||||
Examples: configs
|
|
||||||
| config |
|
|
||||||
| basic_onefile |
|
|
||||||
| basic_folder |
|
|
||||||
| basic_dayone |
|
|
||||||
|
|
||||||
Scenario Outline: Entry can start and end with tags
|
Scenario Outline: Entry can start and end with tags
|
||||||
Given we use the config "<config>.yaml"
|
Given we use the config "<config>.yaml"
|
||||||
When we run "jrnl 2020-09-26: @foo came over, we went to a @bar"
|
When we run "jrnl 2020-09-26: @foo came over, we went to a @bar"
|
||||||
|
|
|
@ -54,7 +54,8 @@ Feature: Writing new entries.
|
||||||
| editor_empty_folder |
|
| editor_empty_folder |
|
||||||
| dayone |
|
| dayone |
|
||||||
|
|
||||||
@todo # this might need a new step for editors + encryption
|
# this might need a new step for editors + encryption
|
||||||
|
@todo
|
||||||
Scenario: Writing an empty entry from the editor in encrypted journal should yield "Nothing saved to file" message
|
Scenario: Writing an empty entry from the editor in encrypted journal should yield "Nothing saved to file" message
|
||||||
Given we use the config "editor_encrypted.yaml"
|
Given we use the config "editor_encrypted.yaml"
|
||||||
#When we open the editor and enter nothing
|
#When we open the editor and enter nothing
|
||||||
|
@ -72,11 +73,13 @@ Feature: Writing new entries.
|
||||||
| simple |
|
| simple |
|
||||||
| empty_folder |
|
| empty_folder |
|
||||||
|
|
||||||
@todo # There is a problem with DayOne behave tests and console input
|
@todo
|
||||||
Scenario: Writing an empty entry from the command line in DayOne journal
|
Scenario: Writing an empty entry from the command line in DayOne journal
|
||||||
|
# There is a problem with DayOne behave tests and console input
|
||||||
|
|
||||||
@todo # Need some steps for encryption + editor
|
@todo
|
||||||
Scenario: Writing an empty entry from the command line in encrypted journal
|
Scenario: Writing an empty entry from the command line in encrypted journal
|
||||||
|
# Need some steps for encryption + editor
|
||||||
|
|
||||||
Scenario Outline: Writing an empty entry from the editor should yield nothing
|
Scenario Outline: Writing an empty entry from the editor should yield nothing
|
||||||
Given we use the config "<config_file>.yaml"
|
Given we use the config "<config_file>.yaml"
|
||||||
|
@ -159,8 +162,9 @@ Feature: Writing new entries.
|
||||||
| empty_folder |
|
| empty_folder |
|
||||||
| encrypted |
|
| encrypted |
|
||||||
|
|
||||||
@todo # Need to test DayOne w/out an editor
|
@todo
|
||||||
Scenario: Writing an entry at the prompt (no editor) in DayOne journal
|
Scenario: Writing an entry at the prompt (no editor) in DayOne journal
|
||||||
|
# Need to test DayOne w/out an editor
|
||||||
|
|
||||||
Scenario: Writing into Dayone
|
Scenario: Writing into Dayone
|
||||||
Given we use the config "dayone.yaml"
|
Given we use the config "dayone.yaml"
|
||||||
|
|
Loading…
Add table
Reference in a new issue