What is a follow up alert? How to create follow up alerts in test director?

Test director is mercury interactive’s test management tool. 

- It helps in creating a quality assurance personnel plan and organizing the whole testing process usually termed as the test director testing process.

- It lets you build a data base consisting of the manual as well as automated test cases, test cycles, run tests, reports of the tracking defects and so on. 

- The test director instructs to create alerts automatically and notify the responsible people whenever some changes are encountered by the project. 

- Alerts are generated for the changes that affect the project in one or more than one ways. 

- For generating automatic alerts, the administrator can activate the trace-ability notification rules based on the associations made among the requirements, defects and test.

What is a Follow Up Alert?

- Test director allows to add own follow up flag to a defect, test instance or a specific test so as  to remind oneself to follow up on an issue. 

- When the date of actual follow up arrives, an e – mail is send to the person’s mail box. 

- Test director notifies the tester by adding a trace that changes the flag to the changed entity or by mailing a notification whenever a change is made to the requirement, defect or test in the project. 

- Creating follow-up alerts is always useful since you are always reminded whenever it is required to follow up on some issues. 

Requirements for Follow up Alert

- Test director 8.0 should be installed on your system. 

- You must have access to all the four modules of the test director namely requirements, test plan, test lab and defects. 

- You must have either a sample project or an actual project on which you carry out the exercise.

- Work with a new copy of the project. 

- You should also have either a sample application or an actual application.  

Now we shall discuss the procedure to add a follow up flag to a defect whose status requires to be checked. 

When the follow up date comes, the flag icon is turned to red color and the test director sends a notification via e – mail. One thing that you should always take care of is that the flags have a specific user name which means only the user whose name is on the flag will be able to see it. 

Steps to create a Follow-up Alert

Follow the steps mentioned below to create a follow up alert:

1. Click on the defects tab so as to turn on the defects module.
2. From the defects grid select the defect for which you want to set up a flag to follow  up.
3. Now for creating a follow up alert click on the ‘flag for follow up’ button and a flag for follow up dialog box will open up. Fill in the following details:

a)   Follow up by: select the date.

b)   Description: type:

Once done with filling up the details click ok. A flag icon will be added to the      defect record by the test director.

4. To display the information bar for your follow up alert, double click with the follow up flag on the defect. A defect details dialog box will pop up and will display a yellow information bar with the follow up alert.
5. To close the dialog box click on cancel button.

What issues should be considered when deciding whether to automate a test? How to generate an automated test script?est Scripts, Scripts

Execution of the test sets lies at the center of any testing process. As the software system or application encounters changes, the defects are located by running both manual as well as automated tests in the project. Also, the quality of the tests is assessed by running the tests itself. 

Issues considered when deciding to go for automation?

- Deciding which all tests have to be automated is a part of the test planning process. 

- Two options namely manual and automated are available for the execution of the tests. 

- If you go with the manual execution of the tests, you can begin with the execution just after you finish defining the test steps. 

- If you go for automating the tests, the test scripts need to be generated and completed. 

- Below we state the issues that should be considered when deciding to go for automation:

1. Do Automate: Only the tests which are data driven or which make use of multiple data values for the same operation, which run with every new version of the application as a measure to check its functionality i.e., regression testing, which are for stress testing i.e., run many times and tests that facilitate the checking of a server system or multi-user client system (load testing) must always be automated.
2. Do not automate: The tests which are meant for a single execution, need to be executed immediately, check for the usability of the tests and whose result cannot be predicted should not be automated.

Steps for generating Automated Test Scripts

Below mentioned steps can be followed for the generation of the automated test scripts:

1. First, click on the test plan tab in order to enable the display of the test plan module.
2. Locate the manual test that you want to automate by selecting the subject folder available at the root of the test plan tree. There click on the find button and the find folder/ test dialog box will open up.
3. Type the name of the test to be searched for in the ‘value to find’ field of the box. Check the ‘include tests’ check box so that the test director can be instructed to look for folders and tests. Finally click on find option. ‘Search results’ dialog box will pop up thus displaying all the possible matches. Click on go to button and the test will be highlighted in the test plan tree. Close this dialog box.
4. Click on the design steps tab in order to display the design steps tab.
5. For generating a test script click on the generate script button. You can choose either of the following options:

