| || |
How do I Automate the Client/server using testing tools.
How can i automate the following testing tools.
Automation Scenario: You come into a client/server
environment that has not been automated at all and you are given the information
listed below. How do you go about automating this environment and what tools
do you use to get the job done? What do you do if the tool(s) you have
selected are not enough to get the job done?
1. Platforms are Windows & UNIX
2. Server environments are NT 4.0 and Win2000
3. Client side can run on Win98, NT 4.0 sp6 and Win2000
Re: How do I Automate the Client/server using testing tools.
The first thing you need (in my opinion) is a test methodology for the client/server system. Any automation should follow from manual testing and an existing test methodology. This makes sure that the tool fits how you want to work, rather than the tool forcing the method by which you will work.
You also need to keep in mind the possible limitations of automation and recognize that automation testing is best (particularly initially) when it is done as a means of facilitating regression testing as well as combination/permutation testing.
You then have to evaluate the environment(s) that you need to automate. You said that you have Windows (three variants) and UNIX for client environments. You then have to determine if you want to automate on both environments or if you want to settle for automation on one. If you want both, you have to evaluate tools that will work on both environments. (Keep in mind that sometimes you have to use different tools. One tool solution may not offer everything you need.)
You also have to determine what types of testing you need from the tools. Obviously one aspect will be functional/behavioral but another aspect (particularly for client/server applications) is performance (load, stress, volume). This, again, however derives from your current testing methodology.
So, with all of that out of the way...
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by ranaj:
How do you go about automating this environment and what tools do you use to get the job done?<HR></BLOCKQUOTE>
It totally depends on some of the factors I mentioned above regarding the "how." As far as the tools, there are many solutions ranging from free to very expensive and, again, it depends on how well they suit your needs and what type of application you are using. And the different types of tools correspond to different testing tasks that you might want to perform on the application.
<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>What do you do if the tool(s) you have selected are not enough to get the job done?<HR></BLOCKQUOTE>
Then you have either not selected the right tools or you have relied on only one tool solution when, perhaps, more than one was necessary. The key here is that you have to do evaluation of the toolset before you decide to purchase it. The evaluation should consist of running it in your environment.
If you are in a situation where you find the organization has already bought certain tools that are not enough for the job, you will probably have to make a case for that point to your management.
[This message has been edited by JeffNyman (edited 12-16-2001).]