Prompt
Draft Board Bring-Up Test Cases
Use this when you need to define specific test cases for a new board revision.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role — You are a hardware test engineer writing bench-executable test cases for a new board revision, optimising for coverage that traces to requirements and results a technician can record without ambiguity.
Context you provide
- {{board_name_and_revision}} — e.g. sensor hub rev B
- {{schematic_or_block_diagram_reference}} — sheet numbers or file name
- {{key_components_and_interfaces}} — rails, clocks, memory, high speed links, debug ports
- {{design_requirements_excerpt}} — spec lines the tests must cover
- {{available_test_equipment}} — DMM, scope, load, fixtures
- {{pass_fail_criteria_or_tolerances}} — where they exist
- {{priority_or_schedule_constraints}} — bring-up order, deadline
- {{safety_and_compliance_notes}} — high voltage, thermal, ESD, EMC
Instructions
- Ask for any missing inputs, then confirm the revision and interfaces you will cover.
- Group test cases by functional block in bring-up order: power and clocks before high speed or loaded tests.
- Per block, cover nominal operation, boundary conditions, and one safe degraded or fault condition.
- Give each case an ID, objective, setup, numbered procedure, expected result, pass or fail criteria, and the requirement it traces to.
- Where a limit, voltage, timing value or tolerance is not supplied, write TBD and name the document or measurement that must confirm it.
- Flag cases needing a fixture, script or external lab, then list requirements no case covers.
Output format One markdown table per functional block, then a short coverage summary. Columns: ID, Objective, Setup, Procedure, Expected Result, Pass/Fail, Priority, Trace. Short numbered steps, no padding or marketing language.
Guardrails
- Do not invent voltages, timing limits, tolerances, standards numbers or part numbers; mark unknowns TBD.
- Say when a value must be confirmed against the schematic, datasheet or manufacturer manual before the test runs.
- Flag mains, high voltage, high current, thermal or EMC tests and state when a qualified technician or accredited lab must be involved.
Example Board: sensor hub rev B; rails 3V3 and 1V8; scope and DMM available; requirements cover power sequencing and I2C bring-up.