Skip to content
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.

Sign up for GitHub

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

fix: tiny wording issue in REGRESSION_TEST_BEST_PRACTICES.md #29123

Merged
merged 1 commit into from
Oct 11, 2023
Merged

fix: tiny wording issue in REGRESSION_TEST_BEST_PRACTICES.md #29123

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion contributingGuides/REGRESSION_TEST_BEST_PRACTICES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Example:
For the test case steps we're asking to be created by the contributor whose PR solved the bug, it'll fall into a category known as bug fix verification. As such, the steps that should be proposed should contain the action element `Verify` and should be tied to the expected behavior in question.
The steps should be broken out by individual actions taking place with the written style of communicating exact steps someone will replicate. As such, simplicity and succinctness is key.

Here are some below examples to illustrate the writing style that covers this:
Below are some examples to illustrate the writing style that covers this:
- Bug: White space appears under compose box when scrolling up in any conversation
- Proposed Test Steps:
- Go to URL https://staging.new.expensify.com/
Expand Down