Classic vs. Visual 4Test

Segue's 4Test editor supports two views of test script source code - classic or "Visual 4Test". This is controlled by checking the 'Visual 4Test" menu item on the Edit menu seen when a .t or .inc file is open for editing.

The 4Test editor remembers the last setting you pick. From then on, as you open each file, it will modify the contents of the file to the current setting. Perhaps the major reason that the change in view requires a change in the file is because the Visual 4Test view supports collapsing nested blocks of the test script from view. The collapsed or expanded state of these statement blocks is also recorded in the file. Some find this ability to hide currently uninteresting blocks of code from view to be the most powerful reason to use the Visual 4Test view.

Another benefit of the Visual 4Test view is color syntax highlighting. You can adjust the colors to your needs thru the Options menu.

Problem - If you are tracking changes to your Visual 4Test format files, changes in the collapsed/expanded states appear as source code changes.
Solution - Have your team agree to collapse all statement blocks before saving each new version.

Problem - The conversion from one form to the other and back does not always produce what you started with. For example, during the conversion from classic to Visual 4Test, in-line comments (those that start with /* and end with */ )are are merged within a single // style comment. There are some situations where comments on the end of a line will appear as a separate comment on the next line.
Solution - Be aware of this problem. It is recommended that your group decide which view they prefer, and have everyone stick with that. An alternate approach is to ban the use of in-line comments.

Problem - Visual 4Test format files can be corrupted by using other editors. Some editors automatically modify leading tab characters to spaces, for one. If these tab characters are changed, the logic of the test script can be altered or the 4Test editor may not be able to open it or run it.
Solution - If your group must use a different editor at times, stick with the classic format.