docs: Add documentation for how to QA the GPP module locally #133
Conversation
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
mashalifshin
force-pushed
the
gpp-qa-doc
branch
from
4d451bb to
d20cb15
Compare
luc-lisi
approved these changes
Oct 27, 2025
Contributor
luc-lisi
left a comment
luc-lisi
left a comment
There was a problem hiding this comment.
Yay documentation! Thank you so much for this!
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.
Problem Statement
QAing the different states of the presence/absence of the GPP bundle in a non-production environment was pretty tricky and required some setup.
Proposed Changes
This adds a doc the for the local GPP QA process. Since getpocket.com doesn't exist anymore, I changed the doc to use a generic domain instead.
Verification Steps
It would be great if the reviewer would run through these again, but I don't think there is a way to do it now that getpocket.com is no longer live. That said, we did use these exact steps when QAing the GPP fix, so it should be decently exercised already.