From 0e33a476ea0fd8a5b836aadbc9a8d3b3a117c66d Mon Sep 17 00:00:00 2001 From: Jonathan Wren Date: Sat, 16 Jul 2022 14:03:33 -0700 Subject: [PATCH] update tests --- tests/bdd/features/config_file.feature | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/tests/bdd/features/config_file.feature b/tests/bdd/features/config_file.feature index d8bcfc31..d6b6121f 100644 --- a/tests/bdd/features/config_file.feature +++ b/tests/bdd/features/config_file.feature @@ -111,15 +111,15 @@ Feature: Multiple journals 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 "One or more keys appear multiple times at the same level" + 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 "One or more keys appear multiple times at the same level" + 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 "One or more keys appear multiple times at the same level" \ No newline at end of file + Then the output should not contain "There is at least one duplicate key in your configuration file" \ No newline at end of file