In this post, I will attempt to compare Scripted and Exploratory styles of software testing. On the third hand, scripted testing is seemed as a strict and serious process and exploratory one is seemed free and easy. But each test style has own swings and roundabouts. Let’s look at them from different points and try defining appropriate conditions to use first one and second one.
Posts tagged ‘software testing’
Some time ago I published the post “Test plan + templates”. I received many comments reflecting different views, so in this article, I decided to continue the talk about planning.
Firstly, I liked J.Hoffman’s and Hannibal’s comments very much, and at the beginning of the talk, I’d like to mention the main points of their comments.
In my previous article I told you about such usability testing methods as Surveys, Questionnaires and Pluralistic walkthroughs. This time, let’s talk about Self-reporting logs and Thinking aloud protocol.
Self-report logs are forms of “pencil-paper” type, in which users fix all actions and thoughts about interaction with application. This method is economical enough as experts are involved only in handling of results, without supervising action of the user in runtime of jobs.
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: