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

fix broken jrnl format import

Browse source
This commit is contained in:
dbxnr 2020-02-12 03:09:59 +00:00
parent ff1c180759
commit 2777e6770c
6 changed files with 28 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

39
features/dayone2.feature
View file

@ -1,39 +0,0 @@
Feature: Day One 2.0 implementation details.
Scenario: Loading a Day One 2.0 journal
Given we use the config "basic.yaml"
When we run "jrnl --import dayone2 features/data/journals/dayone2.json"
Then we should get no error
and the output should contain "Journal exported to"
Scenario: Day One 2.0 schema validation fails
Given we use the config "basic.yaml"
When we run "jrnl --import dayone2 features/data/journals/not_dayone2.json"
Then we should get no error
and the output should contain "not the expected Day One 2 format."
Scenario: Converted journal is added to config
Given we use the config "basic.yaml"
When we run "jrnl --import dayone2 features/data/journals/dayone2.json"
When we run "jrnl -ls"
Then the output should contain "dayone2.txt"
And the output should contain "default"
Scenario: Converted journal is validated
Given we use the config "basic.yaml"
When we run "jrnl --import dayone2 features/data/journals/dayone2.json"
When we run "jrnl dayone2 -n 2"
Then we should get no error
and the output should contain "2020-01-10 12:21 Entry Number Two."
Scenario: Check tags are handled correctly
Given we use the config "basic.yaml"
When we run "jrnl --import dayone2 features/data/journals/dayone2.json"
When we run "jrnl dayone2 --tags"
Then we should get no error
and the output should contain
"""
@great : 2
@awesome : 1
"""