How to run a test automatically in Test Director?

The whole testing process revolves around the execution of the tests. As the changes are introduced in to the software system or application, running tests either manually or automatically becomes mandatory so that the defects can be located and quality can be assessed. 

How are tests run?

- One starts the testing process with the creation of the tests and adding these tests to a test set. 

- Tests are grouped into test sets by the test director so that some specific goals can be achieved. 

- Execution process of the tests can be controlled via the various controls provided by the test director. 

- Along with these controls, there are certain conditions and settings which need to be configured for the execution of the tests as desired by the tester. 

- The date and time can also be scheduled when the tests will be executed. 

- Once the tests have been defined the tester can begin with the execution of the tests. 

- Whenever the tests are executed manually, it is basically the test steps that were defined earlier during the test planning which are executed one by one. 

- The steps are passed or failed by the tester depending up on whether there is a match between the expected results and the actual results. 

- For the automatic run of a test, the selected tool is directly opened by the test director and the test is run. 

- The result hence obtained is exported to the test director. 

- Setting conditions and specifying date and time for the execution of a test both can be done with the help of the execution flow tab.

- In the execution, one thing should be noticed which is that the condition is always dependent on the result of some other specified test in the same flow. 

- Also, the sequence in which the tests are to be executed can be specified. 

In this article we shall see how the test execution can be automated. The tool selected for the execution of the tests is opened directly by the test director and the tests are run on either local or remote machine. It is either choice if you want to run all the tests or some specified ones. 

For running the tests automatically one of the following tools must be installed on the system:

a)   Astra quick test

b)   Quick test professional

c)   Winrunnner

Follow the below mentioned steps:

1. Clicking on the test lab tab will display the test lab module. This is a must for the automation of the tests.
2. The test set you want to execute automatically should be displayed in the execution grid. For doing this click on the execution grid tab and select the required test from the test sets tree.
3. Select a test. For running the winrunner test select the required test or if you want to run an astra quick test or QTP test select the required one. Next clicking on the run button will open up the execution dialog box and the test will be displayed.
4. Configure the test run settings and select the ‘run all tests locally’ option for running the tests on the local machine.
5. For running the tests click on run tests and the tool will be opened automatically by the test director and the tests will be run. The execution progress can be viewed in the status column.
6. Once the execution of the test is complete close the execution dialog box by clicking on the exit option.
7. Also the summary of the test results can be viewed in the execution grid.

What are file types used in Silk Test?

Silk test consists of many file types which have been discussed in this article. There are various types of files that are used by the silk test in the process of automation testing. 

Each of the files is used for a specific purpose or we can say function such as certain files are required by the silk test for the creation and execution of the tests. 

Now we shall discuss the different file types available one by one:

1. Test plan (.pln): This file type in silk test facilitates the creation of the test suites. But the test suites can be created lonely if this file type is combined with the test scripts.

Testone

          Script: test.t

          Test case: one

Testtwo

          Script: test.t

          Test case: second

Here in the above example the main test script file is test. t. on the other hand the ‘one’ and the ‘second’ are the names of the test cases in the main script file test.t. Whenever this file type is run the test cases one and second are automatically picked up by the main script file and executed.

2. Test script (.t): This file type in the silk test is used while writing the actual test scripts. Whenever such a file is in run session the test one and test two test cases are executed by it in a predefined order and at the end the note pad application is closed.
3. Frame file (.inc): The windows and the controls present in the AUT or application under test are defined by an abstraction layer. These windows as well as the controls are referenced later in .t files.
4. Result file (.res): This file type consists of all the test run results which have the names of all the passed as well as failed tests along with their suitable descriptions. These file types may or may not contain log messages.

Leaving out the result file (.res) type, almost all the other file types are based up on text. Therefore, the editing of all those files can be edited either using the silk test IDE or by using a text editor.

In the silk test version that was released in the year of 2006, the files can be saved in either of the two formats namely:

1. ANSI format or
2. The UTF – 8 format

5. Project (.vtp): This file type is saved with an extension of 'verify test project' and is used as storage for the locations as well as the names of the files that are currently in use by some project. With this file type there is another associated file type .ini extension since it is an initialization file.
6. Data driven script (.g.t): This file type stores the data driven test cases which are use to pull out data from the data bases.
7. Suite (.s): With the help of this file type the sequential execution of several test scripts is possible.  
8. Text file (.txt): This is an ascii file type and can be used for the following purposes:

a)   For storing a data that can be used for driving a test.

b)   For printing a file in some another document.

c)   The test automation file is accompanied by this file type as a read me file.

d)   For transformation of a tab delimited plan in to a silk test plan.

Entire above discussed source files are compiled and stored as the ‘pseudo code object files’ at either of the times:

1. When the files are loaded or
2. When any change has occurred in the file types. 

What is the difference between the graphical user interface testing and usability testing?

There are different types of testing and graphical user interface testing and usability testing are two of them. In this article we have taken up the discussion regarding two types of testings mentioned in the heading plus the differences between them.

