Black Box testing for web-based application: (4)
Software Testing Methodolog
(Continued from previous question...)
Black Box testing for web-based application: (4)
23. Printers
Users like to print. The concept behind the web should
save paper and reduce printing, but most people would
rather read on paper than on the screen. So, you need
to verify that the pages print properly. Sometimes
images and text align on the screen differently than
on the printed page. You need to at least verify that
order confirmation screens can be printed properly.
24. Combinations
Now you get to try combinations. Maybe 600x800 looks
good on the MAC but not on the IBM. Maybe IBM with
Netscape works, but not with Lynx.
If the web site will be used internally it might make
testing a little easier. If the company has an
official web browser choice, then you just need to
verify that it works for that browser. If everyone has
a T1 connection, then you might not need to check load
times. (But keep in mind, some people may dial in from
home.) With internal applications, the development
team can make disclaimers about system requirements
and only support those systems setups. But, ideally,
the site should work on all machines so you don't
limit growth and changes in the future.
25. Load/Stress
You will need to verify that the system can handle a
large number of users at the same time, a large amount
of data from each user, and a long period of
continuous use. Accessibility is extremely important
to users. If they get a "busy signal", they hang up
and call the competition. Not only must the system be
checked so your customers can gain access, but many
times crackers will attempt to gain access to a system
by overloading it. For the sake of security, your
system needs to know what to do when it's overloaded
and not simply blow up.
Many users at the same time
If the site just put up the results of a national
lottery, it better be able to handle millions of users
right after the winning numbers are posted. A load
test tool would be able to simulate large number of
users accessing the site at the same time.
Large amount of data from each user
Most customers may only order 1-5 books from your new
online bookstore, but what if a university bookstore
decides to order 5000 different books? Or what if
grandma wants to send a gift to each of her 50
grandchildren for Christmas (separate mailing
addresses for each, of course.) Can your system handle
large amounts of data from a single user?
Long period of continuous use
If the site is intended to take orders for flower
deliveries, then it better be able to handle the week
before Mother's Day. If the site offers web-based
email, it better be able to run for months or even
years, without downtimes.
You will probably want to use an automated test tool
to implement these types of tests, since they are
difficult to do manually. Imagine coordinating 100
people to hit the site at the same time. Now try
100,000 people. Generally, the tool will pay for
itself the second or third time you use it. Once the
tool is set up, running another test is just a click
away.
26. Security
Even if you aren't accepting credit card payments,
security is very important. The web site will be the
only exposure some customers have to your company.
And, if that exposure is a hacked page, they won't
feel safe doing business with you.
(Continued on next question...)
Other Interview Questions
|