fix e2e tests

[northdpole]

Issue

What is the issue?

e2e tests are failing, we should fix them

[iagoscm]

hey @northdpole, where exactly are the e2e tests?

[kart-u]

hello @northdpole
Could you please assign this issue to me? I’d love to actively work on it and contribute.

Hi @northdpole, I explored the repo to locate the e2e tests. The package.json defines "test:e2e": "jest", but I couldn’t find any dedicated e2e test files or folder. Cypress config exists but is not wired to the e2e script. It looks like the e2e setup is incomplete or missing. Could you clarify the intended framework/location for e2e tests?

[R0h1tAnand]

Issue

What is the issue?

e2e tests are failing, we should fix them

Hey @northdpole,

I dug into this and found the problem. The tests were commented out back in November, but the actual issue is that the Jest configuration is completely missing.

The repo has jest and jest-puppeteer installed, but there's no jest.config.js or jest-puppeteer.config.js anywhere. So even if we uncomment the tests, Jest doesn't know how to run them - it can't transform the TypeScript, launch puppeteer, or start the Flask server before running tests.

I also noticed there's a cypress.json file and PR #729 from @tanvikapandey7 trying to add Cypress tests instead.

So before I submit a fix - which approach do you want?

1. I can add the missing Jest config files and get the existing tests working again (probably 1-2 hours of work)
2. Or should I help finish the Cypress migration instead?

Either way, happy to contribute. Just let me know which direction makes sense for the project or I can open a PR and you can review it ???

[northdpole]

i think since we started migrating to cypress lets finish it