> For the complete documentation index, see [llms.txt](https://docs.thousandeyes.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/development-guide.md). # Transaction Test Development Guide Eventually, you'll need to start tweaking your ThousandEyes transaction test scripts. Where do you start? Follow these steps to gain proficiency and create more robust and efficient transaction test scripts. * [Working with Web Development Tools](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/getting-started/working-with-web-development-tools) - The first step is to familiarize yourself with standard web development tools such as Chrome’s built-in developer tools. Similar tools are available in other web browsers. In addition to learning how to read a waterfall chart, you can also use browser developer tools to try out custom JavaScript code, analyze details of web applications that you’re looking to monitor using ThousandEyes, and examine HTML page elements that you’d like to reference in your transaction test scripts. * [Optimizing and Troubleshooting Transaction Scripts](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/development-guide/robust-transaction-scripts/optimizing-transaction-scripts) - This page introduces a few basic scripting optimizations, some of which are also important for troubleshooting during script development. * [Transaction Scripting Tips and Tricks](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/development-guide/robust-transaction-scripts/transaction-scripting-tips) - This page presents more nuanced guidance, about things to consider when there are several possible ways to do something. * [Executing custom JavaScript code](https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/development-guide/transactions-executing-custom-javascript-code) - There are times when a piece of JavaScript code works in the developer console but won’t work in a transaction test. This page outlines the differences between two main JavaScript code execution contexts, and how they work with the ThousandEyes BrowserBot, which is the component within the ThousandEyes cloud and enterprise agents that executes the transaction test. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.thousandeyes.com/product-documentation/browser-synthetics/transaction-tests/development-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.