More test shuffling

- Move more tests around
- Rename some test files
- Disable one test (markdown-355)
  Not sure why it's now failing. We should come back to this.
- Add more placeholder test scenarios (marked with @todo)
  You can run just these tests with `behave --no-skipped --tags=todo`
- Fix "missing_directory" test
  This test was missing the config file it was trying to use. So, it was
  really a very useless, broken test that we absolutely should not have
  approved the PR (#963) for.
This commit is contained in:
Jonathan Wren 2020-09-05 19:05:13 -07:00
parent 78d362e0db
commit 1d11f3db32
No known key found for this signature in database
GPG key ID: 43D5FF8722E7F68A
17 changed files with 301 additions and 225 deletions

View file

@ -1,4 +1,4 @@
Feature: Searching a journal
Feature: Searching in a journal
Scenario: Displaying entries using -on today should display entries created today.
Given we use the config "basic.yaml"
@ -6,6 +6,8 @@ Feature: Searching a journal
Then we should see the message "Entry added"
When we run "jrnl -on today"
Then the output should contain "Adding an entry right now."
But the output should not contain "Everything is alright"
And the output should not contain "Life is good"
Scenario: Displaying entries using -from day should display correct entries
Given we use the config "basic.yaml"
@ -32,3 +34,39 @@ Feature: Searching a journal
Then the output should contain "This thing happened yesterday"
And the output should contain "Adding an entry right now."
And the output should not contain "A future entry."
Scenario: Searching for a string
Given we use the config "basic.yaml"
When we run "jrnl -contains life"
Then we should get no error
And the output should be
"""
2013-06-10 15:40 Life is good.
| But I'm better.
"""
Scenario: Searching for a string within tag results
Given we use the config "tags.yaml"
When we run "jrnl @idea -contains software"
Then we should get no error
And the output should contain "software"
Scenario: Searching for a string within AND tag results
Given we use the config "tags.yaml"
When we run "jrnl -and @journal @idea -contains software"
Then we should get no error
And the output should contain "software"
Scenario: Searching for a string within NOT tag results
Given we use the config "tags.yaml"
When we run "jrnl -not @dan -contains software"
Then we should get no error
And the output should contain "software"
Scenario: Searching for dates
Given we use the config "basic.yaml"
When we run "jrnl -on 2013-06-10 --short"
Then the output should be "2013-06-10 15:40 Life is good."
When we run "jrnl -on 'june 6 2013' --short"
Then the output should be "2013-06-10 15:40 Life is good."