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	select
-Setting the main window as active	Set Active
-Closing a dialog box	close
-Selecting an item from a list box	Select
-Scrolling the scroll bar to the maximum position possible	Scroll to max
-Writing text in a text field	Set text
-Checking a check box	Check
-Picking a menu item	pick
-Unchecking a check box	uncheck

- 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. 

How will you call from one action to another action in QTP?

In the test scripts produced with the help of quick test professional, one action can be called from another action. In this article we are going to discuss the same i.e., how this can be done? 

How to call from one action to another action?

- A call to a reusable action can be inserted easily that might be stored in some local test (current test) or in some external test (external test). 

- Calling one action from some other action is just like inserting an action call in an existing action or just linking it to it.

- The steps involved in this whole process can be viewed using the action view tool but they cannot be modified. 

- The local object repository of the action that has been called is read only. 

- It is not necessary that each and every calling and called action must have a local object repository. 

- It may or may not have a repository.

- If the external action that has been called has some data in the data table, you get two options:

1. Either you take the data from the data sheet of the action and import it as a editable or local copy,
2. Or you take the data from the original action but here the data is read only type.

- The data obtained from the global data sheet of the action that has been called is imported to the test as an editable and local copy of data.

- In order to modify an existing external action you need to open the particular test where you have the action stored and make modifications there itself. 

- These modifications will be visible in all the tests that will call that particular function. 

- If you choose to go for the second option as mentioned above then the changes that you will make will apply to original data as well. 

Step by step procedure of how a call to an action can be inserted?

1. Go to insert menu, the select the “call to existing action” option and you will be provided with a list of actions. From that select “insert call to existing action” or you can also right click on any of the steps. The go for the action button and then click on “insert call to existing” option. Now a action properties dialog box pops up.
2. There is a browse button called “from test” and can be used to find the test that holds the action to be called. All the reusable actions in the test that you select are displayed in this action box.
3. From the action that is displayed select the action that is to be called and its type as well as description both are displayed if available. This type and description help you further in proper identification of the action that you wish to be called.  You can even set other properties of the actions by going to the “setting general action properties”.
4. Now you are done with setting the properties, decide on where the function has to be inserted. For inserting the function you are provided with two options namely:

a)   After the current step or

b)   At the end of the test

There is one thing to be noted which is that if the step that is in current selection is a reusable action from some another test, then the action call is added at the end of the test automatically.

5. Now the last step is to just clock on the OK button and you have your action inserted. This action can be moved to any other desired location by just dragging it to that position.

Software Configuration Management Process

The SCM repository is the set of mechanisms and data structures that allow a software team to manage change in an effective manner. It provides the obvious functions of a DBMS but in addition, the repository performs or precipitates functions such as :
- data integrity.
- information sharing.
- tool integration.
- data integration.
- methodology.
- document standardization.
To achieve these functions, the repository is defined in terms of a meta-model.

Software Configuration Management Process :
A process defines the steps by which you perform a specific task or set of tasks. An SCM process is the way SCM is performed on your project—specifically, how an SCM tool is applied to accomplish a set of tasks.
- Identification of Artefacts
Early identification and change control of artefacts and work products is integral to the project. The configuration manager needs to fully identify and control changes to all the elements that are required to recreate and maintain the software product.
- Version Control
The primary goal of version control is to identify and manage project elements as they change over time. The Configuration Manager should establish a version control library to maintain all lifecycle entities. This library will ensure that changes (deltas) are controlled at their lowest atomic level eg documents, source files, scripts and kits etc.
- Change Request Management
Change Request management can be described as management of change/enhancement requests. Typically the Configuration Manger should set up a repository to manage these requests and support activities like status tracking, assignment etc.
- Configuration audit
Identification, version control, and change control help the software developer to maintain order in what would otherwise be a chaotic and fluid situation. But how can we ensure that the change has been properly implemented?
A software configuration audit complements the formal technical review by addressing the following questions :
- Has the change specified in the ECO been made? Have any additional modifications been incorporated.
- Has a formal technical review been conducted to assess technical correctness.
- Has the software process been followed?
- Has the change been highlighted in SCI?
- Have SCM procedures for noting the change, recording it, and reporting it been followed?
- Have all related SCIs been properly updated?