# Testing a dev builds of the Extension ### Developer builds Often when the wallet developers have finished building a new feature or bugfix they will create a new version of the Chrome extension so it can be tested before releasing it to the public. Users are welcome to test these versions with us and in some cases it provides an opportunity to try new features and benefit from bug fixes before they are released. ### Step by step to test a dev build 1. Find the Pull request on github with the feature or fix: for example [3577](https://github.com/leather-wallet/extension/pull/3577) 2. Download the extension build:\ Click the extension builds link in the PR: ![](/files/OGFms6n7qmwlaDPVkqhG)\ Then scroll down and click "stacks-wallet-chromium" under Artifacts: \ ![](/files/IYNoLq2k9tIvIiprYkj9) 3. Unzip the extension build (currently needed twice). 4. Go to extension management on Chrome: chrome://extensions. 5. Turn off your current wallet extension.\ ![](/files/GOUtIXKIDjEJCi8YcNFp) 6. Switch to developer mode (upper right corner).\ ![](/files/2GKqanZ54NYjGygKssgQ) 7. Click Load unpacked (upper left corner).\ ![](/files/VxxbQalB1DNDJX0zV0bG) 8. Select folder with the unzipped wallet extension. 9. Then Restore the wallet with an existing Secret Key or make a new wallet for testing, this will depend on the functionality you aim to test. 10. Test the new feature or fix and share your experience in the pull request topic on Github where this developer version of the wallet was shared. --- # 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://leather.gitbook.io/guides/testing/testing-a-dev-builds-of-the-extension.md?ask= ``` 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.