Overview of Object Files

Object files are the compiled versions of include (.inc) or script (.t) files. Object files are saved with an "o" at the end of the extension, for example, .ino, or .to. Object files cannot be edited; the only way to change compiled objects is to recompile the include or script file. When you save a script or include file, a source file and an object file are saved. Object files are not platform-specific; you can use them on all platforms that Silk Test Classic supports.

In order for Silk Test Classic to run a script or include file that is in source form, it must compile it, which can be time-consuming. Object files, on the other hand, are ready to run.

Note: You cannot call objects that exist in the object file (.to) from a test plan; you must have the script file (.t).

To disable saving object files during compilation, the AutoComplete options on the General Options dialog box as well as the Save object files during compilation option on the Runtime Options dialog box need to be unchecked.

Silk Test Classic always uses object files if they are available. When you open a script file or an include file, Silk Test Classic loads the corresponding object file as well, if there is one. If the object file is not older than the source file, Silk Test Classic does not recompile the source file. The script is ready to run. If the source file is more recent, Silk Test Classic recompiles the source file before the script is run. If you then later save the source file, Silk Test Classic automatically saves a new object file.

If a file is loaded during compilation, that is, if you include a file in another file that is being compiled, Silk Test Classic loads only the object file, if it exists and is newer than the corresponding source file.

Object files may not be backward-compatible, although sometimes they will be. Specifically, object files will not work with versions of Silk Test Classic for which the list of GUI/browser types is different than for the version used to compile the object file. The list is in 4Test.inc. For example, object files created before 'mswxp' was added as the GUI type for Windows XP cannot be used with ST5.5 SP3, which includes the 'mswxp' GUI type.

If you are using a .ino file, but during compilation Silk Test Classic displays a message that the corresponding .inc file is missing, then you may be experiencing the object file version incompatibility explained in the preceding paragraph.