ITAD Glossary
Device Testing
ITAD
Also known as: functional testing · functionality testing · test and repair · hardware testing · diagnostics testing · battery testing
Device testing checks whether the relevant functions of used IT equipment work before it is considered for reuse. The scope depends on the equipment and intended use. A device test is separate from data sanitization.
What gets tested
| Component | Typical check | Why it matters |
|---|---|---|
| Battery | Read the battery's smart chip for full-charge capacity against original design capacity, plus cycle count; run a load test when the chip can't be read accurately | A worn battery cuts resale value, and a damaged one is a safety risk |
| Memory (RAM) | Confirm installed capacity and run a memory diagnostic | Faulty memory causes crashes that a quick power-on check won't reveal |
| Storage (HDD and SSD) | Check SMART health status, run read/write and bad-sector checks | Drives are the part most likely to fail in used equipment |
| Display and video | Look for dead pixels, backlight and hinge faults; test the graphics output, including to an external display | Screen defects are visible to every buyer and costly to repair |
| Ports, keyboard, touchpad, camera, audio | Exercise each input and output | A single dead port or key lowers the grade |
| Wireless | Connect to Wi-Fi and Bluetooth; cellular on phones and tablets | Connectivity is a key function on most devices |
| Locks | Check for Activation Lock, MDM enrollment and BIOS passwords | A locked device cannot be reused until the owner releases it |
Confirm the applicable testing scope
Ask how the provider documents tests, grades devices and routes equipment that fails. When certification matters to your project, review the current facility certificate and the relevant process scope. For R2, see SERI’s R2 Standard resources.
Testing does not erase data
Testing and data sanitization are separate steps. A device can pass every hardware test and still hold your data, so a test report never replaces a sanitization record.
What a test report should show
- Serial number and asset tag for each device
- Pass or fail for each component tested
- Battery capacity as a percentage of design capacity
- Drive health result and the sanitization method used
- The resulting grade, the testing tool, the technician and the date
Question to ask your ITAD provider
What do you test on each device, and can we see per-serial results, including battery capacity as a percentage of design capacity?
Expect a report listing each device by serial number with pass or fail results for battery, memory, storage, display and video, ports and wireless, the battery's capacity against its design capacity, the drive health result, the grade assigned, and who tested it and when. Testing should be recorded separately from data sanitization.
Source: e-Stewards Standard V4.1 (PDF)