Test software with a user perspective

There are many aspects to testing. One intention is to prove that the final product meets the customer requirements. The tests are usually done in two parts: The tester makes sure that all of the required features and functions are present and accounted for, then the tester makes sure that the features and functions behave as expected.

There is a straightforward way of testing. But there are other aspects testers ought to be aware of.

Trying to break the application on behalf of the user
Let's take the example of a Web application that has a lot of online processing. If the first screen asks for a user id and password, I will start off by entering no values and see what happens. Did I get in? Did an error occur? Does the screen just sit there? What should happen is the application should consider this an invalid response and return the appropriate error message.

Users will type any value into online fields
When I get into application screens, I enter all kinds of crazy values. If the field expects an alpha, I enter a numeric. Then I enter special characters such as (*&%$â ™. I run through the rest of the fields the same way.

I also try to scr

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Software Testing 10 steps to acing Web app security assessments Three software regression testing steps can perfect defect fixes Exploring mobile layout testing, emulators and goals Preparing for testing applications in the cloud Hack maliciously to boost your software's security Testing functionality, performance of mobile Web applications Testing mobile Web applications for usability and context Using SBTM for exploratory testing coverage problems Web 2.0, RIAs push load testing to the max Using session-based test management for exploratory testing Usability testing TechEd 2009 test/dev products: A quick tour Testers: Time to gear up for mobile software testing Software QA managers welcome HP Quality Center updates uTest pilots on-demand software testing, QA service Usability testing vs. user acceptance testing Ten ways to improve testing, performance of Web 2.0 applications Quality assurance tools from Gomez facilitate Web application testing Software testing and quality assurance (QA) fundamentals Configuration testing: QA pros discuss 10 things you may not know Five roles test managers play in agile development: Tutorial, part one Three software regression testing steps can perfect defect fixes Software Testing: Assessing risk and scope Software Testing: How to know you're ready to start testing Quality assurance (QA) and testing's role in requirements Test case preparation for a Web-based application The difference between functional testing and regression testing Mapping results in test environment to production environment Agile software development tutorial: Agile testing

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary integration testing  (SearchSoftwareQuality.com) quality assurance  (SearchSoftwareQuality.com) zenware  (SearchUnifiedCommunications.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

ew up any pre-populated fields. I always tell developers that if you don't want a field changed, then do not allow a user to place a cursor in it and type. I guarantee you that if you leave a field open for input, at some point, at some time, someone will try to type a value into it.

Users will hit every combination of available logic flow
In addition to simple editing errors, I also try every combination of logic flow. When I look at a Web page, I try every hyperlink and see where I end up. The developers look at me and wonder why a user would ever do that. Again, the point is that they may not do it on purpose. However, you should expect that every combination of logic would be attempted at some time.

Look at the presentation
The last thing I look at is the presentation and overall look and feel. I try to make sure that screens have a nice appearance, nice font and that they are consistent. Consider a bulleted list: All items in the list should have a period at the end or they all should not. The fonts should also be consistent. If the headers on one section are 14-point fonts, they should all be that size. This is all a part of making the application look professional.