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.

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

E2E test for cloudflare/pp- components #4

Open
thibmeu opened this issue Nov 9, 2023 · 1 comment
Open

E2E test for cloudflare/pp- components #4

thibmeu opened this issue Nov 9, 2023 · 1 comment

Comments

@thibmeu
Copy link
Contributor

thibmeu commented Nov 9, 2023

This repository is part of a 4 component architecture

The current testing method relies on a dev environment to be deployed.

It would be good to automate it, and share this testbed across repos to validate individual changes. A sample test procedure could be:

  • clone and start pp-issuer: npm run dev -- --port 8787 && curl -X POST http:https://localhost:8787/admin/rotate
  • clone and start pp-attester: npm run dev -- --port 8788 --var ISSUER_DIRECTORY_URL:"http:https://localhost:8787/.well-known/private-token-issuer-directory" --var ISSUER_REQUEST_URL:"http:https://localhost:8787/token-request"
  • clone and start pp-origin npm run dev -- --port 8789 --var ISSUER_NAME:"localhost:8787" --var ORIGIN_NAME:"localhost:8789"
  • clone and build pp-browser-extension npm run build
  • Start a Selenium session (in node.js), load the extension, updates options to have http:https://localhost:8788 as an attester, query the origin http:https://localhost:8789 with Javascript enabled (for client replay), confirm the success page is loaded.
@thibmeu
Copy link
Contributor Author

thibmeu commented Jan 3, 2024

Worth checking how to integrate cloudflare/pp-config

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant