sitespeedio / sitespeedio/browsertime
Add GitHub action test for --debug
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 652
- Forks
- 141
- Avg merge
- 3h 56m
- Merged PRs (30d)
- 5
Description
We are missing a test case where we use --debug. To do that we need to either interact with the browser or just kill after some time (and check the log that everything is ok until everything is closed). It would be cool if we can come up with a pattern we can reuse in some other test cases.
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
No file or test path is named. Start by locating existing GitHub Actions tests for the CLI's --debug option and run the relevant workflow; done means the test exercises --debug, verifies the log remains correct through shutdown, and establishes a reusable pattern for similar cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100