a) QUICKTEST_ TEST: For generating an astra quicktest test or quick test professional test.

b)   WR – AUTOMATED: For generating a winrunner test.

The above two options will be available if the corresponding add ins have been installed. Once the test has been automated, the manual test symbol ‘M’ will be replaced by automated test icon.

6. For viewing the test script click on the test script lab. Click on the launch button for displaying and modifying the test script in the testing tool where it was created.

Whenever an automated test is run, the testing tool selected by the tester is opened by the test director automatically and the test is run on either the remote hosts or local machines. The tests can be run either from the execution flow tab or the execution grid tab.

How to call tests with parameters in Test Director?

Testing an application is a complicated process. Test director has provided help in many tasks such as in the organization and management of the different phases of the testing process which is inclusive of various activities such as test planning, requirements analyzation, defects tracking and so on. 

Test director basically provides the tester with a frame work that is well organized for the testing of applications just before their deployment. Test plans typically evolve around the requirements that are new or have been modified therefore; there is a need of having a central data repository for the management and organization of the testing activities. 

Test director proves to be an effective guide while you go through the following tasks:

1. Requirements specification
2. Test planning
3. Test execution
4. Defect tracking etc.

The above mentioned 4 tasks also represent the 4 major phases of the test director testing process. In the phase of test planning you have the following tasks:

1. Defining the testing strategy
2. Defining test subjects
3. Defining tests
4. Creation of the requirements coverage
5. Designing the test steps
6. Automation of the tests
7. Analyzation of the test plan

A test plan tree is constructed and then the tests are executed for locating the defects and assessing the quality. The following tasks are involved:

1. Creation of the test sets
2. Scheduling the runs
3. Running the tests
4. Analyzation of the test results

How to call tests with parameters in test Director?

- When the test steps are designed, you have an option whether or not include a call to a manual test. 

- When the test is executed, this manual test is called as a part of the execution sequence. 

- The test that is called is actually a template test which has the characteristic that it can be reused as a test that is called by other tests. 

- It is possible to pass parameters to a template test. 

- Parameter is a variable for replacing a fixed value. 

- The values of the parameters can be changed by passing the desired value to the test that calls it. 

Example:

- Suppose there is a test in which you need to log-in with a specific user id and password. 

- There might be two users to the same test i.e., administrator and public. 

- For achieving this, two parameters are created to the test namely user id and password. 

- The value of these two parameters then can be modified according to whether log-in has to be public or administrative.

Follow the steps below to call a test with parameters:

1. Firstly, the design steps tab needs to be displayed for the test therefore click on the design steps tab.
2. Select the test with parameters that are required to be called by clicking on the ‘call to test’ button. A ‘select a test’ dialog box will open up.  Type in the name of the test to be found and click find button. Test director will highlight that particular test. Click OK.
3. Again you will get a ‘parameters of test …’ dialog box which will display all the parameters associated with that particular test.
4. Modify the parameter values in the value column according to your requirements. Values to the parameters can be assigned whenever a test is created to call the tests or whenever a test is added to the test set or whenever the test is run.  Click OK. The selected step will be added to the design steps.
5. Re-order the steps
6. Adjust the step size.

How do you define Test Sets in Test Director? How do you add tests to a Test Set?

One can begin with the creation of test sets and choosing which all tests are required to be added to the test sets. 

What is a test set?

- A test set is a collection of tests in the test director’s terminology. 

- The concept of test set was developed so that specific testing goals could be achieved. 

- The execution of the tests in a test set can be controlled by scheduling the data and time for the execution and setting some testing conditions. 

- After the test sets have been defined, the time comes to execute them. 

- In the manual execution of the test sets the test steps defined earlier are executed. 

- The success or failure of test step depends on the one who is executing the tests based up on whether the expected and actual results match.

- In the automated execution of the tests, the selected testing tool is opened up by the test director, the test is run and the test results are exported to the test director. 

In this article we shall see how the test sets are defined and how tests are added to the test sets. 

- Once the tests have been designed in the test plan module, a test sets tree is created which makes it easy for the tester to organize the whole testing process by making groups of the test sets in a folder. 

