You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bug description
On branch #451, tests were running all green on local but when pushed to GitHub, Vercel tests (which have a different set-up than the one in package.json scripts) had 1 test failing.
Specifically:
/kendraio-app/cypress/e2e/context_and_state.ts
line 232 - 'should allow the disabling of the datagrid'
After running the test on local again, I confirmed this time this test was also failing on local.
At that point, Vercel was showing no test failing. Without pushing new code.
I pushed a "fix" for the test which show all green on local and showed many tests failing on Vercel.
After checking again on local, I noticed the test were passing with one script (run without visual Electron window open) but not with another script.
After reverting the fix to the original state, the above-mentioned test was failing with one script in local, was not failing with another script and all the tests were passing on Vercel.
This behaviour seems apparently random and could be just about this branch, but I am sharing my experience here in case it will happen again. To have a history of this issue.
We should also look into syncing Vercel and local way of setting up and running Cypress tests.
Please check #451 comments and commits test history to understand better.
Reproduction steps
Go to branch revert-fow-instead-workflow
Run: "e2e:serve_and_retest_on_change" -> Check if all test are green
Now run: "e2e:autorun" -> Check if result is the same as previous step
Check in particular test: Context and State
If everything is OK, try the above steps again at this commit history: 34e86db
Expected behaviour
If a test fail, it should fail on local and in Vercel. And it should fail regardless of which scripts I run to run the tests.
Runtime environment
OS: Ubuntu 24.04
Browser: Firefox
Cypress version: "cypress": "^13.3.3"
Angular Version: 16
The text was updated successfully, but these errors were encountered:
It might be related to Angular 15 to 16. Or maybe not as they are not failing on #425
Seems that the script: e2e:autorun do not show the failing test even if e2e:serve_and_test do show it.
With the new scripts test:autorun and test:serve_and_test the results seems consistent between different scrips, in local. Not sure about Vercel but seems consistent there too.
Bug description
On branch #451, tests were running all green on local but when pushed to GitHub, Vercel tests (which have a different set-up than the one in package.json scripts) had 1 test failing.
Specifically:
After running the test on local again, I confirmed this time this test was also failing on local.
At that point, Vercel was showing no test failing. Without pushing new code.
I pushed a "fix" for the test which show all green on local and showed many tests failing on Vercel.
After checking again on local, I noticed the test were passing with one script (run without visual Electron window open) but not with another script.
After reverting the fix to the original state, the above-mentioned test was failing with one script in local, was not failing with another script and all the tests were passing on Vercel.
This behaviour seems apparently random and could be just about this branch, but I am sharing my experience here in case it will happen again. To have a history of this issue.
We should also look into syncing Vercel and local way of setting up and running Cypress tests.
Please check #451 comments and commits test history to understand better.
Reproduction steps
revert-fow-instead-workflow
"e2e:serve_and_retest_on_change"
-> Check if all test are green"e2e:autorun"
-> Check if result is the same as previous stepContext and State
Expected behaviour
If a test fail, it should fail on local and in Vercel. And it should fail regardless of which scripts I run to run the tests.
Runtime environment
"cypress": "^13.3.3"
The text was updated successfully, but these errors were encountered: