(Print) Use this randomly generated list as your call list when playing the game. Place some kind of mark (like an X, a checkmark, a dot, tally mark, etc) on each cell as you announce it, to keep track. You can also cut out each item, place them in a bag and pull words from the bag.
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
I-Running the same tests finds more bugs
O-"It works on my local"
B-Enhanced quality is achieved by working together
O-Testers should think like developers to be successful
B-Defects and bugs that can lead to incorrect functionality
I-Keeping test cases relevant and efficient as the software evolves can be labor-intensive
N-Business-critical tests cases should be automated
I-Tight deadlines often limit the time available for thorough testing
O-Automate everything!
N-Incremental testing is a form of Integration testing
G-Developers should test their own code
G-The environment for automation needs to be isolated and controlled
G-Testing can not prove the absence of bugs
I-Collaboration encourages creativity and innovation
B-Lack of test data is challenging for testers
O-Non-functional testing assesses how well a product behaves
B-"It's not a bug. It's a feature."
N-Bugs found in post deployment is cheaper to fix
B-Functional testing verifies that the software behaves as expected
G-Software testing tries to increase confidence in a product by pointing out what is wrong with it
O-Both test cases and test scenarios are crucial in ensuring a smooth testing process
G-Retesting is when testers ensure bugs found are fixed
O-The pros far outweighs the cons in automated testing
N-Testing processes should be regularly reviewed
G-Collaboration between Devs and QAs encourages creativity and innovation
B-Software testing falls part of Quality Assurance
I-Exhaustive testing is possible
I-Performance testing is part of non-functional testing
N-Test case and scenario creation falls in Test Design phase
