-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Copy how cypress is run on the server #1622
Conversation
4964377
to
1386f76
Compare
Signed-off-by: Louis Chemineau <louis@chmn.me>
1386f76
to
e66d96d
Compare
selectMedia([1, 2]) | ||
downloadSelection() | ||
unselectMedia([1, 2]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason not to make those cypress commands?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mostly typings. Is there a reason to make them cypress commands ? I thought commands were the way to go, but it does not add anything in my experience.
Sorry but I could onky give a 🐘 on this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests are passing 🎉 🐘
/backport to stable25 |
The backport to stable25 failed. Please do this backport manually. # Switch to the target branch and update it
git checkout stable25
git pull origin stable25
# Create the new backport branch
git checkout -b fix/foo-stable25
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25 More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport |
This make e2e experience nicer and the code cleaner
This also takes advantages of sessions, so tests should run faster. Confirmed, tests ran in 3:48 min, where average for this repo was 6:04 min