Percy is designed to integrate with your tests and CI environment. To enable Percy, the token environment variable must be configured in your CI service:
`
PERCY_TOKEN
`: The Percy repo write-only API token. This is unique for each Percy repository.
# Drone project setup
Drone provides an easy way to set environment variables in the `.drone.yml
` config:
<http://readme.drone.io/usage/build_test/#environment:fb92aa3346185c57f15afda861d465a3>
In your `.drone.yml
`, add a section for environment variables and set `PERCY_TOKEN
` to the write-only token from your Percy repo. This token can be found in each Percy repo's settings.
**IMPORTANT: Keep your Percy token secret.** Anyone with access to your token can consume your account quota, though they cannot read data.
If your code is public, do not commit the PERCY_TOKEN to your code.
# Next step: integrate with tests
You're done with setup---the last step is to integrate Percy into your tests and run them. Just choose your client library:
JavaScript
[Ember](🔗)
[React](🔗)
[Storybook for React](🔗)
[Storybook for Angular](🔗)
[Storybook for Vue.js](🔗)
[Storybook for Ember](🔗)
[Cypress](🔗)
[WebdriverIO](🔗)<sup>beta</sup>
[Puppeteer](🔗)<sup>beta</sup>
[Nightmare.js](🔗)<sup>beta</sup>
[Protractor](🔗)<sup>beta</sup>
Ruby
[Rails](🔗)
[Other](🔗)
[Capybara, no tests](🔗)
[Best practices](🔗)
Python
[Selenium](🔗)
Static sites
[Command-line client](🔗)
Everything else
[Percy Anywhere](🔗)