Common questions and setup issues
This is a collection of most common questions associated with Sorry Cypress setup
Yes! In orther to use a private S3 bucket with sorry-cypress, you need to create a bucket with the following:
- 2.Public Access Block should be:
block_public_acls = false
block_public_policy = true
ignore_public_acls = false
restrict_public_buckets = true
- 1.A bucket resource policy making it private. You can restrict bucket access based on the source IP, or only from sources in your private VPC, for example.
Please refer to the following scheme for reference.
- 1.Upload flow: Cypress runner reports its results to director service
- 3.Director service sends back the signed S3 upload URL, stores the read URL in a DB
- 4.Cypress runner uses the signed upload URL to upload the screenshots / videos
- 5.Read flow: a browser reads the test results and uses the read URL from a DB
- 6.AWS S3 returns the content to the browser
Cypress AWS S3 upload / read flow
Most chances something is wrong with your setup or the way you're connecting to sorry-cypress. Try following the next steps for troubleshooting before submitting support requests.
- Make sure Sorry Cypress services are up and running
- Director service is reachable, is connected to the right DB and it logs the requests
- API service is reachable and is connected to the right DB and it logs the requests
- Dashboard loads with empty results
- Ensure you're reconfiguring cypress to use Director's service URL.
- Run cypress in debug mode
DEBUG=cypress:server:*to see the details of network requests - the debug mode works both when running
- Examine Director service log files to see the incoming requests
- Examine the logs files
- Run cypress runner in debug mode -
DEBUG=cypress:server:* cypress run ...
- Examine sorry-cypress log files and identify the requests / responses that are not working as expected