IQSS / IQSS/dataverse-frontend
Optimize local environment for e2e testing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
Depending on the machine resources, some e2e tests are failing in a local development environment, even though they are passing in Github actions.
To address this, we need to investigate some aspects of the environment that may be optimized:
- docker container sizes
- timeouts for e2e tests
- docker platform configuration
This issue is related to the QA discussion in this PR: https://github.com/IQSS/dataverse-frontend/pull/360#issuecomment-2034439860
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 with the QA discussion in PR #360 and compare the local e2e environment with its GitHub Actions configuration. Investigate the listed container sizes, e2e timeouts, and Docker platform settings; done means local e2e tests pass reliably across machines with the relevant environment changes documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions
- Domain
- devops, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100