- The test sets are organized at different hierarchical levels in the test lab module. 

- It is possible for the tester to include both the automated as well as manual tests in the test sets. 

- Also, there occurs no problem if at all the same tests are included in a number of test sets. 

- For the creation of an exact test set it is important that you keep your testing goals clear and concise from the beginning of the testing process itself. 

- Also the issues such as following need to be considered:

1. Current state of the application and
2. Addition of new features
3. Modification of new features.

Test director offers you some categories of test sets that can be created:

1. Sanity
2. Normal
3. Advanced
4. Regression
5. Function

Follow the steps:

1. Open the project.
2. Click on the test lab to display the test lab module.
3. Now you need to add a new folder to the test sets tree. Go in the left pane of the test sets tree and select the root folder. Create a new folder in it by specifying a name for it and click ok.
4. Now add the test set to the test sets list by clicking on the new test set button. In the new test set dialog box enter the name of the test set and its description.
5. Next you need to define the details of the test set by clicking on the test set properties and then details link. Select the status of the test set, it opening date and closing date.
6. In case there is an event failure you need to set the rules for automated tests in the test set.

How to add tests to a test set?

For adding the tests to a test set follow the below mentioned steps:

1. Display the test lab module by clicking on the test lab tab.
2. From the test sets tree select the test set to be added and then click execution grid tab.
3. Go to the select tests button and you can see the test plan tree. If any filters have been applied they need to be cleared using the set filter option.
4. Select the folder containing the tests that you want to add and then click ‘add tests to test set’ button. For confirmation click yes. Parameters of test dialog box will pop up since the tests that are being added contain unassigned parameters.
5. When you are done close the test plan tree by clicking on the close button.  

How to design and copy test cases in test director?

Application testing process is not the one that can be completed in a jiffy. It demands constant input in form of efforts, organization and maintenance. Well, all this becomes easy when you are assisted by mercury interactive’s test management tool.
Test director saves you a great deal of efforts for tasks such as requirements analysis, test planning, test execution, defect tracking etc. here in this article we are going to tell you how you can design as well as copy the test cases in test director. After the tests created for all the subjects have been added to the test plan tree and the basic test information has been defined, the test cases or the test steps are defined.
By defining them we mean that more details or step by step instructions are provided for how that particular test case is to be executed. Each step of a test case consists of two things namely:
1. Actions to be performed on the application under testing or AUT and
2. The expected results.

Test steps can be created either for manual tests or automated tests using test director. For manual testing it is said to be complete when you are done with the designing of the tests.
Then, the test execution can be straightaway be started by using the test plan tree. But in the case of the automated testing, an addition step is to create automated test scripts using any other mercury interactive tool such as Winrunner or some other third party tool.

Steps for designing test cases

Below mentioned are the steps that one can follow for designing a test case:
1. It has to be made sure that the test plan module is on display and if it is not click on the test plan tab to turn it on.
2. The test case for which you are about to design the test steps also needs to be displayed. You can do this by simply clicking on the name of that particular test.
3. Next you need to launch the design step editor by clicking on the ‘design steps lab’.
4. In the design step editor dialog box clicking on the new step button you will get a new step dialog box which will ask you enter a step name which is by default a sequential number.
5. Now for defining that step you require to fill up the following fields and click OK:
         a) Step name
         b) Description
         c) Expected result
6. Last step is to click OK which will close the design step editor and display the design steps.

How to copy the test cases?

In test director you get the option of copying the test cases either from the same project or from some other. Follow the below mentioned steps:
1. You need to turn on the design steps tab and select that particular test case from the test plan tree which you want to be copied.
2. Next step involves selecting the steps of the test cases which you want to be copied. You will observe a gray sidebar, position the mouse pointer there and you will see that the pointer changes to  ->. Now hold down the shift and select the steps you want to be copied.
3. By using the copy steps copy down all the selected steps.
4. Next paste the steps where you want them to be copied in the test plan tree by using the paste steps button in the design steps tab.

What is a Silk Test project? How to create a new Silk Test project?

These days silk test projects are quite popular with the software test automators. In this article our focus is on the silk test projects only. The first aspect of the article discusses what a silk test project is and the other aspect discusses how a new silk test project can be created. 

