IQSS / IQSS/dataverse-frontend
FileRepository e2e tests failing
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 31
- Forks
- 26
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 4
Description
After updating branches with develop branch and the new S3 containerized environment some e2e tests from the File JSDataverse Repository are failing.
These tests sometimes fail, not always and they fail both in my local environment and in Github actions.
- Test
'gets all the files by dataset persistentId after dataset deaccession'has a fix by incrementing thedefaultCommandTimeoutto10_000in thecypress.config.tsfile. - Tests
gets all the files by dataset persistentId when files are tabular data&gets all the files by dataset persistentld when passing filterByType criteriaare the ones that fails always on my local end and now the first one mentioned is failing on Github Actions also.
Screenshot from Github Actions 👇
Screenshoot from my local enviroment 👇
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 affected File JSDataverse Repository e2e tests and the Cypress configuration in cypress.config.ts. Run the three named tests locally, then compare their behavior with the GitHub Actions environment and the new S3 containerized setup. Done means the tests pass consistently locally and in GitHub Actions without relying on an unjustified timeout increase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, cypress, github-actions, typescript
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100