Retesting iswhen testersensure bugsfound arefixedDefects andbugs thatcan lead toincorrectfunctionalitySoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedEnhancedquality isachieved byworkingtogetherCollaborationbetween Devsand QAsencouragescreativity andinnovation"It's not abug. It's afeature."Test caseand scenariocreation fallsin TestDesign phaseCollaborationencouragescreativity andinnovationThe pros faroutweighsthe cons inautomatedtestingTheenvironment forautomationneeds to beisolated andcontrolledIncrementaltesting is aform ofIntegrationtestingFunctionaltesting verifiesthat thesoftwarebehaves asexpectedTesting cannot provethe absenceof bugsRunningthe sametests findsmore bugsTight deadlinesoften limit thetime availablefor thoroughtestingTestersshould thinklikedevelopers tobe successfulNon-functionaltestingassesses howwell a productbehavesDevelopersshould testtheir owncodeTestingprocessesshould beregularlyreviewedExhaustivetesting ispossibleAutomateeverything!Lack of testdata ischallengingfor testersBugs foundin postdeploymentis cheaper tofixKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensive"It workson mylocal"Performancetesting ispart of non-functionaltestingBoth test casesand test scenariosare crucial inensuring a smoothtesting processRetesting iswhen testersensure bugsfound arefixedDefects andbugs thatcan lead toincorrectfunctionalitySoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedEnhancedquality isachieved byworkingtogetherCollaborationbetween Devsand QAsencouragescreativity andinnovation"It's not abug. It's afeature."Test caseand scenariocreation fallsin TestDesign phaseCollaborationencouragescreativity andinnovationThe pros faroutweighsthe cons inautomatedtestingTheenvironment forautomationneeds to beisolated andcontrolledIncrementaltesting is aform ofIntegrationtestingFunctionaltesting verifiesthat thesoftwarebehaves asexpectedTesting cannot provethe absenceof bugsRunningthe sametests findsmore bugsTight deadlinesoften limit thetime availablefor thoroughtestingTestersshould thinklikedevelopers tobe successfulNon-functionaltestingassesses howwell a productbehavesDevelopersshould testtheir owncodeTestingprocessesshould beregularlyreviewedExhaustivetesting ispossibleAutomateeverything!Lack of testdata ischallengingfor testersBugs foundin postdeploymentis cheaper tofixKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensive"It workson mylocal"Performancetesting ispart of non-functionaltestingBoth test casesand test scenariosare crucial inensuring a smoothtesting process

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