Black Box testing for web-based application: (1)
Software Testing Methodolog
(Continued from previous question...)
Black Box testing for web-based application: (1)
1. Browser functionality:
- Is the browser compatible with the application design?
- There are many different types of browsers available.
GUI design components
- Are the scroll bars, buttons, and frames compatible with the browser and functional?
- To check the functionality of the scroll bars on the interface of the Web page to
make sure the the user can scroll through items and make the correct selection from
a list of items.
- The button on the interface need to be functional and the correct hyperlink should go
to the correct page.
- If frames are used on the interface, they should be checked for the correct size and
whether all of the components fit within the viewing screen of the monitor.
2. User Interface
One of the reasons the web browser is being used as
the front end to applications is the ease of use.
Users who have been on the web before will probably
know how to navigate a well-built web site. While you
are concentrating on this portion of testing it is
important to verify that the application is easy to
use. Many will believe that this is the least
important area to test, but if you want to be
successful, the site better be easy to use.
3.Instructions
You want to make sure there are instructions. Even if
you think the web site is simple, there will always be
someone who needs some clarification. Additionally,
you need to test the documentation to verify that the
instructions are correct. If you follow each
instruction does the expected result occur?
4. Site map or navigational bar
Does the site have a map? Sometimes power users know
exactly where they want to go and don't want to wade
through lengthy introductions. Or new users get lost
easily. Either way a site map and/or an ever-present
navigational bar can help guide the user. You need to
verify that the site map is correct. Does each link on
the map actually exist? Are there links on the site
that are not represented on the map? Is the
navigational bar present on every screen? Is it
consistent? Does each link work on each page? Is it
organized in an intuitive manner?
5. Content
To a developer, functionality comes before wording.
Anyone can slap together some fancy mission statement
later, but while they are developing, they just need
some filler to verify alignment and layout.
Unfortunately, text produced like this may sneak
through the cracks. It is important to check with the
public relations department on the exact wording of
the content.
You also want to make sure the site looks
professional. Overuse of bold text, big fonts and
blinking (ugh) can turn away a customer quickly. It
might be a good idea to consult a graphic designer to
look over the site during User Acceptance Testing. You
wouldn't slap together a brochure with bold text
everywhere, so you want to handle the web site with
the same level of professionalism.
Finally, you want to make sure that any time a web
reference is given that it is hyperlinked. Plenty of
sites ask you to email them at a specific address or
to download a browser from an address. But if the user
can't click on it, they are going to be annoyed.
6. Colors/backgrounds
Ever since the web became popular, everyone thinks
they are graphic designers. Unfortunately, some
developers are more interested in their new
backgrounds, than ease of use. Sites will have yellow
text on a purple picture of a fractal pattern. (If
you've never seen this, try most sites at GeoCities or
AOL.) This may seem "pretty neat", but it's not easy
to use.
Usually, the best idea is to use little or no
background. If you have a background, it might be a
single color on the left side of the page, containing
the navigational bar. But, patterns and pictures
distract the user.
(Continued on next question...)
Other Interview Questions
|