--- title: "SDK test" slug: "sdk-test" updated: 2025-05-09T17:57:06Z published: 2025-05-09T17:57:06Z canonical: "support.tulip.co/sdk-test" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.tulip.co/llms.txt > Use this file to discover all available pages before exploring further. # SDK test *Learn how to test your newly built Edge Driver* ### Introduction 1. What you will learn 1. How to test an edge driver project 2. What you will need (pre-requisites) 1. A ready-to-run Edge Driver - check out [SDK Develop](/r230/docs/sdk-develop) and [SDK Create](/r230/docs/sdk-create) first if you haven't already. ### Testing your Driver in Tulip Player Warning This is available in Player 2.8.0. By default, Tulip Player runs with built-in drivers that work out of the box. However, you can also run your custom driver locally in Tulip Player, even without a Tulip instance. To do this, you can launch Player from the command line with the path to your driver's dist directory. Download and install **Tulip Player** from [here](https://download.tulip.co/). On Windows, this is done by using the `set` command in the terminal to set the `TULIP_PLAYER_CUSTOM_DRIVERS_PATH` environment variable, then running the "Tulip Player.exe" from the same terminal: ``` C:\Users\Bob> set "TULIP_PLAYER_CUSTOM_DRIVERS_PATH=C:\Users\Bob\Documents\esp32-diy-sensor\dist" C:\Users\Bob> "C:\Users\Bob\AppData\Local\tulip-player-desktop\Tulip Player.exe" ``` Once player starts, open **Browser Developer Tools** in the Player app and go to the Console tab. ![SDK](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-03-27%20at%2011.12.26%20AM.png) You can fire events (which sends commands to the device). Then, add .run() at the end to have it run for a certain number of times. ![Screenshot 2025-05-09 at 1.45.38 PM.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-05-09%20at%201.45.38%20PM.png) If the events are successful, you'll see them populate in the developer console. ![Screenshot 2025-05-09 at 1.46.17 PM.png](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-05-09%20at%201.46.17%20PM.png) Filter messages with "[CED]" to see your driver logs. ![SDK](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/Screenshot%202025-03-27%20at%2011.12.30%20AM.png) If successful, you should see "data" events logging temperature and humidity values in real time.