Though the graphical user interface testing and usability testing sound quite similar to one another but they are quite different from each other. First we shall discuss about these two types individually and later we shall see the differences between them. 

Graphical User Interface Testing

- Graphical user interface or GUI testing is all about checking the graphical user interface of a developed software system or application as a measure for ensuring that it holds up to its specifications as mentioned in its documentation. 

- The GUI testing is carried out with the help of several varying test cases. 

- The generation of good and effective test cases depends a lot on the certainty of the test designers regarding whether or not the test suite designed by them will cover the over all functionality of the software system or application under question.

- It also depends on the extent up to which the designed test suite exercises the graphical user interface of the software system or application. 

Usability Testing

- Usability testing is more like an interaction design centered on the users for the evaluation of the software system or application.

- The usability testing has been known for giving the direct input regarding the usage of a particular software system or application by the real world users.

- The usability testing actually falls in contrast with the other available usability inspection methods since in these methods the methods used for the evaluation of a graphical user interface are quite different.

- The primary focus of the usability testing is on the capacity of the human designed software system or application to fulfill its intended purpose. 

- The outcome of the usability testing is actually a measure of the ease with which the software system or application can be used. 

- Usability testing falls under the category of the black box testing. 

- The basic goal of the usability testing is to measure the following four aspects mentioned below:

1. Efficiency
2. Accuracy
3. Recall and
4. Emotional response

- Usability testing is carried with the aim of observing the users using the software system or application in order to catch the errors and spot the areas where improvement can be made. 

Differences between Graphical User Interface Testing & Usability Testing

Difference #1:

The purpose of the graphical user interface testing is to see the look and feel of a particular software system or application differs in different operating system. On the other hand the purpose of the usability testing is to make it convenient for the users to use the software system or application.

Difference #2:

Graphical user interface testing involves making confirmations regarding whether or not the software system or application adheres to its design requirements checking on the aspects like:

         a)   Colors

         b)   Fonts

         c)   Control placements and so on.

On the other hand the usability testing goes much deeper in to the above mentioned aspects like whether or not the controls have been arranged in a logical sequence.

Difference #3:

In Graphical user interface testing the tests are executed to check the following:

        a)  whether or not the standards are in place,

        b)   All the screen validations namely navigation conditions, validation 

conditions, aesthetic conditions and so on.

Usability testing involves asking questions like:

       a)   Is navigation intuitive enough?

       b)   Does the GUI make sense to the user? Etc.

What are different scrum controls?

It happens in some of the cases that the whole scrum process comes on the verge of the collapsing! In such cases it is required that the management controls stay in order, undisturbed and firm all the times. 

There are many scrum controls; however the risk assessment continues to be the most valuable one with its impacts as well.

What are different Scrum Controls?

The below mentioned are the effective scrum controls:

1. Issues: 

Issues can be thought of as the obstacles that do not pose any major risk, defect or bug but cannot be considered to be a positive aspect for the software project.

2. Risk assessment: 

This is the most influential scrum control also as it influences the other scrum controls quite much. The success of the project depends largely up on this scrum control as well its impacts.

3. Packets: 

These are product elements pending for the modification in order to facilitate the implementation of the product backlog items in to the working software that is to be released at the end of the sprint.

4. Backlog: 

This backlog consists of all the details of the bugs, defects and the requests of the customers that could not be implemented in the current release and have to be incorporated in to the next release. In addition to all these, the backlogs also consist of the technology and functionality upgrades.

5. Solutions: 

These are the scrum controls occurring between the risks, problems and changes.

6. Release and Enhancement: 

After the risk assessment, this is the second most valuable scrum control for the entire development cycle. This scrum control at any point of time represents a viable release based up on the requirement variables.

How does these scrum controls help?

- Most of the above mentioned scrum controls are employed for the management of the product backlogs and the sprint backlogs. 

- These scrum controls are used for the following purposes:

1. Managing issues
2. Obtaining better solutions

- Even these controls are reviewed from time to time and modified or reconciled if and whenever required during the sprint planning meetings. 

- These scrum controls help control chaos that occurs during the development process. 

- All the above mentioned scrum controls play a great role in the following stages of the scrum:

1. Defined processes
2. Project cost
3. Final product
4. Responsiveness to the environment
5. Completion date
6. Knowledge transfer
7. Team flexibility creativity
8. Probability of success

Scrum, we can say is an enhanced version of the iterative and incremental object oriented development cycle. 

The software releases in a scrum are planned according to the below mentioned variables:

1. Time pressure: Time frame required to make most of the competitive advantage.
2. Quality
3. Resource: It includes staff availability and funds.
4. Vision (system vision)
5. Competition: What is required to gain the competitive edge?
6. Customer requirements: How the current system can be enhanced?

All the above mentioned can be modified according to the development plan during the project. But any processes carried out further should take these changed variables in to account. A system that requires a complicate and complex development process require appropriate control and maximum and efficient control.