> For the complete documentation index, see [llms.txt](https://docs.revrobotics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revrobotics.com/rev-professional-development-technical-path/first-time-programming/testbed.md).
# What is a Testbed?
{% hint style="info" %}
This section is intended to pair with Unit 1, Lesson 4 of the Intro to Robotics V2 curriculum.
{% endhint %}
A **testbed** is a testing environment for hardware and software components. Testbeds are a fantastic tool to practice programming, troubleshoot parts, collect data, and continue to grow familiar with the EDU Kit V2.
Similar setups are used by professional engineers and companies as part of the development, quality control, and refinement processes! Depending on the end goal, these testbeds can be designed a variety of different ways. For example, if a company is gathering data on how much weight a part can handle, the testbed may be designed to continually move over a period of time while adding new amounts of weight.
## In the Classroom:
Let's take a look at the testbed used within Unit 1 of the curriculum:
The goals of our testbed are:
* Provide a base frame that can be reused
* Allow mounting of 3 different kinds of actuators
* Demonstrate using actuator brackets for the different kinds of actuators
* Safely secure moving parts while creating our first OpMode
* Create an easy to move platform for organizing and storing student projects outside of class
This testbed can additionally be used for testing new actuators, Control Hubs, batteries, or sensors upon receiving them. **This is a recommended best practice even if they may not be used yet!**
### Building the Testbed
{% file src="/files/KJuYGPkAC1MwQCc9M652" %}
Completing the Testbed build takes 20-30 minutes.
---
# 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.revrobotics.com/rev-professional-development-technical-path/first-time-programming/testbed.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.