Developersshould testtheir owncodeEnhancedquality isachieved byworkingtogetherNon-functionaltestingassesses howwell a productbehavesIncrementaltesting is aform ofIntegrationtestingTestingprocessesshould beregularlyreviewedRetesting iswhen testersensure bugsfound arefixedFunctionaltesting verifiesthat thesoftwarebehaves asexpectedLack of testdata ischallengingfor testers"It's not abug. It's afeature."The pros faroutweighsthe cons inautomatedtestingRunningthe sametests findsmore bugsDefects andbugs thatcan lead toincorrectfunctionalitySoftwaretesting fallspart ofQualityAssuranceCollaborationbetween Devsand QAsencouragescreativity andinnovationSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itTight deadlinesoften limit thetime availablefor thoroughtestingBusiness-critical testscases shouldbeautomatedKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveCollaborationencouragescreativity andinnovationExhaustivetesting ispossibleTesting cannot provethe absenceof bugsTheenvironment forautomationneeds to beisolated andcontrolledBoth test casesand test scenariosare crucial inensuring a smoothtesting processTestersshould thinklikedevelopers tobe successfulPerformancetesting ispart of non-functionaltestingAutomateeverything!Test caseand scenariocreation fallsin TestDesign phaseBugs foundin postdeploymentis cheaper tofix"It workson mylocal"Developersshould testtheir owncodeEnhancedquality isachieved byworkingtogetherNon-functionaltestingassesses howwell a productbehavesIncrementaltesting is aform ofIntegrationtestingTestingprocessesshould beregularlyreviewedRetesting iswhen testersensure bugsfound arefixedFunctionaltesting verifiesthat thesoftwarebehaves asexpectedLack of testdata ischallengingfor testers"It's not abug. It's afeature."The pros faroutweighsthe cons inautomatedtestingRunningthe sametests findsmore bugsDefects andbugs thatcan lead toincorrectfunctionalitySoftwaretesting fallspart ofQualityAssuranceCollaborationbetween Devsand QAsencouragescreativity andinnovationSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itTight deadlinesoften limit thetime availablefor thoroughtestingBusiness-critical testscases shouldbeautomatedKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveCollaborationencouragescreativity andinnovationExhaustivetesting ispossibleTesting cannot provethe absenceof bugsTheenvironment forautomationneeds to beisolated andcontrolledBoth test casesand test scenariosare crucial inensuring a smoothtesting processTestersshould thinklikedevelopers tobe successfulPerformancetesting ispart of non-functionaltestingAutomateeverything!Test caseand scenariocreation fallsin TestDesign phaseBugs foundin postdeploymentis cheaper tofix"It workson mylocal"

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