QA

QA or Quality Assurance is the final step in the Build process. Someone other than the volunteer(s) who built the machine goes over the box to ensure that it meets quality standards before donation or sale.

Verifying case integrity

Shake it

Listen for loose items, watch for things falling off.

Inspect it

• Make sure slot covers and drive bay covers are installed and tight
• Make sure case airflow is correct
• Check that vendor stickers, CPU labels, asset tags and the like are gone, Free Geek Seattle sticker is present
• Ensure case is clean, free of dust and defects

Power up the box

• There are some hardware tests that should be done but not sure if they need to be done at QA or earlier (like as part of Eval)

1. Memtest
2. SMART conveyance tests

• Does it boot?
• Can you login?
• Does everything work (i.e., networking, sound, video)?

What's Needed

• Setup station (Keyboard, mouse, monitor speakers or headphones, power, network connection)
• Live media or access to Install Server
• Slot blanks or tape
• FGSEA stickers
• Basic toolkit

Procedure

Source: http://wiki.freegeek.org/index.php/QC_checklist

1. Check that the case is closed and secure.
   1. If not, open it and check that:
   2. components are properly connected
   3. the interior is dust-free
   4. cables are tucked out of the way
   5. airflow path is unobstructed
   6. if any of above is not true, send unit back to builder.
   7. close and fasten the case.
2. Pick up the case and move it around, check for rattling sounds. If there's loose stuff inside, open up and take it out.
3. Ensure all slots, bays and ports are covered
   1. Cover ports that don't work with electrical tape. We have slot covers for empty slots.
4. Power on the machine. If it doesn't POST, send it back.
   1. Enter BIOS and ensure settings are correct (ask workshop lead if you don't know what settings are correct)
5. Boot from HDD. Does gdm greeter screen come up?
6. Reboot, this time from PXE (if supported) and run the automated test tools we haven't built yet :^/
   1. Harass the relevant Working Groups about that. If there aren't any, form one.