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

Heisenbug in group-proposals.spec.js #2257

Closed
taoeffect opened this issue Jul 26, 2024 · 3 comments
Closed

Heisenbug in group-proposals.spec.js #2257

taoeffect opened this issue Jul 26, 2024 · 3 comments

Comments

@taoeffect
Copy link
Member

taoeffect commented Jul 26, 2024

Problem

This is a heisenbug that happens on my machine:

group-proposals.spec.js.mp4
    1) proposal-based invitation link has 7 days of expiry

  14 passing (1m)
  1 failing

  1) Proposals - Add members
       proposal-based invitation link has 7 days of expiry:
     AssertionError: Timed out retrying after 30000ms: Expected to find element: `.c-title-wrapper select`, but never found i

I "fixed" this in this PR by using { bypassUI: true } here:

  it(`proposal-based invitation link has ${groupInviteLinkExpiry.proposal} days of expiry`, () => {
    // Expiry check in Group Settings page and Dashboard
    cy.giLogin(`user1-${userId}`, { bypassUI: true })

However, this test should pass with { bypassUI: false } too. In fact, it doesn't make any sense what's going on here, because in the video you can see it's as if user1 is joining the group for the first time when they're logging in, but they've already joined the group long before this!

So something serious is going wrong here.

Solution

See if you can get the test to fail on your local machine. Remove , { bypassUI: true } from that line there and run the tests locally with grunt dev and npx cypress run -c 'baseUrl=http://localhost:8000' --spec "test/cypress/integration/group-proposals.spec.js" (or just plain grunt test, which was how I was running it when I got the heisenbug).

Then identify the problem and fix it.

@taoeffect
Copy link
Member Author

Actually, I'm not sure about this one... it seems to be on #2248 mainly...

@taoeffect
Copy link
Member Author

taoeffect commented Jul 26, 2024

Updated the issue to indicate that this is still a real issue even though it's been worked around for now.

@taoeffect
Copy link
Member Author

Might've been fixed by @corrideat in #2294

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant