Cycle Testing for Visual Studio Code

Welcome to Cycle Testing for Visual Studio Code! This extension provides support for the CycleScript language.

Features

Basic Features (Cycle not required)

• Syntax highlighting
• Comment toggling
• Snippets

Advanced Features (requires Cycle)

Advanced features are provided by a CycleScript language server through the Cycle application. These features include:

• Syntax Errors and Warnings
• Autosuggest for Steps, Keywords, and more
• Step documentation on Hover

Installation

Cycle Installation Path Setting

VS Code needs to know where to find Cycle to enable the advanced extension features. The extension provides a setting to specify Cycle's installation directory.

By default, Cycle is installed at C:/Program Files (x86)/CycleLabs/Cycle, and the extension setting is defaulted to that value. If you are using Cycle installed in the default location, the extension will work correctly without any additional configuration.

If Cycle is not installed in the default location, you will need to change this setting to point to the directory where Cycle is installed.

When you change the installation path setting, you will need to restart the CycleScript language server. The extension provides a command named Cycle: Restart Language Server which is available through the command palette. You can access the command palette through the View -> Command Palette... menu item or by using the keyboard shortcut Ctrl+Shift+P. Once the command palette is open, you can search for the command by typing Cycle in the search field.

Authentication

The advanced features of the extension require an active subscription to Cycle. You must authenticate through Cycle first to enable the Cycle VS Code Extension to run the CycleScript language server.

Language Server Errors

When attempting to restart the language server, you may hit the following error:

Error: spawn EPERM

If this happens, it is most likely due to permissions. Make sure that there are no permissions blocking VS Code from interacting with the Cycle directory or preventing the language server from starting. You may need to check with your InfoSec team.