# Test on a device

> Source: https://developers.specs.com/docs/hardware/test-on-a-device

Run your Lens on SPECS from Lens Studio as you build, then debug it live.

## Before you start

- A SPECS device signed in with your [SPECS account](https://accounts.specs.com/), set up with the [SPECS phone app](https://www.specs.com/download).
- **[Developer Mode](https://docs.lensstudio.com/get-started/connect-and-test/connect-lens-studio-to-specs?target=specs#before-you-connect)** turned on for the device.
- [Lens Studio](https://lensstudio.com/download) 5.25 or later with a SPECS project.

## Push a Lens

From Lens Studio, send the open project to your device. You can [connect to SPECS via Wi-Fi](https://docs.lensstudio.com/get-started/connect-and-test/connect-lens-studio-to-specs?target=specs).

For step-by-step instructions, see the [Lens Development docs](https://docs.lensstudio.com/get-started/connect-and-test/send-a-lens-to-specs?target=specs).

## Debug on device

To pause your scripts on breakpoints and inspect variables while the Lens runs on SPECS:

1. Select **Send to SPECS for Debugging**. A normal send uses optimized bytecode with no debug information, so a debugger can't attach to it.
2. Wait until the Logger shows **The sent Lens has successfully started on SPECS**. Attaching before then fails.
3. Attach the JavaScript debugger from VS Code, Cursor, or another VS Code fork.

You can't reload a Lens on SPECS while the debugger stays attached. To debug code that runs when the Lens starts, such as `onAwake`, debug it in the Lens Studio Preview panel instead. See the [Lens Development docs](https://docs.lensstudio.com/get-started/connect-and-test/send-a-lens-to-specs?target=specs#debug-your-lens-on-specs).

## Share with testers

To get a Lens onto other people's devices without a cable, publish it to **Organization only** or **Beta**. See [Release Channels](https://developers.specs.com/docs/publishing/release-channels).
