background image
<< Part III - Cross-Platform Testing | Porting Tests - Marking 4Test code as GUI-specific >>
Porting Tests to Other GUIs
<< Part III - Cross-Platform Testing | Porting Tests - Marking 4Test code as GUI-specific >>
User's Guide
265
13
C
h
a
p
t
e
r
1
3
Porting Tests to Other GUIs
Introduction
Using SilkTest, you can create portable testcases which will test your
application on any of the supported GUIs. The reason for this is that your
testcases use logical names, called identifiers, to refer to the GUI objects, and
not actual names, called tags. Therefore, if there are differences in the ported
application's appearance, you need only change the window declarations, not
the testcases themselves.
What you will learn
This chapter contains the following sections:
Marking 4Test code as GUI-specific
Introduction
The porting scenarios described in this chapter use 4Test keywords called
GUI specifiers to indicate that portions of include files or script files are
specific to a particular GUI. Before studying these scenarios, you should
understand which GUI specifiers are available and how to use them in your
include files and script files.
Topic
Page
Marking 4Test code as GUI-specific
265
Conditional compilation
269
Supporting GUI-specific executables
271
Supporting GUI-specific captions
272
Supporting GUI-specific menu hierarchies
273
Supporting extra controls
273
Supporting different implementations of the same control
274
Supporting differences in application behavior
277