A console test log should survive the question: what did you actually try?

Prepare the console and your own test kit

"Fully tested" is the most popular phrase in used console listings and one of the least meaningful. A console has a display output, controllers, storage, media drive (on many models), wireless radios, ports, fans and an account system. Reaching the home screen tests a small fraction of that list.

Before you plug anything in, assemble a known-good test kit so a failure points at the console, not at your cables: a display you know works, a compatible power cable or adapter, a known-good display cable, at least one controller you know works, a game disc or cartridge you know works (for models that take physical media) and a network you control.

Read the exact model and revision from the label on the console. A disc-based model, a digital-only revision and a handheld hybrid do not share a function list, so your test matrix should be written for this model, not for "a console."

Stop sign: Do not power on a console with a damaged power cord or port, a cracked case near the power supply, swelling, a burning smell or signs of liquid damage. Do not open energized equipment, bypass a fault or attempt an unfamiliar repair to make a demo video. Set it aside as an unresolved item.

Inspect the console before it runs

Look at the case, vents, ports and media slot with a flashlight. Note cracks, bent or broken port pins, missing feet, stickers and heavy dust in vents. Photograph the label with the model number and the ports.

Write down what is physically included in the sale: console, power cable, display cable, controllers (with their model numbers), stand, original box. Keep this list separate from your test kit. If you tested with your own controller or cable, that does not make it part of the buyer's package.

Run a test matrix with three outcomes

Mark each line checked and working, failed or not assessed. Here is a starting matrix; delete lines that do not apply to the model and add any it has:

A successful launch is narrower evidence than a full game session, and a full session is narrower than "every port works." Write intermittent faults down, even if they only happened once.

Worked example: a 30-minute budget does not finish every test

Choose ten minutes for identification and inspection, ten for operation checks and ten for notes and photographs. That is 30 planned active minutes. In the example console, only the display and home screen were observed in that time; the disc drive, second controller and wireless connection were not assessed.

When the time runs out, unassessed functions stay unassessed. The budget is a planning tool, not permission to mark the matrix complete, and one observed line out of four does not support "fully tested."

Remove accounts and data as a separate step

Account removal is not a hardware test, and it is not optional. Follow the console maker's official instructions to sign out, remove the console as a primary or home device where applicable, and restore it to factory settings. Then confirm it boots to the initial setup screen. The device wiping guide covers the general order.

Do not include an existing account or a downloaded library as a "bonus." Accounts and digital purchases are governed by the platform's terms and are not automatically transferable with the hardware.

Write the listing from the matrix and pack it

Turn the matrix into plain sentences: what you checked, what you saw, what you did not check. Photograph the console from all sides, the ports, the label and every included accessory. The video games guide covers games you might bundle.

Then pack. Many controllers and handheld consoles contain lithium batteries, and USPS Publication 52 sets out specific rules for batteries and devices containing them. Read the current rules and the used-electronics shipping guide before you choose a service.

Common mistakes:

• Testing with your own controller, then shipping a different one.
• Writing "fully tested" after a boot check.
• Forgetting to remove the console from your account.
• Not listing which ports you checked.

A precise test log is more valuable than a sweeping adjective. Finish with a supported contents list, disclosed limits and a carrier-compliant shipment plan, including any applicable battery rules.