Nigel can import your specifications file and generate LabVIEW and Python steps in your sequence. Nigel can also create code module stubs for LabVIEW and Python steps if they don't already exist.

Introduced in TestStand 2026 Q3

You must provide Nigel with your specification file to generate a sequence. You can provide this information using one of the following methods:
  • Attach the CSV or Excel specification file to your Nigel chat window
  • Provide the path to your specification file in your prompt
Your prompt must also specify if you want Nigel to generate code module stubs for the tests from your specifications. You can ask Nigel to generate LabVIEW or Python code modules, or you can specify a path to a folder containing existing code modules you want Nigel to use. Nigel can match existing code modules to your specifications based on the following code module metadata:
  • File names
  • Module descriptions
  • Input and output parameters
You can use the following example prompts as starting points for developing sequences using specification files.
Table 43. Example Specification Import Prompts
Prompt Notes
Make a sequence from the attached specification file. I want <Language> code modules. I do not have any, so you will have to create them in <Code Module Folder Path>.
  • Before entering this prompt, attach your specification file to the Nigel chat using the Add File to Context button.
  • While importing your specifications, Nigel generates code module stubs in LabVIEW or Python in the folder you specified.
Make a sequence from the CSV file located at <Specification File Path>. Use the <Language> code modules located at <Code Module Folder Path>.
  • While importing your specifications, Nigel uses code modules in the folder you specified.
If your specification file is in .csv format and doesn't meet the required file layout, Nigel can try to update the file to the correct layout. When trying to update a file layout, Nigel follows the following process:
  1. Nigel asks for permission to edit the file.
  2. Nigel tries to update the file layout.
  3. Nigel writes an edited copy of the file to the <TestStand Local Application Data> directory.
If Nigel can't correct the file layout after a few editing attempts, it lets you know that the file still requires edits and where the most updated file is located.