Skip to content

docs: Add documentation for how to QA the GPP module locally #133

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

Merged
mashalifshin merged 2 commits into from
Oct 27, 2025
Merged

docs: Add documentation for how to QA the GPP module locally #133

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
dafe3b6
Add docs for QAing GPP
mashalifshin Oct 14, 2025
d20cb15
Fix typos and formatting
mashalifshin Oct 18, 2025
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
53 changes: 53 additions & 0 deletions docs/gpp_qa.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,53 @@
# QAing the MAJC GPP module

## Setup
1. Add a new line to your /etc/hosts file: `127.0.0.1 localhost.example-domain.com`
2. Visit http://localhost.example-domain.com:8080/examples/iife/
3. If you are getting "secure connection" https errors, we only know how to get past this in Chrome. Use Chrome and go to chrome://net-internals/#hsts
4. Input 'example-domain.com' into the last form field for "Delete domain security policies" and hit "Delete"
5. Load http://localhost.example-domain.com:8080/examples/iife/ in the browser

## Test with real GPP bundle. This verifies the behavior when GPP is enabled on the domain.
1. Delete domain security policies for example-domain.com. Clear all storage data and cookies.
2. Update the code to use the real bundle and real production placements. Add this real bundle script tag snippet to the `<head>` of the page:

```js
<script src="https://cdn.cookielaw.org/scripttemplates/otSDKStub.js" type="text/javascript" charset="UTF-8"
data-domain-script="0198ae37-ce9e-7da0-b98e-269bd00d6e36"></script>
````

The MAJC GPP module waits for 200ms before making an ads request to see if a GPP bundle from OneTrust will load.

If not, it will default the GPP string to "".

Ad requests should include a `gpp` param that's either set to an encoded value from OneTrust or "".

To adjust the 200ms to be longer, to make it easier to verify the wait behavior, run this snippet in the browser console:

```javascript
mozAds.setConfigValue('gppReadyTimeout', 2000);
```

### Test first run
1. Load example page
2. Expect to see an ad request go out after 200ms with blank GPP string
### Test reject all
- Clear all storage
- Reload example page
- Expect to see an ad request go out right away (~40-100ms) with the default, which is "reject" GPP string value `DBABBg~BUUAAACA.YA`
- Select "Reject all" from the cookie footer
- Reload example page
- Expect to see an ad request go out right away (~40-100ms) with "reject" GPP string value `DBABBg~BUUAAACA.YA`
### Test accept all
- Clear all storage
- Reload example page
- Expect to see an ad request go out right away with the default, which is "reject" GPP string value `DBABBg~BUUAAACA.YA`
- Select "Accept all" from the cookie footer
- Reload example page
- Expect to see an ad request go out right away with "accept" GPP string value `DBABBg~BUoAAACA.YA`

## Test without any bundle. This verifies the behavior when GPP is not enabled on the domain.
1. Delete domain security policies for example-domain.com. Clear all storage data and cookies.
2. Set the code to use no bundle and real production ad placements
3. Load the example page
4. Expect to see an ad request go out after 200ms with blank GPP string