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

🐛 Re-enable cypress --record on May 2019 #470

Closed
roschaefer opened this issue Apr 15, 2019 · 2 comments · Fixed by #807
Closed

🐛 Re-enable cypress --record on May 2019 #470

roschaefer opened this issue Apr 15, 2019 · 2 comments · Fixed by #807

Comments

@roschaefer
Copy link
Contributor

🐛 Bugreport

We exceeded Cypress free test recordings this month (<= 500 recordings).

0.61s$ docker-compose exec -d backend yarn run test:before:seeder
The command "docker-compose exec -d backend yarn run test:before:seeder" exited with 0.
16.10s$ yarn run cypress:run --record --key $CYPRESS_TOKEN
yarn run v1.15.2
$ cypress run --browser chromium --record --key d43d7a61-8561-4ac0-a742-18c817c7d16a
It looks like this is your first time using Cypress: 3.2.0
[15:33:34]  Verifying Cypress can run /home/travis/.cache/Cypress/3.2.0/Cypress [started]
[15:33:37]  Verifying Cypress can run /home/travis/.cache/Cypress/3.2.0/Cypress [completed]
Opening Cypress...
You've exceeded the limit of private test recordings under your free plan this month. The limit is 500 private test recordings.
To continue recording tests this month you must upgrade your account. Please visit your billing to upgrade to another billing plan.
https://on.cypress.io/dashboard/organizations/ae0b68ee-5e58-4d5b-84aa-11dd163542c4/billing
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The command "yarn run cypress:run --record --key $CYPRESS_TOKEN" exited with 1.
after_failure.1
0.19s$ wget https://raw.githubusercontent.com/DiscordHooks/travis-ci-discord-webhook/master/send.sh
--2019-04-15 15:33:49--  https://raw.githubusercontent.com/DiscordHooks/travis-ci-discord-webhook/master/send.sh
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.0.133, 151.101.64.133, 151.101.128.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.0.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2496 (2.4K) [text/plain]
Saving to: ‘send.sh’
     0K ..                                                    100% 20.4M=0s
2019-04-15 15:33:49 (20.4 MB/s) - ‘send.sh’ saved [2496/2496]
after_failure.2
0.00s$ chmod +x send.sh
after_failure.3
0.32s$ ./send.sh failure $WEBHOOK_URL
[Webhook]: Sending webhook to Discord...
fatal: bad object a6a8d91f94f9376e4f6d11e556a2309e0ab12998
fatal: bad object a6a8d91f94f9376e4f6d11e556a2309e0ab12998
fatal: bad object a6a8d91f94f9376e4f6d11e556a2309e0ab12998
fatal: bad object a6a8d91f94f9376e4f6d11e556a2309e0ab12998
######################################################################## 100.0%
[Webhook]: Successfully sent the webhook.
Done. Your build exited with 1.

Screenshot (79)

@ulfgebhardt
Copy link
Member

@roschaefer might be wise to recheck wether we do a recordin or not (master only? / PR only? -> what makes the most sense?)
Also please make a switch (like a variable or smth) to en/disable this functionality

@ulfgebhardt ulfgebhardt added this to To Do in Human-Connection via automation Apr 20, 2019
@ulfgebhardt ulfgebhardt changed the title Re-enable cypress --record on May 2019 🐛 Re-enable cypress --record on May 2019 Apr 20, 2019
@roschaefer
Copy link
Contributor Author

@ulfgebhardt agree! I would suggest to record cypress on master only.

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 roschaefer mentioned this issue Jun 12, 2019
1 task
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.
Human-Connection automation moved this from To Do to Done Jun 12, 2019
roschaefer added a commit that referenced this issue Jun 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

3 participants