Developersshould testtheir owncodeSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itIncrementaltesting is aform ofIntegrationtestingCollaborationencouragescreativity andinnovationTestersshould thinklikedevelopers tobe successfulBusiness-critical testscases shouldbeautomatedRetesting iswhen testersensure bugsfound arefixed"It workson mylocal"The pros faroutweighsthe cons inautomatedtestingBoth test casesand test scenariosare crucial inensuring a smoothtesting processNon-functionaltestingassesses howwell a productbehaves"It's not abug. It's afeature."Collaborationbetween Devsand QAsencouragescreativity andinnovationEnhancedquality isachieved byworkingtogetherKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveLack of testdata ischallengingfor testersTight deadlinesoften limit thetime availablefor thoroughtestingRunningthe sametests findsmore bugsAutomateeverything!Performancetesting ispart of non-functionaltestingTesting cannot provethe absenceof bugsTheenvironment forautomationneeds to beisolated andcontrolledBugs foundin postdeploymentis cheaper tofixDefects andbugs thatcan lead toincorrectfunctionalityTest caseand scenariocreation fallsin TestDesign phaseTestingprocessesshould beregularlyreviewedFunctionaltesting verifiesthat thesoftwarebehaves asexpectedExhaustivetesting ispossibleSoftwaretesting fallspart ofQualityAssuranceDevelopersshould testtheir owncodeSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itIncrementaltesting is aform ofIntegrationtestingCollaborationencouragescreativity andinnovationTestersshould thinklikedevelopers tobe successfulBusiness-critical testscases shouldbeautomatedRetesting iswhen testersensure bugsfound arefixed"It workson mylocal"The pros faroutweighsthe cons inautomatedtestingBoth test casesand test scenariosare crucial inensuring a smoothtesting processNon-functionaltestingassesses howwell a productbehaves"It's not abug. It's afeature."Collaborationbetween Devsand QAsencouragescreativity andinnovationEnhancedquality isachieved byworkingtogetherKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveLack of testdata ischallengingfor testersTight deadlinesoften limit thetime availablefor thoroughtestingRunningthe sametests findsmore bugsAutomateeverything!Performancetesting ispart of non-functionaltestingTesting cannot provethe absenceof bugsTheenvironment forautomationneeds to beisolated andcontrolledBugs foundin postdeploymentis cheaper tofixDefects andbugs thatcan lead toincorrectfunctionalityTest caseand scenariocreation fallsin TestDesign phaseTestingprocessesshould beregularlyreviewedFunctionaltesting verifiesthat thesoftwarebehaves asexpectedExhaustivetesting ispossibleSoftwaretesting 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
G
2
G
3
N
4
I
5
O
6
N
7
G
8
O
9
O
10
O
11
O
12
B
13
G
14
B
15
I
16
B
17
I
18
I
19
O
20
I
21
G
22
G
23
N
24
B
25
N
26
N
27
B
28
I
29
B
  1. G-Developers should test their own code
  2. G-Software testing tries to increase confidence in a product by pointing out what is wrong with it
  3. N-Incremental testing is a form of Integration testing
  4. I-Collaboration encourages creativity and innovation
  5. O-Testers should think like developers to be successful
  6. N-Business-critical tests cases should be automated
  7. G-Retesting is when testers ensure bugs found are fixed
  8. O-"It works on my local"
  9. O-The pros far outweighs the cons in automated testing
  10. O-Both test cases and test scenarios are crucial in ensuring a smooth testing process
  11. O-Non-functional testing assesses how well a product behaves
  12. B-"It's not a bug. It's a feature."
  13. G-Collaboration between Devs and QAs encourages creativity and innovation
  14. B-Enhanced quality is achieved by working together
  15. I-Keeping test cases relevant and efficient as the software evolves can be labor-intensive
  16. B-Lack of test data is challenging for testers
  17. I-Tight deadlines often limit the time available for thorough testing
  18. I-Running the same tests finds more bugs
  19. O-Automate everything!
  20. I-Performance testing is part of non-functional testing
  21. G-Testing can not prove the absence of bugs
  22. G-The environment for automation needs to be isolated and controlled
  23. N-Bugs found in post deployment is cheaper to fix
  24. B-Defects and bugs that can lead to incorrect functionality
  25. N-Test case and scenario creation falls in Test Design phase
  26. N-Testing processes should be regularly reviewed
  27. B-Functional testing verifies that the software behaves as expected
  28. I-Exhaustive testing is possible
  29. B-Software testing falls part of Quality Assurance