<< Lesson 4 Capturing Your Application | Test frames for Web applications >>

What is Captured in the Test Frame?

<< Lesson 4 Capturing Your Application | Test frames for Web applications >>

Getting Started: A Tutorial

4 C

APTURING

OUR

PPLICATION

The Test Frame

The Test Frame

Before you begin recording testcases, SilkTest needs to learn some things
about your application. This is done by capturing, in a test frame, the data
structures that will support your testcases. The test frame is an include file
(.inc) that acts as a repository of information about the AUT, storing window
declarations, constants and variables. SilkTest references this test frame when
recording and running testcases. For more information about how SilkTest
references test frames see

Chapter 2, "Preparing to Use this Tutorial"

Building a test frame

You build a test frame in two stages, by

First, recording the window declaration for the main window.

Next, bringing up each of the application windows/dialogs one at a time
and recording its declarations.

The first stage automatically takes place when you create the <test
frame>.inc itself. Once the test frame has been created, you then add the
window declarations for the other windows/dialogs in your application.

What is Captured in the Test Frame?

The information captured for a Web application is different from that
captured for a client/server application. If you are testing the Web application
read "Test frames for Web applications" below. If you are testing the client/
server application proceed to

"Test frames for client/server applications" on

page 74