|Konrad Dzwinel 107a408701||2 days ago|
|.github/workflows||7 months ago|
|TEMPLATES||7 months ago|
|autofill||1 month ago|
|crawler||7 months ago|
|features||3 weeks ago|
|helpers||3 weeks ago|
|privacy-protections||3 days ago|
|security||3 days ago|
|tracker-reporting||7 months ago|
|.eslintignore||7 months ago|
|.eslintrc||7 months ago|
|.gitignore||9 months ago|
|README.md||3 days ago|
|git.sh||2 days ago|
|index.html||3 days ago|
|package-lock.json||7 months ago|
|package.json||5 months ago|
|server.js||1 month ago|
🛡 Collection of pages for testing various privacy and security features of browsers and browser extensions.
The site with all tests is live here. All tests run either on page load or provide instructions on how to run them.
Those tests by default require clicking a button to start, but can be run immediately on page load when loaded with a
?run query or by calling a global
runTests() function. Results from those pages are available in the global
results object that can be downloaded as JSON using "download results" button.
Please note that we are not taking external contributions for new test pages, but we welcome all bug reports.
We have couple of test domains, that all resolve to
privacy-test-pages.glitch.me, which help us simulate various scenarios:
good.third-party.site- non-tracking third party, it's not on our blocklist and will not be blocked by our clients
broken.third-party.site- tracking third party that we can't block (e.g. due to brekage), it's on our blocklist, but it will not be blocked by our clients
bad.third-party.site- tracking third party that's on our blocklist and our clients will block
If you are working on a simple page you can start any local server (e.g.
python -m SimpleHTTPServer 8000) in the main folder of the project.
If you are working on a complex page you may need to run our custom server (
node server.js) which will require you to install all dependencies first (
After PR is merged test pages are automatically deployed to glitch (code) and github pages (legacy).