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

[FEAT] E2E testing for contributors #830

Open
tianhaoz95 opened this issue Feb 26, 2022 · 0 comments
Open

[FEAT] E2E testing for contributors #830

tianhaoz95 opened this issue Feb 26, 2022 · 0 comments
Assignees
Labels
feature New feature or request

Comments

@tianhaoz95
Copy link
Owner

tianhaoz95 commented Feb 26, 2022

⚠️ So far the conclusion is that documenting the more complicated process for end-to-end testing is of higher priority given the complexity of implementing an automated deploy system.

Objective

To build an infra to do E2E testing which is easier for contributors to use.

Background

E2E testing requires creating a dummy GitHub app and configuring the local environment which take a non-trivial amount of work. It will be great to simplify this process for contributors.

The challenges are:

  • Deploying the staging app requires the webhook secret and client authentication token which is sensitive information that should not be accessed in forks.
    • Use labels or comments that the owner can control to deploy PR to the staging app
  • As there is only one staging app and one testing repository, there can only be one tester at a certain period of time.
    • Deploy one app per PR
    • Use a calendar to coordinate a time for testing
    • Use a queue to coordinate a time for testing

Design

TODO(@tianhaoz95): add some practical design when there is more time to come back to this topic.

Roadmap

  • Document the complicated way to do testing: create a dummy app and dummy repository
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant