Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

About testing

Posted on 2004-10-19
1
Medium Priority
?
186 Views
Last Modified: 2010-04-17
Can anyone give me a general idea of the real life testing process, not the type of testing? I want to how a testing team works.
And give me some details about Stress, Volume and Performance testing, and the testing tools?
0
Comment
Question by:JavaQuestioner
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 3

Accepted Solution

by:
R_Janssen earned 375 total points
ID: 12356830
Well, testing is mostly different for each company/development team.
So I'll stick to my own testing methods:

Basically if you have a complete application or at least a prototype that you wish to test the first thing is to scribble down all the features of your application.

Important is that you work pretty linear on testing subjects. If one doesn't work. Fix that first, then start over from square 1.

Most 'testing teams' only have maybe 1 or 2 people on them. This is to make sure that errors aren't missed. 1 checks, the 2nd double checks the results.

Stress Testing:
Depending on the application at hand; For instance network service applications stress testing is done by creating enormous amounts of dataflow to the application, preferably the dataflow sent should mimic atleast double the amount of users that will be using it. If it kills the service, lower the amount. Also the data should be a mixed set. So for instance, if you wish to mimic 25 users, 12 users would send bogus data, 10 users would send retrieval request data and the rest data that has to be stored or commands.

For our own testing purposes on stress testing we developed an own application that listens to the data sent by the stresstest application. As we don't want the stress app to stress itself out :)

Volume and performance are also noted in this, Basically if the service maintains it's response and does it work the stress test would be set as completed. If the app is still in beta or prototype then stress testing it once a week isn't a bad idea as code changes daily.

Testing tools used mostly by our own team are Spy++, our own stress tool, SysInternal tools (Regmon, Filemon etc)

Hope this answers your question.


0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Q&A with Course Creator, Mark Lassoff, on the importance of HTML5 in the career of a modern-day developer.
This article will show how Aten was able to supply easy management and control for Artear's video walls and wide range display configurations of their newsroom.
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
Simple Linear Regression

704 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question