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
🐛 Re-enable cypress --record on May 2019 #470
Comments
@roschaefer might be wise to recheck wether we do a recordin or not (master only? / PR only? -> what makes the most sense?) |
ulfgebhardt
changed the title
Re-enable cypress --record on May 2019
🐛 Re-enable cypress --record on May 2019
Apr 20, 2019
@ulfgebhardt agree! I would suggest to record |
datenbrei
modified the milestones:
🗳 Release: Migrate Alpha to Nitro,
🏃 Sprint: Manitou
Jun 12, 2019
roschaefer
added a commit
that referenced
this issue
Jun 12, 2019
Define env variables $BRANCH and $CYPRESS_RETRIES Source: https://graysonkoonce.com/getting-the-current-branch-name-during-a-pull-request-in-travis-ci/ ------ Cypress is looking for a env var by default. See: https://docs.cypress.io/guides/guides/command-line.html#cypress-run So I guess, all what we have to do is to give the env var another name. I also added a measure to avoid running out of quota: Disable recording if dependabot just updates dependencies.
roschaefer
added a commit
that referenced
this issue
Jun 12, 2019
Define env variables $BRANCH and $CYPRESS_RETRIES Source: https://graysonkoonce.com/getting-the-current-branch-name-during-a-pull-request-in-travis-ci/ ------ Cypress is looking for a env var by default. See: https://docs.cypress.io/guides/guides/command-line.html#cypress-run So I guess, all what we have to do is to give the env var another name. I also added a measure to avoid running out of quota: Disable recording if dependabot just updates dependencies.
This was referenced Oct 4, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🐛 Bugreport
We exceeded Cypress free test recordings this month (<= 500 recordings).
The text was updated successfully, but these errors were encountered: