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>
81 lines
3.6 KiB
Gherkin
81 lines
3.6 KiB
Gherkin
# Copyright © 2012-2023 jrnl contributors
|
|
# License: https://www.gnu.org/licenses/gpl-3.0.html
|
|
|
|
Feature: Journals iteracting with the file system in a way that users can see
|
|
|
|
Scenario: Adding entries to a Folder journal should generate date files
|
|
Given we use the config "empty_folder.yaml"
|
|
When we run "jrnl 23 July 2013: Testing folder journal."
|
|
Then we should get no error
|
|
And the journal directory should contain
|
|
"""
|
|
2013/07/23.txt
|
|
"""
|
|
|
|
Scenario: Adding multiple entries to a Folder journal should generate multiple date files
|
|
Given we use the config "empty_folder.yaml"
|
|
When we run "jrnl 23 July 2013: Testing folder journal."
|
|
And we run "jrnl 3/7/2014: Second entry of journal."
|
|
Then we should get no error
|
|
And the journal directory should contain
|
|
"""
|
|
2013/07/23.txt
|
|
"""
|
|
|
|
Scenario: If the journal and its parent directory don't exist, they should be created
|
|
Given we use the config "missing_directory.yaml"
|
|
Then the journal should not exist
|
|
When we run "jrnl This is a new entry in my journal"
|
|
Then the journal should exist
|
|
When we run "jrnl -99 --short"
|
|
Then the output should contain "This is a new entry in my journal"
|
|
|
|
Scenario: If the journal file doesn't exist, then it should be created
|
|
Given we use the config "missing_journal.yaml"
|
|
Then the journal should not exist
|
|
When we run "jrnl This is a new entry in my journal"
|
|
Then the journal should exist
|
|
When we run "jrnl -99 --short"
|
|
Then the output should contain "This is a new entry in my journal"
|
|
|
|
@on_posix
|
|
Scenario: If the directory for a Folder journal ending in a slash ('/') doesn't exist, then it should be created
|
|
Given we use the config "missing_directory.yaml"
|
|
Then the journal "endslash" directory should not exist
|
|
When we run "jrnl endslash This is a new entry in my journal"
|
|
Then the journal "endslash" directory should exist
|
|
When we run "jrnl endslash -1"
|
|
Then the output should contain "This is a new entry in my journal"
|
|
|
|
@on_win
|
|
Scenario: If the directory for a Folder journal ending in a backslash ('\') doesn't exist, then it should be created
|
|
Given we use the config "missing_directory.yaml"
|
|
Then the journal "endbackslash" directory should not exist
|
|
When we run "jrnl endbackslash This is a new entry in my journal"
|
|
Then the journal "endbackslash" directory should exist
|
|
When we run "jrnl endbackslash -1"
|
|
Then the output should contain "This is a new entry in my journal"
|
|
|
|
Scenario: Creating journal with relative path should update to absolute path
|
|
Given we use no config
|
|
When we run "jrnl hello world" and enter
|
|
"""
|
|
test.txt
|
|
n
|
|
\n
|
|
"""
|
|
Then the output should contain "Journal 'default' created"
|
|
When we change directory to "subfolder"
|
|
And we run "jrnl -n 1"
|
|
Then the output should contain "hello world"
|
|
|
|
Scenario: the temporary filename suffix should default to ".jrnl"
|
|
Given we use the config "editor.yaml"
|
|
When we run "jrnl --edit"
|
|
Then the editor should have been called
|
|
Then the editor filename should end with ".jrnl"
|
|
|
|
Scenario: the temporary filename suffix should be "-{template_filename}"
|
|
Given we use the config "editor_markdown_extension.yaml"
|
|
When we run "jrnl --edit"
|
|
Then the editor filename should end with "-extension.md"
|