> For the complete documentation index, see [llms.txt](https://sexytrees.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sexytrees.savimbo.com/practice-guide/iteration/what-is-a-b-testing.md).

# What is A/B testing?

We're big fans of field testing and continuous improvement

Academia has its value. For instance, much of the core work of solutions like Inga was done in proper academic structures by the Inga Foundation.&#x20;

But there is a still a lot of real-world regional questions to answer that may or may not be covered by the literature. This includes crops affected by climate change, economic structures, and intesections with climate credits.&#x20;

To the extent possible, we've documented the academic answers to questions we were able to answer, solutions like [adding rock phosphate](https://sexytrees.savimbo.com/practice-guide/inga-agroforestry/fertilizer-and-mulch.md) to depleted oils in Inga soil reclamation in the Andes. &#x20;

But some questions like direct seeding vs seedling cultivation are more site specific, and thats where A/B testing is essential.&#x20;

### A/B testing as continuous improvement

Academia isn't the only field that builds things or figires them out. Toyota uses continuous improvement, medicine uses randomized clinical trials, and high-tech uses A/B testing to refine things in faster cycles in the real world.&#x20;

### How to run an A/B test on a farm plot


---

# 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://sexytrees.savimbo.com/practice-guide/iteration/what-is-a-b-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.
