Testing paradigms for consumer electronics
I can answer this for my particular experience in ECE. Digital design, embedded design, and system design. Essentially we do all the same tests as software folks.

Design reviews
We have manual reviews of designs for digital implementations, PCBs, and analog circuits. Similar to code reviews. For embedded designs, the embedded code is reviewed similarly to software. For digital designs the HDL is evaluated the same way.

Static analysis
There is a lot of automated error checking for certain design processes. For the most part, they are the same but require a lot more design specific settings for the rules. Design rule checks (DRCs) for PCBs and design constraints for analog design come to mind. 

Block tests
This probably most closely relates to unit tests. The electrical design is segmented into blocks for design and testing. The block has known inputs and corresponding desired outputs. A block test will confirm that this sub-set of the design is working properly.

System tests
The obvious next step from successful block tests are system tests, similar to integration testing. The blocks are connected in a logical sequence to ensure the entire design works as expected.

Functional tests
This would be analogous to user testing. Certain common uses are tested to ensure the sequence of use doesn't break the design.

Performance tests
Quite commonly we need to test whether the design is not drawing too much power or getting too hot through regular use. This is especially important in my field of implanted medical electronics. 

Security tests
This may be a little less common. Hacking hardware is fairly common. The only test I have designed and performed here had to do with ensuring certain parts of the ROM in a MCU design could not be read externally. Otherwise things like adding that black resin over an ASIC is fairly good security to minimally protect designs.

Smoke tests
Also quite common. In fact, as you might have guessed, this test gets its name from hardware testing. Hardware can go up in smoke literally.



The final two are probably only applicable to hardware and don't have analogous testing done in software.

Environmental testing
For "non-functional" testing, we make sure the device works in the specified environment. Temperature is at least tested, humidity less often. There are lots of things in electronics with a temperature coefficient, we have to test in the range of specified use to make sure that coefficient isn't going to mess with performance or functionality.

Testing selection
This depends on the industry. For implanted medical devices we test every component as well as every completed device. For something like graphics cards, cherry picking of the final products is preferred.