"A Silk Test Project can be thought of as a collection of files consisting of the information regarding to a test project". 

How to create a Silk Test Project?

- For creating a silk test project you need to go through the following steps:

1. First step, is to run the silk test.
2. Next step, involves selecting the appropriate basic work flow bar.
3. Now you need to open up your project on the work flow bar.
4. Select a new project from the list of options.
5. Just double click on the icon “create project” which is available in the new project dialog box.
6. Once you have opened the create project dialogue box, enter the name and the description of your project in the box.
7. Finally click OK after checking that all the details that you have entered are correct.

- All the resources associated with a set of test cases are organized by the projects in silk test and are later presented in the project explorer. 

- Such a presentation makes it much easier to view, work up on and manage the project in the test environment. 

- The project holds the relevant information regarding the project as well as other references to the associated resources such as the following:

1. Test plan
2. Test scripts
3. Test data
4. Test option sets
5. .ini files
6. Frame/ include files
7. Editor settings
8. Data files for queries as well as attributes
9. Results and lastly
10. The configuration information.

- All of this information is organized in the projects at the level of the project. 

- This also means that once the project has been configured after adding all the appropriate files to it, there is no need to do it again and again. 

- In silk test, it is quite simple to switch between the projects. 

- Whichever project you want to open, you can open it and execute the tests on it. 

- Whenever a new project is created, silk test agent is employed by the silk test automatically as a measure to provide support to the type of application that is being tested. 

- By default the following settings are not enabled in any project:

1. Enabled extensions
2. Agent options
3. Class mappings and so on.

- In silk test it is possible to retain the settings from the current test set by just saving the settings as the option set by using the option save new options set. - The saved option set then, can be included in the project whenever you create one. 

- Silk test provides you with two ways of creating a project:

1. Manual
2. Automatic

- Of course a project can be automatically generated by the silk test based up on the existing files as specified by the use. 

- Two project files are used by the silk test for storing the information regarding the project:

1. Project name.ini: It is an initialization file which stores information regarding the option sets, queries and so on that form a part of your project.
2. Project name.vtp: The extension stands for ‘verify test project’. This file stores the leftover things of the project information i.e., the names and locations of the files that are in use by the project. 

How will you check a web application for broken links using QTP?

Checking for the broken and ill links forms a very important aspect of any web testing profile. The below mentioned are few testings which take the priority of the web testing check list:

1. Usability testing
2. Functionality testing
3. Compatibility testing
4. Interface testing
5. Security testing
6. Performance testing

Out of all these the functionality testing tests the following basic aspects of a web page or site or application:

1. all the links in web pages
2. data base connection
3. forms in the web pages
4. cookies

When it comes to checking of the links the following links are tested:

1. out going links from a specific domain
2. internal links
3. links jumping on same page
4. links for sending mails
5. orphan pages and lastly
6. broken  links

Our focus is on last aspect i.e., testing of the broken links in a web page, site or web application with the help of the quick test professional. 

What are broken links?

- Broken links are also termed as dead links since they are permanently unavailable and hence cannot be accessed by the user. 

- If you would have observed you might have surely come across 404 error while browsing some site. 

- This signifies the presence of a broken link. 

- Using quick test professional, the broken links can be identified during the run time itself by following any one of the two methods mentioned below:

1. via manual creation of a check point
2. via automatic page check point

How a broken link be checked manually by creating a page check point?

- A direct menu option is not available in the quick test professional for incorporating a page check point. 

- Therefore, you need to take assistance of a standard check point. 

- What you actually need, is to click on the start recording session and then select insert option, then check point and finally standard check point option.

- You can use F12 if it works for you.

- Get the hand pointer on the web page and click OK. 

- You will get a page check point properties dialog box which has a broken link check box. 

- You need to check that box and click OK. 

- After this, you need to run the scripts and check the status of links in broken link result. 

- If the links pointing only to the current host have to be checked then you need to check the box titled check only links to current host by going to the tools menu and then selecting web options. 

- Similarly, if the links pointing to all the hosts have to be checked then this box has to be kept unchecked. 

For following the second method you need to go through the following:

Tools à options à web à advanced

- You will get two boxes labeled “broken links” and “create a check point for each page while recording”, check these both boxes. 

Now every time the quick test professional starts recording on a new page, a check point will be automatically included for all the broken links. 

One thing that you should know is that the quick test professional experiences some issues with the windows vista if the internet explorer version that you using is 7.0. 

Tabbed browsing is something that is not supported by the quick test professional especially in Microsoft internet explorer. 

An alternative to this can be to disable tabbed browsing first and then proceed with quick test professional. In internet explorer the quick test professional may not be able to recognize the web objects. 

What are the main attributes of test automation?

Test automation is nowadays counted among the best software development aids that we have today. It is a great testing aid that seeks to resolve the drudgery of the testers. Test automation has become so common nowadays that every one of us knows quite a lot about it.

What does Test Automation do?

- Test automation actually controls the execution of the test cases by using an automated process. 

- Also, the comparison of the actual and the predicted outcome takes place in the same and "take it easy" manner.  

- One thing that should be noted is that only those manual processes can be automated which have deployed a formalized testing process. 

- In the test automation process, the user actions are recorded and the checkpoints are introduced in to the testing script so that playing it back from a particular point is made easy when you have to perform regression tests. 

- The manual tests that passed can be automated and is mostly used in the testing methodologies like:

1. Data driven testing
2. Regression testing
3. Performance testing and so on.

Attributes of Test Automation

By attributes, we mean the characteristics of the test automation process. It has got quite a lot of positive attributes. So let us what all attributes we can state for test automation:

1. Repeatability:

Automation supports repeated execution of a test case several times again and again. When you need to execute the same test case again and again the test automation comes as a big win for you.

2. Programmability: 

The test cases can be programmed to be executed on a number of different machines whereas the manual tests have to be executed in a sequential way one after the other.

3. Reliability: 

You can rely on test automation for repeat-ability and accuracy.

4. Impact

5. Criticality

6. Maintainability: 

The maintenance is just that you have to update the test automation suites for every new release of the software system or application.

7. Flexibility: 

With test automation it becomes quite easy for you to run automated tests that frequently change according to the regressions at particular time intervals and also the tests can be run in mainstream scenarios.

8. Efficiency: 

The ratio of total cost to the required effort need is reasonable.

9. Portability: 

The automated tests can be executed in different environments unlike manual test cases.

10.Robustness: 

The automated tests are quite effective for the software systems or applications that are quite unstable or change rapidly.

11. Usability: 

The automated tests can be used to a large extent by different types of users.

12. Speed

13. Accuracy

14. Relentlessness: 

The automated test generator as well as the process never gets tired generating and running test cases.

There are some tests like exploratory testing and usability which cannot be automated because of their free style. Testers involved in a testing team support diverse software systems and applications that are quite unrelated to each other. 

- If the projects that demands implementation of a unique testing strategy, then the testers involved in the whole will appear more to be a hindrance rather than being a help. 

- The testers will require tie to get adjusted to the new environment which unfortunately they cannot get and thus lowering the level of their productivity. 

- We cannot waste time on re- engineering the development frame works but we can surely harness test automation power for every new application that we need to develop. 

- The application can be continuously improved since the test automation has got so many positive attributes that can surely benefit the whole testing process. 

How do you plan test automation? Can test automation improve test effectiveness?

“How to plan test automation?” is perhaps the most frequently asked question of today’s software testing field. Another important question is, “can test automation improve test effectiveness?” 

In this article we have tried our level best to answer both of these questions! 

What is meant by Test Automation?

- In test automation, we actually develop a quick process that will take care of the execution of the tests by itself i.e., without any human intervention.

- It also compares the actual and predicted outcomes, sets up the pre- conditions for the tests.

- A common test automation process involves automation of a manual testing process that makes use of a formalized testing tool. 

- Although the manual testing can discover a whole lot of defects in the software system or application, it is quite laborious or you can say it involves a lot of drudgery and time.

- It is not possible for you to discover defects of all the classes using manual testing; it is a task that can only be accomplished using test automation. 

- Test automation takes time only once i.e., while you automate them and after this it saves a whole lot of time when compared to manual testing, tests can be run quickly and repeatedly. 

How to plan test automation?

There are two approaches to test automation and both of them are equally good and either of them can be followed. They are:

1. Code driven testing: This approach involves public interfaces to classes, libraries or modules to be tested with a whole variety of the input arguments for the validation of the results that are returned and are quite correct.

2. Graphical user interface testing: This approach involves a testing frame work that generates a user interface events like mouse clicks and key strokes for the validation of the observable behavior of the program i.e., whether it is correct or not?

There is one drawback which is that the test automation tools can cost you much and they cannot be employed without manual testing. Test automation is effective if you have to repeatedly test one thing. 

There is one more approach to the test automation which is commonly known as “model based testing”. 

- Using this approach you automatically generate tests through the use of a model of the software system or application for the generation of test case but this method of planning test automation is still under research and controversies. 

- One should keep the following questions in mind while planning the test automation:

1. What to automate?

2. When to automate?

3. Whether or not automation is really required?

Can Test Automation improve Test Effectiveness?

Yes, test automation can improve test effectiveness.

- The test cases generated by test automation are quite reliable as compared to those created by manual testing.

- In test automation, human error is eliminated.

- The tests generated are repeatable as well as programmable. 

- They also have the following characteristics:

* Reusable

* Comprehensive: The test suite that is built covers all the features of the software system or application.

* Cost reduction: Due to less resources, used cost is also reduced.

* Fast: Testing is quite fast.

* Better quality software: The resultant software system or application is of better quality since it is tested by a large number of tests with fewer resources and less time.

Describe some automation testing tools?

Automated testing has greatly reduced the drudgery of the developers who otherwise would have to carry out testing on big software systems and applications projects manually. Today there are many automation testing tools available to your advantage. Using these tools you can automate any of the test scripts which will make your work easier than ever consuming less time and efforts. In this article we have discussed about some of the automation testing tools. They are as follows:

1. TestComplete: 

- This testing tool has been designed for both the novice as well as advance testers.

- Using this tool, creating, managing and running tests for any system becomes so easy be it a desk top or web software. 

- It has got a quite easy to use interface and a whole lot of tools for the purpose of customizing it

- This tool supports cross browser web testing, html5 applications and distributed testing as well. 

- Using this tool, you can create tests using just one browser which can be run on almost any browser.

- You do not have to make any changes to the tests i.e., testing is completely browser independent. 

- Furthermore, this testing tool is independent of any other development tool or software application. 

- It supports all the languages.

2. Telerik by Test Studio: 

- This testing tool supports functional testing, load testing, performance testing, and mobile testing very well. 

- It also supports in depth desk top testing i.e., you can easily test AJAX, HTML5, WPF and Silverlight apps. 

- This tool is quite affordable.

- Using this tool, you can create as well as capture tests.

-Web performance tests can also be created which offer a detailed insight in to the performance metrics of your apps.

- This tool is quite advanced and covers most of the technologies and protocols. 

- Using this tool, you can even run a functional test which in turn can help you to gather data on server processing time, client rendering time and network latency etc. 

- Furthermore, this tool supports testing for iOS apps.

- It also provides support for iphone, ipad, ipod, test natives, web and hybrid apps etc.

3. Micro focus- SilkTest: 

- Using this tool, one can create robust, powerful and fast automated tests across a quite broad range of technologies and applications. 

- It can be used easily for the identification of the quality related problems that occur in the early stages of the SDLC or software development life cycle. 

- Till now two versions of this testing tool have proven to be quite worthy namely Silk4Net and Silk4J.

- These two testing tools provide you with the option of bringing the power of SilkTest to integrated development environment of your choice like eclipse or visual studio and so on. 

- This testing tool has showed quite lot robustness.

4. HP: Unified Functional Testing Software (quick professional tool): 

- This tool rules the software industry.

- This tool has got the ability of accelerating the functional testing by following a simplification process for simplifying the test design and maintaining both the non GUI based applications and GUI based applications.

- The integrated test scenarios can be validated quite easily.

- All these features result in a reduction in risk and improve the quality for the applications of the modern era. 

- This testing tool includes HP service test products and HP functional testing. 

- It also includes some of the other add-ins from HP. 

- Using this tool you can increase the efficiency of your testing by using the automated processes and re- using of the data.