# Test
Test entries should contain try and contain the items noted in the rubric such as recording the key steps to test the solution and any test results.
As previously noted in the ‘understanding the test solution section’ there are a few items we have looked at to be included in these types of entries.
**Procedure**
What tactic was used to perform the test? Were there specific steps used to ensure the robot performed as expected?
**Results**
What results were achieved and were they expected or not?
**Analysis**
Do the results reflect the intended outcome? If not, what does the team think needs to be done in order to achieve the expected outcome.
The below example pages demonstrate data that was collected during a team meeting/practice and analysis of the cumulative data over a period of time to review how the drivers performance, and thus the robot, was doing. This is just one aspect of how testing could be notated in the notebook.
*Paired Test Entries*
Below are a couple additional examples of testing entries that give some explanation with associated data.
|  |  |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
---
# 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://iiwii-robotics.gitbook.io/engineering-notebook/vex-engineering-notebooks/parts-of-a-notebook-sections/notebook-entries/edp-entries/test.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.