mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-10 16:48:31 +02:00
80bfff384e
* Add linewrap option 'auto' * Specify the exception thrown * Add BDD test * Specify name instead of number * Create test for linewrap auto and fancy format * Fix linewrap auto for fancy format
135 lines
6.9 KiB
Gherkin
135 lines
6.9 KiB
Gherkin
# Copyright (C) 2012-2022 jrnl contributors
|
|
# License: https://www.gnu.org/licenses/gpl-3.0.html
|
|
|
|
Feature: Multiple journals
|
|
|
|
Scenario: Read a journal from an alternate config
|
|
Given the config "basic_onefile.yaml" exists
|
|
And we use the config "multiple.yaml"
|
|
When we run "jrnl --cf basic_onefile.yaml -999"
|
|
Then the output should not contain "My first entry" # from multiple.yaml
|
|
And the output should contain "Lorem ipsum" # from basic_onefile.yaml
|
|
|
|
Scenario: Write to default journal by default using an alternate config
|
|
Given the config "multiple.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl --cf multiple.yaml this goes to default"
|
|
And we run "jrnl -1"
|
|
Then the output should not contain "this goes to default"
|
|
When we run "jrnl --cf multiple.yaml -1"
|
|
Then the output should contain "this goes to default"
|
|
|
|
Scenario: Write to specified journal using an alternate config
|
|
Given the config "multiple.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl work --cf multiple.yaml a long day in the office"
|
|
And we run "jrnl default --cf multiple.yaml -1"
|
|
Then the output should contain "But I'm better"
|
|
When we run "jrnl work --cf multiple.yaml -1"
|
|
Then the output should contain "a long day in the office"
|
|
|
|
Scenario: Tell user which journal was used while using an alternate config
|
|
Given the config "multiple.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl --cf multiple.yaml work a long day in the office"
|
|
Then the output should contain "Entry added to work journal"
|
|
|
|
Scenario: Write to specified journal with a timestamp using an alternate config
|
|
Given the config "multiple.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl work --cf multiple.yaml 23 july 2012: a long day in the office"
|
|
And we run "jrnl --cf multiple.yaml -1"
|
|
Then the output should contain "But I'm better"
|
|
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
|
|
Given the config "multiple.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl work --cf multiple.yaml : a long day in the office"
|
|
And we run "jrnl --cf multiple.yaml -1"
|
|
Then the output should contain "But I'm better"
|
|
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
|
|
Given the config "multiple.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl ideas -1"
|
|
Then the output should be empty
|
|
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
|
|
Given the config "bug343.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl --cf bug343.yaml a long day in the office"
|
|
Then the output should contain "No default journal configured"
|
|
|
|
Scenario: Don't crash if no file exists for a configured encrypted journal using an alternate config
|
|
Given the config "multiple.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl new_encrypted --cf multiple.yaml Adding first entry" and enter
|
|
these three eyes
|
|
these three eyes
|
|
n
|
|
Then the output should contain "Journal 'new_encrypted' created at "
|
|
|
|
Scenario: Don't overwrite main config when encrypting a journal in an alternate config
|
|
Given the config "basic_onefile.yaml" exists
|
|
And we use the config "multiple.yaml"
|
|
When we run "jrnl --cf basic_onefile.yaml --encrypt" and enter
|
|
these three eyes
|
|
these three eyes
|
|
n
|
|
Then the output should contain "Journal encrypted to features/journals/basic_onefile.journal"
|
|
And the config should contain "encrypt: false"
|
|
|
|
Scenario: Don't overwrite main config when decrypting a journal in an alternate config
|
|
Given the config "editor_encrypted.yaml" exists
|
|
And we use the password "bad doggie no biscuit" if prompted
|
|
And we use the config "basic_encrypted.yaml"
|
|
When we run "jrnl --cf editor_encrypted.yaml --decrypt"
|
|
Then the config should contain "encrypt: true"
|
|
And the output should not contain "Wrong password"
|
|
|
|
Scenario: Show an error message when the config file is empty
|
|
Given we use the config "empty_file.yaml"
|
|
When we run "jrnl -1"
|
|
Then the error output should contain "Unable to parse config file"
|
|
|
|
Scenario: Show an error message when using --config-file with empty file
|
|
Given the config "empty_file.yaml" exists
|
|
And we use the config "basic_onefile.yaml"
|
|
When we run "jrnl --cf empty_file.yaml"
|
|
Then the error output should contain "Unable to parse config file"
|
|
|
|
Scenario: Use a config file with linewrap set to 'auto'
|
|
Given we use the config "linewrap_auto.yaml"
|
|
When we run "jrnl -1"
|
|
Then the output should contain "Life is good."
|
|
|
|
Scenario: Use a config file with linewrap set to 'auto' and use format 'fancy'
|
|
Given we use the config "linewrap_auto.yaml"
|
|
When we run "jrnl -1 --format fancy"
|
|
Then the output should contain "Life is good."
|
|
|
|
Scenario: Show a warning message when the config file contains duplicate keys at the same level
|
|
Given the config "duplicate_keys.yaml" exists
|
|
And we use the config "duplicate_keys.yaml"
|
|
When we run "jrnl -1"
|
|
Then the output should contain "There is at least one duplicate key in your configuration file"
|
|
|
|
Scenario: Show a warning message when using --config-file with duplicate keys
|
|
Given the config "duplicate_keys.yaml" exists
|
|
And we use the config "multiple.yaml"
|
|
When we run "jrnl --cf duplicate_keys.yaml -1"
|
|
Then the output should contain "There is at least one duplicate key in your configuration file"
|
|
|
|
Scenario: Don't show a duplicate keys warning message when using --config-override on an existing value
|
|
Given we use the config "multiple.yaml"
|
|
When we run "jrnl --config-override highlight false"
|
|
Then the output should not contain "There is at least one duplicate key in your configuration file"
|