Archive for January, 2012
Screenshots are needed for bug reports, user guides, figures of expected results, etc. Sometimes one screenshot is more useful than long confused description. In this post I gathered methods of screenshot creating which I use in my daily work.
Let our program take a dozen parameters. To test all combinations is very difficult, so you should choose the most common and potentially affecting each other. Bugs that arise by a particular combination of all ten parameters are rare.
The most common are bugs that arise by a particular combination of two parameters. The more information about the mutual influence of the parameters (more precisely – of the mutual non-influence), the more combinations we can not test. In the absence of such information, as well as by complex algorithms of program behavior, you should apply the method of pairwise testing.
Thus, we can simplify our task and test all the possible values for each pair of parameters.
In my previous article, I told you about such usability testing methods as Contextual inquiry, Checklists, Prototyping. This time, let’s talk about Surveys, Questionnaires and Pluralistic walkthroughs.
Survey is a special interview with the users, where they are given specially prepared questions, and their responses are recorded for further processing. The traditional reviews methodology may also play an important role in the study of application. Questions included in this review may vary depending on the purpose of the study, but are generally grouped into the following categories:
Boundary Value Testing is the most well-known and simple technique of test design, which helps the tester choose the most effective values from the ranges of values. This technique is applicable at all levels of testing – unit, integration, system, and system-integration test levels.
We consider the steps of using of the equivalence classes technique:
1.Determining the range of values (usually, the equivalence class).
2.Determination of the boundary range.
3.Creating three test cases for each boundary – one that checks the border value; second that checks the value below boundary; and the third that checks the value above boundary.