Skip to content

If a word/term is found in various files, only one error message should be returned #4

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

Open
baruza opened this issue Jun 14, 2017 · 2 comments

Comments

@baruza
Copy link
Member

baruza commented Jun 14, 2017

Please aggregate all instances of a found word in one error message.

This should not apply for the cases where we are looking at the context of the word ("The word might have different spelling in '..'" and "The word “” seems to be out of context in '...'” error messages.)

@tisnik tisnik self-assigned this Jun 14, 2017
@baruza baruza changed the title If a word/term is found in various files, only one werror message should be returned If a word/term is found in various files, only one error message should be returned Jun 14, 2017
@baruza
Copy link
Member Author

baruza commented Jun 14, 2017

Alternatively, we aggregate all test cases. The error messages could look like:

INFO: “cleanup” might have different spelling.
Found in: test.adoc (4) “steps to cleanup the database” reviewed=?
Introduction.adoc (3) “ perform the cleanup procedure, use” reviewed=?
Explanation: The correct usage of this word depends on the word’s part of speech.
Action: Verify and correct if necessary. Mark as reviewed when used correctly.

@baruza
Copy link
Member Author

baruza commented Jun 14, 2017

Ah the formatting has changed, please, see my suggestions in the test automation meeting minutes:

https://docs.google.com/a/redhat.com/document/d/1NhSRiNp9WqyHuT9LNMymMDWcumQ2P09OqWy7_eJPWYo/edit?usp=sharing

@tisnik tisnik removed their assignment Sep 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants