Test Code Editor

The Test Code Editor in XJDeveloper allows viewing and development of XJEase test code without leaving the XJDeveloper environment. The editor uses standard windows keypresses for shortcuts, and the Edit and View menus have editor-specific options added to them when test code is being edited.

Syntax Highlighting

The editor supports syntax highlighting. XJEase keywords are shown in a different colour to make the code easier to read. The editor also supports "code folding" where blocks of code such as functions can be collapsed by clicking on the "-" symbol in the left margin, and expanded again by clicking "+".

Selected Word Highlighting

By default, the editor will highlight all occurrences in the file of the word under the caret, and will also highlight all occurrences of the currently selected text. This behaviour can be customised or disabled in the Options Dialog.

Function Definitions

At the bottom of each file is Go to Definition in File. This button will show all the functions defined in the file in a list. Clicking on a function name will move the cursor to the top of the function. You can also go to the definition of a function as well. Right-click on where a function is used (or press F12 when the cursor is on it). This will move the cursor to the top of that function - opening the file if required as well. Sometimes a function will be defined in multiple places, and so a small menu will be shown to allow you choose which definition to go to.

Finding All References

Right-clicking on a suitable XJEase variable or function (including those called by a CALL statement) will enable the Find All References menu item on the drop down menu. Alternatively, if the current position of the caret in the editor is over a suitable variable or function, then the Ctrl + F12 keyboard shortcut can also be used. After launching a reference search, the Find and Replace Dialog will open (or gain focus if it is already open) and display all locations of any references that are found. Making a subsequent search for references will replace the previous reference search results on the Find and Replace Dialog.

When finding references, all project files are searched in the state that they existed at the most recent compilation. Therefore it should be noted that making any changes to any document without saving may cause inaccuracies (compared to the contents of edited documents) in the results when finding all references. Saving a document after making edits will automatically trigger a recompilation, as will clicking the Recompile Code button under the Tools menu. If any errors are present after compilation, this may also result in inaccuracies in reference results. Furthermore, recompilation will not automatically update results displayed in the Find and Replace dialog.

Line Numbering

Line numbers help you to find problems quickly by referring to the error in the Errors Pane or in the output from XJRunner.

Line numbers do not start at line 1 in Device or Circuit code files, because the files will also contain information configured via XJDeveloper screens. This information goes at the top of the file, and code below it. Displaying the line numbers in this way ensures that they correspond to any errors reported from running the tests.

Keyboard Shortcuts

See Editor Keystrokes for a list of keystrokes recognised by the XJDeveloper editors.