Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI mode | TypeError: suite.tests is not iterable #27871

Closed
403-html opened this issue Sep 21, 2023 · 2 comments
Closed

UI mode | TypeError: suite.tests is not iterable #27871

403-html opened this issue Sep 21, 2023 · 2 comments
Assignees

Comments

@403-html
Copy link

Current behavior

We get error when we run test suite. All was working for quite a long time so not sure when it stopped working. We changed to new Cypress version few days ago.

After small debug session we have found out it does only occur on ui mode when running tests, as tests passes without issue on run mode. When we run test, and for example some test fails, then runner picks next... during this we get error like below. Test passes, and it's stuck on the next one.

Error

cypress_runner.js:161752  Uncaught TypeError: suite.tests is not iterable
    at findTestInSuite (cypress_runner.js:161752:28)
    at suiteHasTest (cypress_runner.js:161776:10)
    at Runner.<anonymous> (cypress_runner.js:162352:12)
    at Runner.emit (cypress_runner.js:146202:5)
    at next (cypress_runner.js:155477:10)
    at cypress_runner.js:155529:5
    at timeslice (cypress_runner.js:145764:27)

Desired behavior

Tests are seen properly and itarable.

Test code to reproduce

Can't do, simple cases doesn't work, tried to make reproductive case. Can't share codebase.

Only I can say that tests are nested properly and all brackets are open/closed in hierarchy.

Cypress Version

13.2.0

Node version

v18.11.0

Operating System

macOS 13.5.1

Debug Logs

No response

Other

No response

@nagash77
Copy link
Contributor

Hi @403-html In order to give our engineers the best chance at recreating your problem, please create a reproducible example using a fork of Cypress Test Tiny. This gives us the best chance of seeing exactly what you are seeing and being able to investigate effectively.

@jennifer-shehane
Copy link
Member

Right now there doesn't seem to be enough information to reproduce the problem on our end. We'll have to close this issue until we can reproduce it. This does not mean that your issue is not happening - it just means that we do not have a path to move forward.

Please comment in this issue with a reproducible example and we will consider reopening the issue. Here are some tips for providing a Short, Self Contained, Correct, Example and our own Troubleshooting Cypress guide.

@jennifer-shehane jennifer-shehane added stage: needs information Not enough info to reproduce the issue and removed stage: needs information Not enough info to reproduce the issue labels Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants