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

Create a proof-of-concept end-to-end (E2E) starter repository #22

Open
kniedermaier opened this issue Apr 24, 2024 · 0 comments
Open

Create a proof-of-concept end-to-end (E2E) starter repository #22

kniedermaier opened this issue Apr 24, 2024 · 0 comments
Assignees

Comments

@kniedermaier
Copy link

The E2E starter proof-of-concept should have:

  1. a simple toy application (e.g. https://github.com/navapbc/template-infra/tree/main/app)
  2. some simple playwright tests against the toy app

In addition, the proof-of-concept should address the technical implementation considerations found in the related 🔒 tech spec:

  1. Provide scaffolding for Playwright configuration
  2. Include an example test
  3. Document initial configuration settings and setup requirements and an overview of how to run these tests as part of local development
  4. Integrate Playwright with CI/CD as part of a Github Actions workflow

References

This work will help answer the last outstanding question in the "End-to-end starter" 🔒 tech spec around whether it makes sense to create a separate E2E starter template or to embed an E2E starter in existing application templates.

Related repository: https://github.com/navapbc/template-e2e

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