Rahuldoesn'tbelieve it's acomponentissueEduardawalks intoour area andsays, "Knockknock"Unitshave tobe testedupstairsProductEngineeropens acontainmentfor limitsHong sendsan e-mailending with"Pleaseadvise."PE gives youa unit thatdoesn't workPE wantsATE tocharacterizethe unitsTom asksaboutupgradingTestStandIt's atimingissueThe unitspass onretestPaulcomplainsaboutsomethingPaulwants tocleansomethingA newoperatorneeds to beadded to thedatabaseChris asks,"Did you puta scope onit?"Heatherexpeditesan ECOLisa needsall units fora "verylate" orderSarah finds atest issue butit's actually adatasheetissueNPI needshelp withinductanceThe unitsaremanuallyapprovedIt took morethan 6 e-mailsto resolve asimpleproblemQ&Rneeds toclear aflagOperatorused thewrongfixtureOutlookgoesdownComponentEngineeringwants acustom testprogramRahuldoesn'tbelieve it's acomponentissueEduardawalks intoour area andsays, "Knockknock"Unitshave tobe testedupstairsProductEngineeropens acontainmentfor limitsHong sendsan e-mailending with"Pleaseadvise."PE gives youa unit thatdoesn't workPE wantsATE tocharacterizethe unitsTom asksaboutupgradingTestStandIt's atimingissueThe unitspass onretestPaulcomplainsaboutsomethingPaulwants tocleansomethingA newoperatorneeds to beadded to thedatabaseChris asks,"Did you puta scope onit?"Heatherexpeditesan ECOLisa needsall units fora "verylate" orderSarah finds atest issue butit's actually adatasheetissueNPI needshelp withinductanceThe unitsaremanuallyapprovedIt took morethan 6 e-mailsto resolve asimpleproblemQ&Rneeds toclear aflagOperatorused thewrongfixtureOutlookgoesdownComponentEngineeringwants acustom testprogram

Test Engineering BINGO - Call List

(Print) Use this randomly generated list as your call list when playing the game. There is no need to say the BINGO column name. 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
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
  1. Rahul doesn't believe it's a component issue
  2. Eduarda walks into our area and says, "Knock knock"
  3. Units have to be tested upstairs
  4. Product Engineer opens a containment for limits
  5. Hong sends an e-mail ending with "Please advise."
  6. PE gives you a unit that doesn't work
  7. PE wants ATE to characterize the units
  8. Tom asks about upgrading TestStand
  9. It's a timing issue
  10. The units pass on retest
  11. Paul complains about something
  12. Paul wants to clean something
  13. A new operator needs to be added to the database
  14. Chris asks, "Did you put a scope on it?"
  15. Heather expedites an ECO
  16. Lisa needs all units for a "very late" order
  17. Sarah finds a test issue but it's actually a datasheet issue
  18. NPI needs help with inductance
  19. The units are manually approved
  20. It took more than 6 e-mails to resolve a simple problem
  21. Q&R needs to clear a flag
  22. Operator used the wrong fixture
  23. Outlook goes down
  24. Component Engineering wants a custom test program