Create manual testing documentation procedure#14776
Merged
Merged
Conversation
michaelDCurran
approved these changes
Apr 3, 2023
See test results for failed build of commit 89ede9ac41 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Link to issue number:
None
Summary of the issue:
Commonly tested components of NVDA should have standard test plans.
This gives contributors a base manual testing plan when creating PRs that touch these NVDA components.
This also gives alpha/beta testers a base test plan for NVDA.
Description of user facing changes
None
Description of development approach
A directory has been created,
./tests/manual, which contains markdown files group by the NVDA component, e.g. "addon store", "start up / shutdown", "speech dictionaries", "settings", etc.The goal is to document manual test plans for commonly tested NVDA components.
Testing strategy:
None
Known issues with pull request:
None
Change log entries:
N/A
Code Review Checklist: