kusuma.m

• May 12th, 2005

 

choosing a tool depends upon the domain of the application, depends upon the features of the tools, types of testings to be conducted, clients budget and cost of the tool ,trained resources,

suman

• Jun 4th, 2005

 

choosing of a tool deends on many things ... 
 
1. Application to be tested  
2. Test environment 
3. Scope and limitation of the tool. 
4. Feature of the tool. 
5. Cost of the tool. 
6. Whether the tool is compatible with your application which means tool should be able to interact with your appliaction 
7. Ease of use 
 

jagadish

• Oct 7th, 2005

 

 If the application is of Functional based then for test automation Winrunner is used, if the application is of to test in performance core then for the test automation Loadrunner is used.

Jayanthi

• Oct 27th, 2005

 

We must otherwise know where all we can't use AUT tools.

1.Usability test

2.If results are not predictable

3.For small build

4.For applications not being stable

Bindu05

 Profile Answers by Bindu05 

• May 18th, 2006

 

Based on risk analysis like: personnel skills, companies software resources

Based on Cost analysis

Comparing the tools features with test requirement.

Support for the applications IDE, support for the application environment/platform.

 Bindu

Bharath.P

• Jun 5th, 2006

 

there r different types of tools r there in teh market for test automation

for functional and window based applications: winrunner

Java Based applications : silk

To Test Load And Performance of the web applications:LoadRunner

To test .net,java,sap,people soft,siebel,et.c :QTP

so depending on the crieteria we can decide which tool we have to use

suppose if u want to test web application functionality u can use either winrunner or qtp  qtp is is advanced one having extra features

if u want to test the performance u can use Load runner

purely java besed application we can use silk

somalin

• Nov 3rd, 2006

 

 How will you choose a tool for test automation?

anupak

 Profile Answers by anupak 

• May 21st, 2008

 

Based on the reuirement.

some of things that you might want to look are

• Interface that you are testing, For GUI, you might use tools like QTP  and for CLI you may use tools like expect etc
• How convinient it is to integrate with your framework.
• One test management tool like QC

Regards

Vinod

preethi.gollamandala

 Profile Answers by preethi.gollamandala 

• Sep 14th, 2009

 

it depends on the following reasons.

Client requirement
Project domain
Project environment
Customer requirements
Ease of use
Should be configurable with the project

nbabu11

 Profile Answers by nbabu11 Questions by nbabu11

• May 13th, 2011

 

1)All the objects are recognizable by the tool or not
2)For the recognized objects, scripting is getting created properly or not
3)Team is having the knowledge of the tool or not
4)Will that tool supports the application or not.
5)Do we have to add any add-in to support the tool to test the application.