# Run Cypress Tests without Connecting Repository

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 `Projects` and then `Add New Project`. Ignore `+ Add Repostory` since in this example we are not integrating with a repository. Be sure to select Cypress for `Testing Framework`. Give it a `Project Key` as a unique identifier for this project. The Project Key will be used to identify artifacts later.

![](/files/-MRLeVKbDE59fT5jTs8Y)

**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 Tests` and select the corresponding `Build` you created in the previous step.

![](/files/-MRLgxlzxb6V14AIN5zI)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testery.io/how-to/run-cypress-tests-without-connecting-repository.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.