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

Fix logout flaky test #3965

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Fix logout flaky test #3965

wants to merge 3 commits into from

Conversation

ndricimrr
Copy link
Contributor

@ndricimrr ndricimrr commented Sep 30, 2024

Yet another attempt...

Seems like for some unexplicable reason the login function is not found.

So I removed it.

Check Test Video Recording here

Fixes #3884

Copy link
Contributor

@walmazacn walmazacn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems the linked failed test is based on older test definition and template:

it('Logout and login again', () => {
  cy.login('[email protected]', 'tets');

  //logout
  cy.get('[data-testid="luigi-topnav-profile"]').click();
  cy.contains('Sign Out').click();
  cy.get('[data-testid="logout-headline"]').should('contain', 'You have successfully logged out');
  cy.get('[data-testid="logout-message"]').should('contain', 'Sign in again to continue working on awesome things!');
  cy.expectPathToBe('/logout.html');

  //login again
  cy.contains('Re-Login').click();
  cy.expectPathToBe('/assets/auth-mock/login-mock.html', 5000);
  cy.get('body').should('contain', 'Login to Luigi sample app');
  cy.login('[email protected]', 'tets');
})

Compare it with the latest version of this test (5000ms timeout shouldn't be there):
https://github.com/SAP/luigi/blob/main/test/e2e-test-application/cypress/e2e/tests/1-angular/login-flow-nav-dropdown.cy.js#L69

That's why I'd wait until more tests run and then we can draw some conclusions

@ndricimrr
Copy link
Contributor Author

Yes. True. It seems like we need to wait until next version after "2.16.0" gets released, to see it.

@ndricimrr
Copy link
Contributor Author

wait for next release and reconsider this if still flaky

@walmazacn walmazacn self-assigned this Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Stuff like NFRs, CI pipeline
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Investigate backwads compatibility flaky test fail
3 participants