mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-10 00:28:31 +02:00
1530ad39a1
* Encapsulate all multiline strings in triple-quotes in Gherkin files Since pytest-bdd v8.0.0 uses the official Gherkin parser, multiline strings must now be encapsulated by triple-quotes. See: - https://pytest-bdd.readthedocs.io/en/stable/#id2 - https://pytest-bdd.readthedocs.io/en/stable/#docstrings * Remove comments in Gherkin files causing test breakage These comments break the step matching. * Fix compatibility of step-functions matching on multiple lines In pytest-bdd v8.0.0 it is no longer possible to match based on multiple lines, which breaks essentially all steps that support docstrings. Solve this by adding a wrapper-function for each of these instances, that matches the docstring step, and calls the original function. So, what used to be: @then(parse("the output should match\n{regex}")) @then(parse('the output should match "{regex}"')) def output_should_match(regex, cli_run): ... Is now: @then(parse("the output should match")) def output_should_match_docstring(cli_run, docstring): output_should_match(docstring, cli_run) @then(parse('the output should match "{regex}"')) def output_should_match(regex, cli_run): ... There is possibly a way around this that is much better than what I've done here, but this is a start at least. * Update version requirement of pytest-bdd to >=8.0 * Update tox config to match poetry config --------- Co-authored-by: Micah Jerome Ellison <micah.jerome.ellison@gmail.com>
119 lines
4.3 KiB
Gherkin
119 lines
4.3 KiB
Gherkin
# Copyright © 2012-2023 jrnl contributors
|
|
# License: https://www.gnu.org/licenses/gpl-3.0.html
|
|
|
|
Feature: Encrypting and decrypting journals
|
|
|
|
Scenario: Decrypting a journal
|
|
Given we use the config "encrypted.yaml"
|
|
And we use the password "bad doggie no biscuit" if prompted
|
|
When we run "jrnl --decrypt"
|
|
Then the output should contain "Journal decrypted"
|
|
And the config for journal "default" should contain "encrypt: false"
|
|
When we run "jrnl -99 --short"
|
|
Then the output should be
|
|
"""
|
|
2013-06-09 15:39 My first entry.
|
|
2013-06-10 15:40 Life is good.
|
|
"""
|
|
|
|
|
|
@todo
|
|
Scenario: Trying to decrypt an already unencrypted journal
|
|
# This should warn the user that the journal is already encrypted
|
|
Given we use the config "simple.yaml"
|
|
When we run "jrnl --decrypt"
|
|
Then the config for journal "default" should contain "encrypt: false"
|
|
When we run "jrnl -99 --short"
|
|
Then the output should be
|
|
"""
|
|
2013-06-09 15:39 My first entry.
|
|
2013-06-10 15:40 Life is good.
|
|
"""
|
|
|
|
|
|
Scenario: Trying to encrypt an already encrypted journal
|
|
Given we use the config "encrypted.yaml"
|
|
When we run "jrnl --encrypt" and enter "bad doggie no biscuit"
|
|
Then the output should contain "already encrypted. Create a new password."
|
|
Then we should be prompted for a password
|
|
|
|
Scenario Outline: Encrypting a journal
|
|
Given we use the config "simple.yaml"
|
|
When we run "jrnl --encrypt" and enter
|
|
"""
|
|
swordfish
|
|
swordfish
|
|
n
|
|
"""
|
|
Then we should get no error
|
|
And the output should contain "Journal encrypted"
|
|
And the config for journal "default" should contain "encrypt: true"
|
|
When we run "jrnl -n 1" and enter "swordfish"
|
|
Then we should be prompted for a password
|
|
And the output should contain "2013-06-10 15:40 Life is good"
|
|
|
|
Scenario: Encrypt journal twice and get prompted each time
|
|
Given we use the config "simple.yaml"
|
|
And we don't have a keyring
|
|
When we run "jrnl --encrypt" and enter
|
|
"""
|
|
swordfish
|
|
swordfish
|
|
y
|
|
"""
|
|
Then we should get no error
|
|
And the output should contain "Journal encrypted"
|
|
When we run "jrnl --encrypt" and enter
|
|
"""
|
|
swordfish
|
|
tuna
|
|
tuna
|
|
y
|
|
"""
|
|
Then we should get no error
|
|
And the output should contain "Journal default is already encrypted. Create a new password."
|
|
And we should be prompted for a password
|
|
And the config for journal "default" should contain "encrypt: true"
|
|
|
|
Scenario: Encrypt journal twice and get prompted each time with keyring
|
|
Given we use the config "simple.yaml"
|
|
And we have a keyring
|
|
When we run "jrnl --encrypt" and enter
|
|
"""
|
|
swordfish
|
|
swordfish
|
|
y
|
|
"""
|
|
Then we should get no error
|
|
And the output should contain "Journal encrypted"
|
|
When we run "jrnl --encrypt" and enter
|
|
"""
|
|
tuna
|
|
tuna
|
|
y
|
|
"""
|
|
Then we should get no error
|
|
And the output should contain "Journal default is already encrypted. Create a new password."
|
|
And we should be prompted for a password
|
|
And the config for journal "default" should contain "encrypt: true"
|
|
|
|
Scenario Outline: Running jrnl with encrypt: true on unencryptable journals
|
|
Given we use the config "<config_file>"
|
|
When we run "jrnl --config-override encrypt true here is a new entry"
|
|
Then the error output should contain "journal can't be encrypted"
|
|
|
|
Examples: configs
|
|
| config_file |
|
|
| basic_folder.yaml |
|
|
| basic_dayone.yaml |
|
|
|
|
|
|
Scenario Outline: Attempt to encrypt a folder or DayOne journal should result in an error
|
|
Given we use the config "<config_file>"
|
|
When we run "jrnl --encrypt"
|
|
Then the error output should contain "can't be encrypted"
|
|
|
|
Examples: configs
|
|
| config_file |
|
|
| basic_folder.yaml |
|
|
| basic_dayone.yaml |
|