Performancetesting ispart of non-functionaltestingFunctionaltesting verifiesthat thesoftwarebehaves asexpectedEnhancedquality isachieved byworkingtogetherBugs foundin postdeploymentis cheaper tofixTheenvironment forautomationneeds to beisolated andcontrolledIncrementaltesting is aform ofIntegrationtesting"It's not abug. It's afeature."Retesting iswhen testersensure bugsfound arefixedNon-functionaltestingassesses howwell a productbehavesKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveThe pros faroutweighsthe cons inautomatedtestingTesting cannot provethe absenceof bugsRunningthe sametests findsmore bugsTestingprocessesshould beregularlyreviewedTight deadlinesoften limit thetime availablefor thoroughtestingAutomateeverything!Exhaustivetesting ispossibleDevelopersshould testtheir owncodeSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itTest caseand scenariocreation fallsin TestDesign phaseBoth test casesand test scenariosare crucial inensuring a smoothtesting process"It workson mylocal"Defects andbugs thatcan lead toincorrectfunctionalityLack of testdata ischallengingfor testersCollaborationencouragescreativity andinnovationTestersshould thinklikedevelopers tobe successfulSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedCollaborationbetween Devsand QAsencouragescreativity andinnovationPerformancetesting ispart of non-functionaltestingFunctionaltesting verifiesthat thesoftwarebehaves asexpectedEnhancedquality isachieved byworkingtogetherBugs foundin postdeploymentis cheaper tofixTheenvironment forautomationneeds to beisolated andcontrolledIncrementaltesting is aform ofIntegrationtesting"It's not abug. It's afeature."Retesting iswhen testersensure bugsfound arefixedNon-functionaltestingassesses howwell a productbehavesKeeping testcases relevantand efficient asthe softwareevolves can belabor-intensiveThe pros faroutweighsthe cons inautomatedtestingTesting cannot provethe absenceof bugsRunningthe sametests findsmore bugsTestingprocessesshould beregularlyreviewedTight deadlinesoften limit thetime availablefor thoroughtestingAutomateeverything!Exhaustivetesting ispossibleDevelopersshould testtheir owncodeSoftware testingtries to increaseconfidence in aproduct bypointing out whatis wrong with itTest caseand scenariocreation fallsin TestDesign phaseBoth test casesand test scenariosare crucial inensuring a smoothtesting process"It workson mylocal"Defects andbugs thatcan lead toincorrectfunctionalityLack of testdata ischallengingfor testersCollaborationencouragescreativity andinnovationTestersshould thinklikedevelopers tobe successfulSoftwaretesting fallspart ofQualityAssuranceBusiness-critical testscases shouldbeautomatedCollaborationbetween Devsand QAsencouragescreativity andinnovation

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