eValid™ -- Automated Web Quality Solution Browser-Based, Client-Side, Functional Testing & Validation, Load & Performance Tuning, Page Timing, Website Analysis, and Rich Internet Application Monitoring.

Limits and Constraints
Certain limits and constraints apply during eV.Manager operation and use, as follows.

• Folder Structure
  There will be problems in eV.Manager operation if you don't have an existing Project\Group\*.evs file/folder structure available in which to capture your tests. eV.Manager uses the name of the Project folder as the project name and the name of the Group folder as the group name.

• File Name and Folder Name Character Set Constraints
  For technical reasons you cannot use either the # (number sign) character or - (hyphen) character or " " (blank) character in any project folder name, group folder name, or test script folder name.

  This limitation is imposed because these characters are reserved for internal use exclusively by the eV.Manager test execution engine. These characters have specific meaning to that engine.

  We recommend use of the _ (underscore) in place of the - (hyphen).

• File Name and Folder Name Length Constraints
  Filename lengths must be less than 32 characters, including the .evs extension. Although longer filenames are possible in Windows, and for eValid script files, eV.Manager either truncates or disregards long filenames.

  In addition to the above constraints, no eValid test name, Project name/folder, or Group name/folder may begin with a digit. For example 2test.evs will not work correctly, whereas T2test.evs will be OK.

• Variable Names and File Names May Not Match C-Language Keywords
  Filenames and variable names must not match any of the reserved C-language keywords such as assert, break, case continue do, double, else, exit, float, for, goto, if, int, long, return, short, return, signed, sizeof, static, struct,s witch, union, void, volatile, while etc. If you use such words the built-in C interpreter will likely cause errors for which the error messages may not be 100% clear. It is safest to avoid any variables that look like they might be taken as keywords as C.

  Unfortunately, eV.Manager behavior upon encountering such a keyword is not as polite as we would like. The generated intermediate ATS file will stop with the last non-offending test case, so in most cases it is the next one in the sequence that has the illegal test name.