Diagnostic Testing and Fault Isolation
Start with the complaint, not the tool
Every diagnostic job begins by converting a vague customer complaint into a measurable symptom: when it occurs, under what load, temperature, speed or weather, and whether it is constant or intermittent. Then verify the fault yourself before touching anything. A technician who skips verification often repairs a fault that does not exist.
Test, do not guess
Use a logical sequence: confirm the symptom, gather data (scan tool live data, freeze-frame, DTCs), form a hypothesis, then test the hypothesis with the least invasive test first. Distinguish circuit faults (open, short to ground, short to power, high resistance) from component faults. A voltage drop test under load finds resistance faults that a simple ohmmeter misses.
Know what DTCs really mean
A diagnostic trouble code names the circuit or system the control module monitored, not the part to replace. A code for an oxygen sensor heater circuit may be caused by a blown fuse, corroded connector, chafed loom or failed heater element. Treat the code as a starting point for a test plan.
Traps in exam questions
Common traps include confusing root cause with symptom, assuming the most expensive component is at fault, ignoring intermittent faults caused by heat or vibration, and forgetting to check powers, grounds and connectors before condemning a module. Another trap is failing to confirm the repair: clear codes, run the monitor to completion and road-test.
Rule of thumb
If a circuit should carry current and does not, check supply, ground and load in that order. A 0.5 V drop across a ground connection under load is excessive; chase it before replacing anything.
Worked example
Intermittent no-crank, battery good. Measure voltage at the starter solenoid control terminal while cranking: 0 V. Back-probe the ignition switch output: 12 V. The open circuit lies between them, so inspect the connector and loom rather than replacing the starter.