-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Before each SocialAuth Issue #27919
Comments
Can you provide a reproducible example? Here are some tips for providing a Short, Self Contained, Correct, Example and our own Troubleshooting Cypress guide. If not, we'll have to close the issue. |
Hi Jennifer. Sorry for thr late reply. |
@mohdbilal2000 Without an example we can run, we won't be able to investigate. |
I have tried automating Linkedin using cypress but as you may know it opens a guest window of it's own for browsing, and wheneven I tries to re run the tests after few tests it will show that i cant login cause i have logged in multiple times in few minutes. I tried using session and before each but neither of them worked for me. If you have any other approach, please do let me know |
This issue has not had any activity in 180 days. Cypress evolves quickly and the reported behavior should be tested on the latest version of Cypress to verify the behavior is still occurring. It will be closed in 14 days if no updates are provided. |
This issue has been closed due to inactivity. |
What would you like?
I tried before each login by using session and global variable to automate Linkedin using cypress for some flows for better learning of cypress, and wrote script for the same but unfortunately when the test re runs after updating something on the script after few re runs it again shows me login limit reached, if anyone tries this and find a solution so that the login credentials that are saved in before each method do not repeat itself and makes the testing smooth.
Why is this needed?
For better testing on the social web applications
For learning cypress
The text was updated successfully, but these errors were encountered: