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

Jump to bottom

Include type of PRs that does Need Testing in QA documentation. #24

Open
rpattath opened this issue Oct 13, 2020 · 2 comments
Open

Include type of PRs that does Need Testing in QA documentation. #24

rpattath opened this issue Oct 13, 2020 · 2 comments
Labels
Category: Documentation/Training Improvements or additions to documentation. Category: Quality Assurance Changes to code or files that improve testing or fixes bugs. Status: Available Issue was approved and available to claim or abandoned for over 3 days.

Comments

@rpattath
Copy link
Member

Currently the QA doc does not have information about certain PRs that does not need testing. Some examples:

  1. Documentation PRs that describes a process or feature which does not have a set of step by step instruction to be run.
  2. If Travis is implement and working as expected then unit test or any other test automation does not need to be tested again by QA team as long as Travis runs that test and is successful.

Feel free to add more scenarios that I may have missed above.
@rpattath rpattath added Category: Documentation/Training Improvements or additions to documentation. Category: Quality Assurance Changes to code or files that improve testing or fixes bugs. Status: Available Issue was approved and available to claim or abandoned for over 3 days. labels Oct 13, 2020
@DARK-art108
Copy link

Hello @rpattath can I take up this issue? :)

@nlok5923
Copy link
Contributor

nlok5923 commented Dec 6, 2020

@rpattath can i work on it if nobody is currently working on it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Category: Documentation/Training Improvements or additions to documentation. Category: Quality Assurance Changes to code or files that improve testing or fixes bugs. Status: Available Issue was approved and available to claim or abandoned for over 3 days.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rpattath @DARK-art108 @nlok5923