Add cypress test to verify downloading

## Change Summary Provide summary of changes with issue number if any. ## Have you done all the things below - [ ] Run `npm run format` to format everything with prettier. - [ ] Run `npm run lint` and fix all errors and new warnings. - [ ] Made sure that all database changes have a migration and you ran `npm run dbtypes`. - [ ] Make sure to run the unit tests with `npm test`. This project uses vitest for more details look at [Vitest](#Vitest). - [ ] Made sure to test your changes with [cypress](#cypress) by running `npm run start:test` and in another terminal `npm run cypress` and when it is done stopping the server with ctr-c. If this fails, and you don't know why look in the [cypress section](#cypress), or just create the pull request anyway and leave this unchecked. - [ ] If you added any features it would be great if you tested them with cypress(Not required). - [ ] Did you make sure to have all text in the correct format as mentioned in [translating.md](TRANSLATING.MD#help) ## Change type - [ ] feat: (new feature for the user, not a new feature for build script) - [ ] fix: (bug fix for the user, not a fix to a build script) - [ ] docs: (changes to the documentation, changes to issue or pull request templates;) - [ ] style: (formatting, missing semi colons, fixing typo, etc) - [ ] refactor: (refactoring production code, eg. renaming a variable) - [ ] test: (adding missing cypress tests, refactoring cypress tests; editing github actions; no production code change) - [ ] new league type: (added another league type like the premier league ) ## Additional information / screenshots (optional) Anything for maintainers to be made aware of

lukasdotcom commented

2026-02-04 15:46:32 -05:00

Owner

Change Summary

Provide summary of changes with issue number if any.

Have you done all the things below

Run npm run format to format everything with prettier.
Run npm run lint and fix all errors and new warnings.
Made sure that all database changes have a migration and you ran npm run dbtypes.
Make sure to run the unit tests with npm test. This project uses vitest for more details look
at Vitest.
Made sure to test your changes with cypress by running npm run start:test and in another terminal
npm run cypress and when it is done stopping the server with ctr-c. If this fails, and you don't know why look in
the cypress section, or just create the pull request anyway and leave this unchecked.
If you added any features it would be great if you tested them with cypress(Not required).
Did you make sure to have all text in the correct format as mentioned in translating.md

Change type

feat: (new feature for the user, not a new feature for build script)
fix: (bug fix for the user, not a fix to a build script)
docs: (changes to the documentation, changes to issue or pull request templates;)
style: (formatting, missing semi colons, fixing typo, etc)
refactor: (refactoring production code, eg. renaming a variable)
test: (adding missing cypress tests, refactoring cypress tests; editing github actions; no production code change)
new league type: (added another league type like the premier league )

Additional information / screenshots (optional)

Anything for maintainers to be made aware of

Rows
Columns

Add cypress test to verify downloading #937

Change Summary

Have you done all the things below

Change type

Additional information / screenshots (optional)