Functional testing verifies that a circuit board assembly does what it's supposed to do. Not just that the right components are placed correctly—that's what in-circuit testing checks—but that the assembled board actually performs its intended function.
It's the closest thing to testing your product the way an end user would experience it, but automated and repeatable.
What functional testing covers#
A functional test exercises the board through its normal operating modes. Depending on the product, that might include:
- Power-up sequencing — verify voltage rails come up in the correct order and settle within spec
- Communication interfaces — confirm UART, SPI, I2C, USB, or Ethernet links respond correctly
- Sensor inputs — stimulate sensors or provide known inputs and verify the board's response
- Actuator outputs — trigger relays, motors, or LEDs and confirm they activate
- Firmware validation — program the board and run self-test routines
The key distinction: functional testing treats the board as a system, not as a collection of individual components.
Functional testing vs. other methods#
Each testing method answers a different question:
| Method | Primary question | What it catches |
|---|---|---|
| Functional test (FCT) | Does the board work? | System-level failures, firmware bugs, integration issues |
| In-circuit test (ICT) | Are the components correct? | Wrong values, missing parts, solder defects |
| Flying probe | Are the connections right? | Opens, shorts, component presence |
| Boundary scan | Are the digital connections intact? | JTAG-accessible net failures |
They're complementary, not competing
Most production test strategies combine methods. ICT catches assembly defects fast; functional testing catches the system-level issues ICT can't see. The question isn't which one—it's which combination fits your volume and board complexity.
When functional testing is the right fit#
Functional testing makes the most sense when:
- Your board has active firmware — microcontrollers, FPGAs, or processors that need to run code as part of the test
- System behavior matters — the board's value comes from how subsystems interact, not just whether individual components are present
- You're at low-to-medium volume — functional test fixtures are simpler and less expensive than full ICT, making them practical even for hundreds of units
- ICT isn't feasible — dense boards with limited test access may not support ICT, but can still be functionally tested through connectors and interfaces
What you need for functional testing#
A typical functional test setup includes:
- A test fixture — provides mechanical alignment and electrical contact to the board's test points and connectors
- Test instrumentation — power supplies, multimeters, signal generators, and communication adapters
- Test software — scripts or programs that orchestrate the test sequence, collect measurements, and determine pass/fail
- A test specification — defines what gets tested, acceptance criteria, and the test flow
The fixture is the physical interface between your board and the test system. For bed-of-nails functional testing, pogo pins contact test points on the board while the test software runs through the verification sequence.
Getting started#
If you're setting up functional testing for the first time, start with these steps:
- Define your critical functions — list what the board must do, prioritized by failure impact
- Map your test access — identify which signals you can reach through test points and connectors
- Choose your instrumentation — match measurement needs to available equipment
- Write your test sequence — start with power verification, then work through subsystems
Ready to set up functional testing?
Configure a test fixture for your board and get a quote in minutes.