Add tests for colors in configs

- Identifying invalid color configs
- Upgrading config from no colors -> colors
This commit is contained in:
Aaron Lichtman 2019-11-06 02:49:47 +01:00
parent 8053d250f4
commit eb1ed3c0cd
No known key found for this signature in database
GPG key ID: 22368077DE9F9903
5 changed files with 54 additions and 7 deletions

View file

@ -13,7 +13,7 @@ Feature: Upgrading Journals from 1.x.x to 2.x.x
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
When we run "jrnl -n 1" and enter
"""
Y
bad doggie no biscuit
@ -21,3 +21,8 @@ Feature: Upgrading Journals from 1.x.x to 2.x.x
"""
Then we should see the message "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 have "colors" set to "{'date':'red', 'title':'blue'}"