Software Testing - difference in testing client-server, web based and main frame applications

Author

difference in testing client-server, web based and main frame applications

newtoqa

2007-03-08, 10:11 pm

Hi,
I am new to qa and I have one question. When testing client server
application, web based application and mainframe application what are
the main differences? Can someone please explain it? Thankyou!

robert.keith@digitaltester.com

2007-03-13, 7:19 pm

On 9 Mar, 02:46, "newtoqa" <pujag...@gmail.com> wrote:
> Hi,
> I am new to qa and I have one question. When testing client server
> application, web based application and mainframe application what are
> the main differences? Can someone please explain it? Thankyou!

Client-server is a network architecture. It seperates an application
into 2 parts. The client is typically responsible for interacting with
the user and based on this interaction it requests the server to
perform specific tasks. Usually there are more clients than servers.
The server is usually the brains in the partnership, it has all the
data and all the routines that allow clients to access information
using a specified protocol.

Client-server testing therefore looks at validating the interaction
between the client and the server. It will ensure that the client
makes relevant requests and that these requests are formatted
(encoded) in an agreed way and then ensures that the server responds
with the requested information in an agreed format (encoding)

Web based testing is a form of client server testing, however it is
concerned specifically with testing interactions between clients using
web based protocols (HTTP, FTP, SMTP) The client is typically a web
browser and the server could be anything that is capable of returning
data over HTTP. This could be a PHP web page that displays database
records or accepts an order.

Mainframe testing also falls under the client server umbrella. THe
main-frame runs the application and the client merely displays the
data. Mainframe terminals are typically referred to as "dumb
terminals" since all they do is display the text that the mainframe
tells them to.

If you want more information on testing check out my blog @
http://blog.digitaltester.com

Hope that this has answered your question,

Rob
Development Director
DigitalTester Limited
http://www.digitaltester.com

info@e-valid.com

2007-03-13, 7:19 pm

On Mar 8, 7:46 pm, "newtoqa" <pujag...@gmail.com> wrote:
> Hi,
> I am new to qa and I have one question. When testing client server
> application, web based application and mainframe application what are
> the main differences? Can someone please explain it? Thankyou!

There are many differences in the way you test these three
kinds of systems.

Client/Server and mainframe (legacy) apps are fundamentally
different in the way a user interacts with them, namely, on a
screen.

By comparison, with a web browser enabled applications you
interact with the face of a browser, in this case called the
"client" (the client browser).

Assuming that software testing means "systematically
exercising an application to ascertain or confirm quality
oriented properties about it," then the easiest way to test a
browser enabled application is via tests that work
in/through/with a browser.

The simplicity of this approach accounts for the very strong
interest in GUI-based testing -- for web applications, through
a browser.

There are many ways to drive tests from a browser, of course,
but the best/easiest solutions are if you can do that work
FROM a specialized browser. The eValid web application
testing solution is that kind of support engine -- a full-
featured browser with test functionality built inside.

You can download your evaluation copy of eValid V7 from:

http://www.e-Valid.com/Products/Dow...tml?status=FORM

Full details about the eValid web analysis and testing suite
can be found at:

http://www.e-Valid.com

Sponsored Links