When our new billing portal is deployed, there will be warnings/errors when recording tests if limits reached. This will never affect test runs where the --record flag is omitted.
step 1
step 2
After doing warnings, extend handle 402 errors from the API which will have errors
Parallel runs TBD
This logic is similar to the custom errors here
only now we need to handle even successful 200 response, because it will have warnings list attached postRunResponse@2.1.0. The error codes are listed for now here: https://github.com/cypress-io/cypress-api/wiki/Errors#warnings-when-creating-a-run-build
When our new billing portal is deployed, there will be warnings/errors when recording tests if limits reached. This will never affect test runs where the
--recordflag is omitted.step 1
FREE_PLAN_IN_GRACE_PERIOD_EXCEEDS_MONTHLY_PRIVATE_TESTSFREE_PLAN_EXCEEDS_MONTHLY_PRIVATE_TESTSstep 2
After doing warnings, extend handle 402 errors from the API which will have errors
Parallel runs TBD
This logic is similar to the custom errors here
cypress/packages/server/lib/modes/record.coffee
Line 293 in b656c67
only now we need to handle even successful 200 response, because it will have
warningslist attached postRunResponse@2.1.0. The error codes are listed for now here: https://github.com/cypress-io/cypress-api/wiki/Errors#warnings-when-creating-a-run-build