> For the complete documentation index, see [llms.txt](https://funtest-1.gitbook.io/funtest-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence.md).

# Creating Test Sequence

- [Test File Overview](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/test-file-overview.md): This section describes all the capabilities and functionalities of FunTEST's Test File
- [TEST Sequence Tab](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/test-file-overview/test-sequence-tab.md): This section will describe the TEST tab within a test file where a test sequence steps are defined
- [FunTest Commands](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/funtest-commands.md)
- [Operator Interface](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/funtest-commands/operator-interface.md): Following commands can be used to control the operator interface to display information to the operator or request action from the operator
- [Sequence Flow](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/funtest-commands/sequence-flow.md): Following commands allow you to control sequence flow
- [Digital I/O](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/funtest-commands/digital-i-o.md): This section describes how can you use digital I/Os in your test sequence
- [Test Result Export](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/funtest-commands/test-result-export.md): This section describes most common ways to create and export test reports
- [Printing](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/funtest-commands/printing.md): Use the command #print to print your test results automatically
- [Other Commands](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/funtest-commands/other-commands.md)
- [Calling Device Plugin](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/calling-device-plugin.md): This section describes how to call and use plugins in your test sequence
- [Test Point Control](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/test-point-control.md): This section explains how to control test points (switching system) to route test equipment to the device under test (DUT)
- [Using Spreadsheet Formulas](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/using-spreadsheet-formulas.md): This section describes how to take advantage of working in a spreadsheet editor while creating a test sequence
- [Variables](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/variables.md): This section describes how you can work with variable in a test sequence
- [Interrupt Events](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/interrupt-events.md)
- [Online Debugging](https://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence/online-debugging.md): Online Debugging is a power tool you can use when developing a test sequence


---

# 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://funtest-1.gitbook.io/funtest-documentation/creating-test-sequence.md?ask=<question>&goal=<endgoal>
```

`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.