mirror of
https://github.com/jrnl-org/jrnl.git
synced 2025-05-10 16:48: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>
71 lines
2.8 KiB
Gherkin
71 lines
2.8 KiB
Gherkin
# Copyright © 2012-2023 jrnl contributors
|
|
# License: https://www.gnu.org/licenses/gpl-3.0.html
|
|
|
|
Feature: Upgrading Journals from 1.x.x to 2.x.x
|
|
|
|
Scenario: Upgrade and parse journals with square brackets
|
|
Given we use the config "upgrade_from_195.json"
|
|
When we run "jrnl -9" and enter "Y"
|
|
When we run "jrnl -99 --short"
|
|
Then the output should be
|
|
"""
|
|
2010-06-10 15:00 A life without chocolate is like a bad analogy.
|
|
2013-06-10 15:40 He said "[this] is the best time to be alive".Lorem ipsum dolor sit amet, consectetur adipiscing elit. Praesent malesuada
|
|
"""
|
|
And the output should contain
|
|
"""
|
|
2010-06-10 15:00 A life without chocolate is like a bad analogy.
|
|
"""
|
|
And the output should contain
|
|
"""
|
|
2013-06-10 15:40 He said "[this] is the best time to be alive".
|
|
"""
|
|
|
|
Scenario: Upgrading a journal encrypted with jrnl 1.x
|
|
Given we use the config "encrypted_old.json"
|
|
When we run "jrnl -n 1" and enter
|
|
"""
|
|
Y
|
|
bad doggie no biscuit
|
|
bad doggie no biscuit
|
|
"""
|
|
Then we should be prompted for a password
|
|
And the output should contain "2013-06-10 15:40 Life is good"
|
|
|
|
Scenario: Upgrading a config without colors to colors
|
|
Given we use the config "no_colors.yaml"
|
|
When we run "jrnl -n 1"
|
|
Then the config should contain
|
|
"""
|
|
colors:
|
|
date: none
|
|
title: none
|
|
body: none
|
|
tags: none
|
|
"""
|
|
|
|
Scenario: Upgrade and parse journals with little endian date format
|
|
Given we use the config "upgrade_from_195_little_endian_dates.json"
|
|
When we run "jrnl -9 --short" and enter "Y"
|
|
Then the output should contain
|
|
"""
|
|
10.06.2010 15:00 A life without chocolate is like a bad analogy.
|
|
10.06.2013 15:40 He said "[this] is the best time to be alive".
|
|
"""
|
|
|
|
Scenario: Upgrade with missing journal
|
|
Given we use the config "upgrade_from_195_with_missing_journal.json"
|
|
When we run "jrnl --list" and enter "Y"
|
|
Then the output should contain "features/journals/missing.journal does not exist"
|
|
And we should get no error
|
|
|
|
Scenario: Upgrade with missing encrypted journal
|
|
Given we use the config "upgrade_from_195_with_missing_encrypted_journal.json"
|
|
When we run "jrnl --list" and enter
|
|
"""
|
|
Y
|
|
bad doggie no biscuit
|
|
"""
|
|
Then the output should contain "features/journals/missing.journal does not exist"
|
|
And the output should contain "We're all done"
|
|
And we should get no error
|