> For the complete documentation index, see [llms.txt](https://docs.fireapis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fireapis.com/the-basics/tables/testing-tables.md).
# Testing Tables
Once you've created a table and migrated it, you can test operations such as creating, updating, deleting and listing records from the specified table
Here's how you can test your tables:
1. Click the table you want to test.
Location of test in table.
2. You will see the **Test** button in the table view (refer to the image above). Click the **Test** button to open the test UI popup.
Test User Interface
3. Refer to the image above, where you can test different endpoints that are pre-created by Fireapis. In the example above, we used the **POST** endpoint, which adds a new record to your database based on the input you provide.
After test result
4. In the image above, you can see the response from the **POST** API call. You can find more information about the test user interface here.
{% hint style="info" %}
In **POST** API call, you **don't need** to pass the ID (which is the primary column type), as Fireapis automatically assigns the primary key as a **unique value by default.** [Learn more about different endpoints in Fireapis.](/the-basics/tables/endpoints.md)
{% endhint %}
---
# 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.fireapis.com/the-basics/tables/testing-tables.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.