Keeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveCollaborationbetween Devsand QAsencouragescreativity andinnovationTheenvironment forautomationneeds to beisolated andcontrolledBugs foundin postdeploymentis cheaper tofixSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itDevelopersshould testtheir owncodeNon-functionaltestingassesses howwell a productbehavesCollaborationencouragescreativity andinnovationDefects andbugs thatcan lead toincorrectfunctionalityExhaustivetesting ispossibleRetesting iswhen testersensure bugsfound arefixedIncrementaltesting is aform ofIntegrationtestingBusiness-critical testscases shouldbeautomatedLack of testdata ischallengingfor testersRunningthe sametests findsmore bugs"It workson mylocal"Testersshould thinklikedevelopers tobe successful"It's not abug. It's afeature."Test caseand scenariocreation fallsin TestDesign phaseTestingprocessesshould beregularlyreviewedTesting cannot provethe absenceof bugsThe pros faroutweighsthe cons inautomatedtestingBoth test casesand test scenariosare crucial inensuring a smoothtesting processPerformancetesting ispart of non-functionaltestingAutomateeverything!Enhancedquality isachieved byworkingtogetherFunctionaltesting verifiesthat thesoftwarebehaves asexpectedTight deadlinesoften limit thetime availablefor thoroughtestingSoftwaretesting fallspart ofQualityAssuranceKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveCollaborationbetween Devsand QAsencouragescreativity andinnovationTheenvironment forautomationneeds to beisolated andcontrolledBugs foundin postdeploymentis cheaper tofixSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itDevelopersshould testtheir owncodeNon-functionaltestingassesses howwell a productbehavesCollaborationencouragescreativity andinnovationDefects andbugs thatcan lead toincorrectfunctionalityExhaustivetesting ispossibleRetesting iswhen testersensure bugsfound arefixedIncrementaltesting is aform ofIntegrationtestingBusiness-critical testscases shouldbeautomatedLack of testdata ischallengingfor testersRunningthe sametests findsmore bugs"It workson mylocal"Testersshould thinklikedevelopers tobe successful"It's not abug. It's afeature."Test caseand scenariocreation fallsin TestDesign phaseTestingprocessesshould beregularlyreviewedTesting cannot provethe absenceof bugsThe pros faroutweighsthe cons inautomatedtestingBoth test casesand test scenariosare crucial inensuring a smoothtesting processPerformancetesting ispart of non-functionaltestingAutomateeverything!Enhancedquality isachieved byworkingtogetherFunctionaltesting verifiesthat thesoftwarebehaves asexpectedTight deadlinesoften limit thetime availablefor thoroughtestingSoftwaretesting fallspart ofQualityAssurance

Software Testing BINGO - Call List

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