mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-10 16:48:31 +02:00
9664924096
This commit should greatly simplify all password handling logic. No passwords are stored in the config dict anymore. Only the Encrypted Journals have any password related logic. I also had to remove some password fields from the test files, which shows how dangerous the previous approach was. A slight code change could've leaked passwords to the config file. However, I had to change the install progress a little bit to make this work. It will now not ask you for a password right away but rather if you want to encrypt or not. Only if you reply 'y' will it ask you for the password later on.
51 lines
2.1 KiB
Gherkin
51 lines
2.1 KiB
Gherkin
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
|
|
|
|
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
|
|
|
|
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
|
|
|
|
Scenario: Tell user which journal was used
|
|
Given we use the config "multiple.yaml"
|
|
When we run "jrnl work a long day in the office"
|
|
Then we should see the message "Entry added to work journal"
|
|
|
|
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"
|
|
|
|
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
|
|
|
|
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"
|
|
|
|
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"
|