Subscribe by Email

Tuesday, October 16, 2012

How Silk Test records user actions?

Software systems or applications as we all know are composed of a GUI or graphical user interface objects such as those mentioned below:
  1. Windows
  2. Menus
  3. Buttons and so on.
These GUI objects can be manipulated by the user via a mouse or a key board for initiating the operations on an application.
These GUI objects are interpreted by the silk test and are recognized in to different categories based up on the following aspects that uniquely identify them:
  1. Class
  2. Properties and
  3. Methods
While the testing is in progress, an interaction takes place among the silk test and the GUI objects so that the operations can be submitted to the application under testing or AUT automatically without much efforts and also because the actions of a user can be simulated. 
This is also done to verify the results of each and every operation. The silk test is said to be the simulated user which is then said to drive the application under test or AUT. 

The silk test comes with two distinct components namely:
  1. The silk test host software
  2. The silk test agent software
- The first component of the silk test i.e., the silk test host software is used for developing, editing, compiling, running and debugging of the test plans as well as the test scripts. 
- The machine on which this component is installed is called the host machine. - The latter component of the silk test i.e., the silk test agent is the one that interacts with the graphical user interface of the application under test. 
- The commands present in the 4test scripts of the application are translated in to GUI specific commands which help in driving and monitoring the application under test.
- It is possible to run the agent locally on the same machine on which the host is already running or else it can be run in a networked environment. 
- But in this case, the machine will be known as the remote machine. 

How the user actions are recorded by the silk test?

- A repository is created for storing the information regarding the application under test or AUT before the test scripts are created and executed. 
- This repository consists of the descriptions of the GUI objects that are responsible for compromising with your application under test. 
- The silk test associates with these objects by means of two things namely:
  1. Object properties and
  2. Object methods
- Using these two aspects the actions performed on the objects can be easily recognized by the silk test and can be intelligently recorded in to the test script using the 4test language. 

Below we are giving some examples of what is recorded by the silk test for some user actions:
-User action
  As recorded by the silk test
-Selection of a radio button from a group
-Setting the main window as active
  Set Active
-Closing a dialog box
-Selecting an item from a list box
-Scrolling the scroll bar to the maximum position possible
  Scroll to max
-Writing text in a text field
  Set text
-Checking a check box
-Picking a menu item
-Unchecking a check box

- A property is that characteristic of an object that can be accessed directly and may be common among some classes. 
- On the other hand, the methods constitute of the user actions and are particular to an object. 
- Methods that are particular to an object are inherited from the parent class of the object. 
- Methods are unique to the objects of a class. 

No comments:

Facebook activity