Run integration tests against persistent environments, i.e. lit.dev
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 230
- PR merge metrics
- No merged PRs in 30d
Description
Context
We have bugs that come up occasionally due to persistent state. For example playground service worker.
These could be caught by integration testing against lit.dev directly or/and against a stable url staging environment.
Completion criteria:
- Github Action that runs on maybe a once per day schedule integration tests against lit.dev
- Post merge&deploy integration test against live site.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing integration tests and GitHub Actions workflows in the repository. Determine how to run those tests against lit.dev and a post-deploy live site, then verify that a scheduled daily run and a post-merge deployment run both execute successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100