> For the complete documentation index, see [llms.txt](https://docs.amltd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amltd.com/dc-works/getting-started/test-your-applet.md).
# Test Your Applet
After creating and reviewing the **Asset Check-In** Applet, test it from the Applet Designer to confirm that it can create, display, and update records.
{% hint style="warning" %}
A test run uses the Applet’s actual connected database table. Any records created, changed, or deleted during testing affect live table data.
{% endhint %}
### Save the Applet
Before beginning the test:
1. Select the **Save** icon in the upper-right corner of the Applet Designer.
2. Confirm that the Applet’s revision number has advanced.
Changes made in the Applet Designer are not saved automatically. Save again whenever you want a new test run to include your latest changes.
### Start a test run
Select the **play** button in the upper-right corner of the Applet Designer.
*Select the play button to launch a test run.*
The Applet opens in a separate browser tab. This allows you to test it while keeping the Applet Designer open in its original tab.
{% hint style="info" %}
The test run displays the Applet as a user would see it, but it has not yet been published or deployed to Web Users or Device Users.
{% endhint %}
### Enter a sample record
On the **Data Capture Page**, enter the following sample information:
| Field | Sample value |
| -------------------------- | ----------------------- |
| **Asset ID** | `TEST-001` |
| **Employee or Location** | `Receiving` |
| **Check-In Date and Time** | Current date and time |
| **Condition** | `Good` |
| **Notes** | `Initial tutorial test` |
*Enter sample information to test the Applet’s data-capture workflow.*
Complete the final input to run the generated **Input Action**. The action adds the information held in **New Item** to the connected **Asset Check-In** table.
The newly created record appears in the table on the Data Capture Page.
*The new record appears in the Applet after it is added to the table.*
### View the saved record
Select **View** to open the **Data View Page**.
When this page opens, its Page Load Actions retrieve the existing table records and display them in the table.
*The Data View Page displays the record stored in the connected table.*
Select the `TEST-001` row. The selected row is highlighted, and its information is loaded into **Current Item**.
### Open the record for editing
With the record selected, select **Edit**.
The **Data Edit Page** opens and displays the selected record’s information.
*The selected record is loaded into the Data Edit Page.*
### Update the record
Change **Condition** from:
`Good`
to:
`Needs Repair`
Select **Update**.
The Update button writes the modified values from **Current Item** back to the corresponding record in the connected table.
{% hint style="info" %}
The Update action changes the existing record. It does not create another record.
{% endhint %}
Return to the **Data View Page** and confirm that the Condition value now displays **Needs Repair**.
*The updated value appears when the record is viewed again.*
### Confirm the data in the Designer
You can verify the result directly in the underlying table:
1. Return to the DC Works Designer.
2. Select **Data**.
3. Open the **Getting Started** database.
4. Open the **Asset Check-In** table.
5. Locate the record with Asset ID `TEST-001`.
6. Confirm that **Condition** is set to `Needs Repair`.
*The database table contains the information created and updated during the test.*
This confirms the complete data workflow:
1. The Data Capture Page creates the record.
2. The Data View Page retrieves and displays it.
3. The Data Edit Page loads the selected record.
4. The Update action writes the modified information back to the table.
### Return to the Applet Designer
Close the test-run browser tab or return to the browser tab containing the Applet Designer.
Testing does not publish the Applet or make it available to users. You can continue editing it, save another revision, and launch additional test runs as needed.
### Troubleshooting
If the Applet does not behave as expected, check the following:
* Save the Applet before starting another test.
* Confirm that every input is bound to the intended field in **New Item**.
* Confirm that the final input contains the action that adds New Item to the table.
* Select a row before selecting **Edit**.
* Confirm that the selected row is loaded into **Current Item**.
* Confirm that the Update button updates Current Item in the connected table.
* Reopen the Data View Page if its displayed records need to be refreshed.
### Next step
The Asset Check-In Applet can now create, display, and update records successfully. The next logical guide should cover **Publish Your Applet**, followed by adding the Applet to a **Suite** and making it available to Web Users or Device Users.
---
# 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.amltd.com/dc-works/getting-started/test-your-applet.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.