-
-
Notifications
You must be signed in to change notification settings - Fork 526
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add bdd tests for jrnl installation #1513
Conversation
tests/bdd/features/install.feature
Outdated
| | ||
| |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you use \n
for this instead of a pipe? I think that will be a bit more Gherkin-appropriate since the Gherkin reference has some allowances for this inside of table cells already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I can do that. I can see how that might be confusing.
@apainintheneck Hey, this PR is looking good so far; we just need a little more time to review (had a lot of PRs today, and focusing on the beta). We'll come back to this next week and get merged in. Thank you! |
9d5a574
to
3d29514
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one tiny case change, please. Thanks for adding these much-needed tests.
Checklist
for the same issue.
This is just a first stab at adding BDD tests related to installation as mentioned in #1473. I couldn't really find a way to make it work with just Gherkin because of some of the required mocking and steps that were added. Is that sorta what you had in mind?
The biggest change I made was to use the pipe character
|
as the equivalent of an empty line of input in theall_inputs
fixture used by thewhen_steps.we_run_jrnl()
method. This change made it a lot easier to test the default journal installation case and I think it makes the BDD test more readable too. Do you all know of a better way to handle that?Resolves #1473.