while talking to a mercury interactive representative , he mentioned that Winrunner was more for legacy testing and Quicktest pro was more for the web ... I thought I was going to find the definition of legacy testing here, but this is the closest topic to what I'm looking for and there's no clear definition for that ( at least in QAforums.com ) , so if you happen to read this message and you know the definition of legacy testing , please share the knowledge with us .. Thanks
Legacy just effectivily means old but still in use. Some of the vendors of tools now refer to anything that is non web as legacy, rather as when I started we refered to mainframe as legacy because PC's on client server architectures were the new thing.
One day the web development as we currently know it will be classed as legacy.
Agile Testers of the World UNIT!
Thank you for pointing out that Mercury sales representatives may be the last people to ask about this sort of thing. Legacy systems (take it from someone who was around when computers still used vacuum tubes) are characterized by a batch oriented input/output architecture. What is potentially confusing is that many systems are now front-ended with servers that in turn do a good job of presenting on-line fronts and even web fronts (on-line banking systems are a prime example of that). To the extent that a legacy system is accessed through some front-end, be it a web browser interface or a 3270 green screen or any other type of interface that can be run by emulation on an MS-Windows platform, you can use most of the modern test automation tools. If you test pure legacy systems, or any back-office application, you may need to use input/output files, pipes, queues, andsoforth, that require a completely different testing paradigm. Although I suppose it is possible to script such files by means of Winrunner or QTP, that is like hanging a picture by using the back of an axe to hammer a nail in the wall. To answer the initial post, if you look into a traditional Cobol or Fortran manual/book it will likely come with examples of legacy systems and file handling that are the key to understanding the differences.
For IBM Mainframe apps written in CICS - Mercury Winrunner works well and has the ability of a "GUI Map" interface - not as clean as web GUI but works well. Not sure about QTP as I have not yet had the chance to work with it. Compuware has a special testing tool for IBM CICS applications called Hiperstation.
If your legacy systems are on an AS400 as far as I know you are limited to test based testing using any of the tools - however, providing you plan and design your automation, you can develop some extremely effective automated testing.
If your legacy systems are web/client based no or little difference.
Every system once in production use becomes a legacy system.
I have not failed. I've just found 10,000 ways that won't work" --Thomas Edison