Hi, We have been doing manual tesing for a long time and at last management has provided some funds for the initiation of automated testing.
The plan for the phase-1 is to automate the testing of mainframe green screens.
Management formed a group to identify the criteria for automation. I am one of the member in that team and currently we are formulating the criteria. I would look forward at this forum for some suggestions.
At high level, we are currently thinking of the following:
1. Winrunner should be used for the automation scripts
2. Regression testing can be automated
3. Data creation should be automated
Any suggestions on this one would be greatly appreciated...
LynneM, We have some client server applications and we believe winrunner will work for them also.
Nanook, yes, we already own mercury products.
Daniel, Currently data is created manually and spending lot of time on this one. Most of the time we identify the data from the production and ask the data team to migrate those accounts into test bed. For new scenarios we will manually create data in the test bed.
Maybe someone else can elaborate on this a bit more or correct me, but I get the impression that Mercury is phasing out Winrunner in favor of QTP. I.E. Winrunner isn't being updated with the latest technologies. Considering this, how well does QTP work with mainframe apps?
I understood that Winrunner was being maintained for the technologies that it supports and that QTP does not support. I believe, but someone correct me if I am wrong, that there are no current (or at least public) plans to phase out Winrunner.
QTP works very well on AS400 so as it uses same add-in I would say that it works very well with mainframe.
Out of the 2 I would always look at QTP rather than Winrunner as it is where Mercury is putting its efforts and research.
QTP does have some issues with Client Server interface testing. It was actually meant to test web pages and screens whereas WR was designer to test Client Server systems, The truth is WR was designed to test POS systems, but that was a long time ago. If I were testing client server I would still pick WinRunner. But I think I would script it to a Data-Driven-Keyword methodology, just to make maintenance as simple as possible..