> For the complete documentation index, see [llms.txt](https://www.isaacbowen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.isaacbowen.com/2025/08/21/testing.md).

# testing

I do a bunch of things, don't care if any of them work

the ones that do, in combination, tell me something about what may be going on

to save steps, I get my intuition involved alongside my scientist

I scry for patterns that I can test using novel tools - tools that would create results that either prove the fit (if not the fact) of the pattern

I build the tools, and try to break them

(I am always trying to break them)

new tools in hand, I do a bunch of new things I specifically couldn't do before, don't care if any of them work

etc

the result of this loop is a toolset that works pretty well. the result of this loop does *not* include knowledge of what's actually going on.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.isaacbowen.com/2025/08/21/testing.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.