Run Cypress Tests without Connecting Repository
A step-by-step guide to running Cypress tests on the Testery platform when integration with GitHub / Bitbucket isn't an option.
For some organizations, integrating with GitHub or Bitbucket is not an option. While you'll be missing out on some pretty cool functionality, don't fret. You can still benefit from the other great features Testery has to offer.
Create a Project but don't select a repository. Select
Add New Project. Ignore
+ Add Repostorysince in this example we are not integrating with a repository. Be sure to select Cypress for
Testing Framework. Give it a
Project Keyas a unique identifier for this project. The Project Key will be used to identify artifacts later.
Configure your build server to manually upload the test artifacts. Instead of having Testery automatically fetch the artifacts from the repository, we will have the build server upload them.
token- Your API token. To retrieve your token, click Settings → Integrations → Show API Token and copy the token that is displayed.
project-key- The key you specified above when creating the project.
build-id- The build id from your CI/CD, usually found in an environment variable. This will be used to pull the correct artifacts when starting a test run.
path- The folder containing the tests. This path should include the entire cypress folder. You will need to upload everything your root cypress project folder except the node modules. You can upload the node modules but Testery will delete them as we resolve your node modules for you. It can also take your upload a LOT longer with the node modules in it.
testery upload-build-artifacts --token <token> --project-key <project-key> --build-id <build-id> --path <path> --zip-dir
Create a test run. Now you can test it out by creating a test run the way you normally would. You can do this manually, from the CLI, or from the API. To create a test run manually, select Test Runs -> New Test Run. Be sure to select the project defined above for
Project With Testsand select the corresponding
Buildyou created in the previous step.