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.
1. We get a list of files from the installation package builder. We need to get a list of files before, and the file list checking is performed after the installation. We can also hear the phrase: “Make a list after the installation, everything is true there” – this is a provocation! Do not give in!
Another point: the same installation package can install different file sets under different operating systems, i.e., we perform testing for each operating system separately.
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.
Decision tables are used:
– when the output data or program behavior depends on the combinations of input data values;
– by checking the “business rules”.
Decision tables are usually divided into four parts.
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.
Practical Tips on Software Testing 