Each software tester knows that functional testing is not the only activity type of web site testing, desktop testing or mobile application testing. In order to perform a testing process thoroughly, real users should be involved in testing activities.
It is a good practice to create models of typical and problem users and utilize these models in course of software testing. The models should be detailed and realistic. For creating them it is necessary to inquire who will work with the software product under test.
Gathering information and elaborating models of potential users one should be careful. Nowadays a number of laws regulate usage of personal data. So, it is wise to be on the safe side and create a model basing on several people and using imagination. The characters should be detailed, realistic but generalized.
It is very helpful for a tester to be able to imagine software product end-users, peculiarities of their life, habits and surrounding which effect interacting with the application.
It is Important to Get to Know Such Data About Software Users:
- Where the user usually is and where he or she interacts with the application. What lighting and weather are usually there?
- What Internet connection he or she usually utilizes. Whether the connection is strong and reliable or the signals are weak.
- What is the user profession? He or she works in the office or outside? If the work is physical and the user’s hands are dirty, how does this factor influence over interaction with the software?
- With what programs may the user work while the tested application is functioning? What software is installed on the user’s device?
- What else the user might do while working with the program under test? Will the user interrupt or postpone interaction with the tested software? What impact this will have on the application?
- If we are talking about mobile testing it is good to know how often the application functioning will be interrupted by incoming calls, various messages and notifications from other programs. How the interruptions will influence the tested software?
Basing on this information it is possible to create several different detailed models of user characters. The testers should imagine how each of the created user character would react on various features of the tested software and what difficulties he or she may face.
A software testing company advises its testers to pretend being one or another character. In this case a tester can demonstrate for colleagues and for himself or herself user behavior and usability problems of the tested software product.
This entry passed through the Full-Text RSS service — if this is your content and you're reading it on someone else's site, please read the FAQ at http://ift.tt/jcXqJW.