QuickTest Pro Automated Testing

Question

I have three simple questions.

Does anyone use QuickTest Pro for automated testing?

Any other automated testing apps you recommend?

Automated testing of a good idea?

thanks

Answer 1

With regard to test automation, there are several threads:

• What is better for web testing? Recording automation or coding?
• User interface testing
• Automated GUI Testing

I never used Quick Test Pro, but I worked on several projects that used various automated test tools; Silk Test, Rational Robot, WinRunner. The most successful of these efforts were those that used Rational Robot with the RRAFS card to isolate application changes from test scripts. We also use STAF to automate and manage our test infrastructure.

Automated testing is a good technique for testing aspects of an application, but it does not replace human testers. Like all tools, you can use it or you can abuse it. So far, what you are testing is stable, repetitive, has predictable or calculated results, and you test it often enough, then the automation costs will ultimately pay for themselves.

Answer 2

I led the automation team that used QTP, and I hated it. The recording / playback functionality was terrible, it was usually confusing, which led to strange test results. A record can only be used to create a database of objects, and even then she had to give all kinds of hacks to make it work somewhat reliably.

QTP / QC is based on ActiveX / COM and can only be written using VBScript, which is another flaming dog poo package. There are all these hacks and tricks that we had to do to get any extensibility. We did things such as running a test, which dynamically adds a QTP test to the test suite, edits input parameters, changes the object repository to suit the environment, saves the test, creates an instance of the scheduler to run the test. After the test completes, copy all the results to the parent test, and then remove the QTP test from the test suite. In the end, we ended up publishing custom COM components that VBScript called and used QTP / Quality Center as a semi-powerful reporting engine, which in fact did not provide enough flexibility to get the type of reports that we really need.

Another problem with Mercury / HP is that they transferred all their technical support to India and did not train them. It was common to spend 2 weeks on a lower level of purgatory support before you could talk to anyone with any technical knowledge of the API, just to say that yes, this is a mistake, but we will not fix it.

I regret the strong language, but I found that the whole episode is traumatic and will never work on a project or for a team that uses QTP / QC again.

Answer 3

I found automatic non-UI testing to definitely deserve it.

Automated user interface testing is also worth it, but not so much. For my project, the user interface is less than 10% of the code. Automated testing of the user interface has many other problems, such as synchronization and access to the stream, which makes it more difficult than expected. I use nunitforms to test the user interface.

I would suggest that if possible, check the interface logic first and then check the last user interface. You get a much better hit for the dollar with non-UI testing.

I appreciated the QA automated testing program and it looked good, but I went with nunitforms as it looked more like what I did for testing other than the UI.

Answer 4

"Automatic testing" is not as good as it seems. As far as I can tell, this is test automation, which is only part of the process.

Answer 5

what automatic testing?

I wrote some scripts that are part of the post-build process to compare some results using the API, but this is not specifically what you want.

As for automated applications for the Windows user interface, I saw a glimpse of a rational robot, but I can not specifically recommend it.

Answer 6

We do not use QuickTest Pro, where I work, but we are in the process of exploring options for automatic system testing. As for the recommendations, this is a bit complicated, not knowing what your criteria are for accepting or rejecting a software tool. I evaluate automated system tools according to these criteria:

• Does anyone other than a programmer allow automated system tests to be created?
• Can script programmers use it for customization?
• Does this support data-based testing (runs one test in a row with test data from external files and / or databases).
• Can you customize the launch of order tests?
• How well does it support inclusion in a continuous integration environment?

These are just opportunities. Cost is certainly a factor. Regardless of whether the tool requires learning a corporate language for scripting, this is another factor.

Automated testing is definitely a good idea. Automated testing is one of the key factors for continuous integration .

Answer 7

Automation of any tasks should be there if the tasks have a repetition. in the module, if you need to run regression test cases for each assembly in which some minor improvements are made in the product, then the launch of the regression script can be automated. In this example, resident test case automation will increase productivity and allow the tester to focus more on manual testing.

Besides qtp, you can also learn squish for qt related projects and a testing partner for Windows C ++ and VB projects.

Answer 8

Dan, I use QTP 11 for automation.

Let me know your requirements, for example, which application you want to test, etc. Many open source tools and shareware are available for almost all types of applications.

Automated testing is a good idea, provided that what you are about to automate will not change very often. If not, you will end up modifying test cases more often than using it in your application when necessary.