Update README to reflect current best practices in creating and running tests #477
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #472.
🤔 What's changed?
This PR updates README to
go test
usage over CLIgodog
as it grants better flexibility and familiarity for Go developers,context.Context
in step examples for better concurrency readiness.⚡️ What's your motivation?
Running tests with CLI
godog
has limitations (#154) and is sometimes a bit obscure due to doing "magic" under the hood, using regular Go tests is (in my opinion) a better approach in general, so I think we should update documentation to encourage morego test
usage.🏷️ What kind of change is this?
♻️ Anything particular you want feedback on?
📋 Checklist:
This text was originally generated from a template, then edited by hand. You can modify the template here.