Rahuldoesn'tbelieve it's acomponentissueSarah finds atest issue butit's actually adatasheetissueTom asksaboutupgradingTestStandLisa needsall units fora "verylate" orderA newoperatorneeds to beadded to thedatabaseOperatorused thewrongfixtureUnitshave tobe testedupstairsIt took morethan 6 e-mailsto resolve asimpleproblemPE gives youa unit thatdoesn't workChris asks,"Did you puta scope onit?"Paulwants tocleansomethingComponentEngineeringwants acustom testprogramQ&Rneeds toclear aflagThe unitspass onretestThe unitsaremanuallyapprovedNPI needshelp withinductanceOutlookgoesdownProductEngineeropens acontainmentfor limitsPaulcomplainsaboutsomethingEduardawalks intoour area andsays, "Knockknock"Hong sendsan e-mailending with"Pleaseadvise."PE wantsATE tocharacterizethe unitsHeatherexpeditesan ECOIt's atimingissueRahuldoesn'tbelieve it's acomponentissueSarah finds atest issue butit's actually adatasheetissueTom asksaboutupgradingTestStandLisa needsall units fora "verylate" orderA newoperatorneeds to beadded to thedatabaseOperatorused thewrongfixtureUnitshave tobe testedupstairsIt took morethan 6 e-mailsto resolve asimpleproblemPE gives youa unit thatdoesn't workChris asks,"Did you puta scope onit?"Paulwants tocleansomethingComponentEngineeringwants acustom testprogramQ&Rneeds toclear aflagThe unitspass onretestThe unitsaremanuallyapprovedNPI needshelp withinductanceOutlookgoesdownProductEngineeropens acontainmentfor limitsPaulcomplainsaboutsomethingEduardawalks intoour area andsays, "Knockknock"Hong sendsan e-mailending with"Pleaseadvise."PE wantsATE tocharacterizethe unitsHeatherexpeditesan ECOIt's atimingissue

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