Lecture 1 - A Bug or Not a Bug -> Quick Intro -> Three Conditions Of A Bug’s Existence -> The Gist Of Testing -> Spec, Spec, SpecThe gist of any testing is a search for bugs. Whether we try a new food processor, observe the behavior of a girlfriend or boyfriend, or torture ourselves with self-analysis – we are looking for bugs.
Here is how bugs are found:
1. We find out (or already know) the expected result.
2. We find out (or already know) the actual result.
3. We compare the actual result with the expected result.
As you can see, each of us is an experienced tester ALREADY, because bug finding is an essential part of our existence.
Example
As an illustration of the correct approach, I can tell you about my pal who has developed a whole system of argumentation to support his thesis that humans and computers are built on the same principle. The cornerstone of his theory is the fact that both humans and computers have:
– physical containers (body/hardware)
– intangible content (soul/software)
Thus, when he gets sick he says “I’ve got a hardware problem,” and when he does stupid things he says, “My software is buggy.”
Now, let’s remember that we are here to learn about software testing. It’s more or less clear how to get an actual result – we just have to observe how the software behaves. Obtaining the expected result can be far more complex. Next ->
Lecture 1 - A Bug or Not a Bug >- Quick Intro -> Three Conditions Of A Bug’s Existence -> The Gist Of Testing -> Spec, Spec, Spec
