-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Add relationships support to cypress. #14103
Labels
area: feature request 💡
$$ bug-bounty $$
https://www.jhipster.tech/bug-bounties/
theme: tests
$500
https://www.jhipster.tech/bug-bounties/
Milestone
Comments
mshima
added
area: feature request 💡
theme: tests
and removed
area: triage
theme: undefined
labels
Feb 28, 2021
5 tasks
Big +1 |
1 task
This issue is stale because it has been open 30 days with no activity. |
pascalgrimaud
added
$$ bug-bounty $$
https://www.jhipster.tech/bug-bounties/
$500
https://www.jhipster.tech/bug-bounties/
labels
Sep 25, 2021
Adding a bounty for this |
Let's do this. |
This was referenced Oct 2, 2021
This was referenced Oct 9, 2021
@mshima : approved |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area: feature request 💡
$$ bug-bounty $$
https://www.jhipster.tech/bug-bounties/
theme: tests
$500
https://www.jhipster.tech/bug-bounties/
Overview of the feature request
This is the only feature missing when comparing to protractor.
Protractor implementation selects last item from select and use it.
This is really easy to implement, but it doesn't follow best practices:
https://docs.cypress.io/guides/references/best-practices.html#Having-tests-rely-on-the-state-of-previous-tests
This approach causes problems like #13645.
To follow best practices I suggest the following approach:
Motivation for or Use Case
Related issues or PR
The text was updated successfully, but these errors were encountered: