User Rajesh Roshan (email@example.com) posted:
Can anyone let me know What are the things to consider
for the question below.
A web based appliction that is tested and manual
scripts are created.Now planning to migrate the
application to different application server and want
to Automate these manual scripts.
Can we reuse the manual scripts for Automation? and
I would like to know how much work will go into
automating the scripts that would greatly increase
Can anybody help me or advice me on this. Thanks in
Re: Automation Scripts
User DAVID MARSH (DAVID.MARSH@thales-cs.com.nospam) posted:
You can do what you like... some chant the mantra of everything according to
the dark lord of rational, others are free spirits.
There is nothing to stop you from just writing your scripts based on your
present manual tests. A great advantage of this is that whenyour automation
fails, which could be because of Rational 'upgrading' something and leaving
you with huge problems, you still have the manual steps to follow to get you
out of the do do.
Have a look at Carl Neagles DDE stuff, or consider your own frame work.
Write a collection of functions.
A function for each type of object, to read and/or write to objects as
A function for each screen (caling the object functions), with the ability
to input data and extract results.
Use csv files to pump data into the screens.
Have some navigation functions to get between screens.
Have some functions to capture errors and clear unwanted windows.
By the sound of it Carl and his possee do it more elegantly than I do, but
we are both (almost) on the same wavelength, I've just got to do some fine
Please do not attempt to record and playback, it will end in tears.
The initial work this way is slow, but once you have your functions in place
future tests get realy easy as you have the building blocks there to knock
up scripts very quickly.
Time? I think you would have to do your own metrics, how long to do a
typical screen then how many screens plus and for the navigation and error
stuff then a bit more for each manual test for data preperation and writing
I prefer to write the tests as functions, then put a front end on so I can
write a subscript. I was working on a log system to generate a list of
tests to run, then how far I got so if automation stopped I knew where to
A very important thing to consider with your manual tests are if they have
dependancies, such as do you have to create clients with one test before you
can run the billing test? If so think about how you can set things up so if
you only want to run the billing tests you either create clients there, or
have the database prepopulated.