In this post we will discuss the points to take care while testing following applications:
- STAND-ALONE DATABASE APPLICATION
- CLIENT/SERVER APPS
- WEB BASED APPLICATIONS
- PRINTERS AND DRIVERS – Interface software
- LOCALIZATION / INTERNATIONALIZATION
STAND-ALONE DATABASE APPLICATION
- installation (copy files, settings to registry, icon, groups). “Vanilla Windows” installation.
- forms: test each field for capacity (5 test cases) and valid/Invalid input (3+), functionality
- reports – calculations, data display (window sizes), colors, proportions, query attached
- search – create database for testing that feature, each search-able field, combinations of 2 and 3, wild cards (* and ?) and their positioning
- sort by multiple criteria, use empty fields to be substituted by data from other fields
- import/export use Complete Record for testing (empty fields, shorter strings, data going to wrong field), volume testing
- backup/restore – same as above
CLIENT/SERVER APPS
- administration
- installation (client, server),
- user rights/privileges
- error messages
- database security (user ID, password)
login: boundary testing (6-12 characters), letters & digits, case sensitivity
password: boundary testing (6-12 characters), letters & digits, case sensitivity, replacing characters for asterisks, no CUT/COPY, # of failures
WEB BASED APPLICATIONS
- Browser/OS Compatibility (overlapping frames, missing images, links not linking, fonts changing sizes)
- performance
- navigation (Dynamic Pages)
PRINTERS AND DRIVERS
- Printer Drivers (especially new) are buggy
- do not use new printers and drivers for testing applications
- try multiple printers/drivers to decide if the problem is in the AUT or in driver
- how do you install a new printer?
- how do you know the version of a driver? (right click menu/printing preferences/right mouse click menu/About…)
- Verification – overlapping actual result page with expected result page
- Bug report – attach scanned image of the page with highlighted problems
- Enumeration becomes a part of the bug description
- test case is a file/document to be printed
- Automation of creating printouts -is easy
- To automate verification we print to file and binary compare files automatically
- Problems to look for: incomplete content (part of data not printed), font issues (size, style, etc.), overlapping, lost positioning/adjustments, typing outside of page (labels, envelops), double-sided (order changes on the fly)
LOCALIZATION / INTERNATIONALIZATION
- adjusting software to another language, currency, time/date format
- double-byte characters set problem
- standard names for controls are provided by Microsoft (GUI standards) in many languages
- LOOK AT controls (menu items, label, list boxes)
- EXPECT labels/list items not fitting into frames, incomplete translation
- Internationalization – making software independent of language, currency, date format
Recent Comments