In reference to this answer to a Stack Overflow question: what is "bench-testing code"? (Not to be confused with benchmark.)
Presumably it is some kind of code that embedded inside comments and used in the context of QA/testing. But what is it exactly?
"bench testing" was used a lot in the electronics industry. It refers to testing a circuit on the work bench.
"Bench testing code" simply tests the functionality of a section of code.
Placing the actual "bench testing code" in comments provides a much more detailed description of what testing was actually performed.
In my opinion, code should only have a reference (filename) of the "bench testing code" which is maintained elsewhere.
In short, it's a synonym for unit test code.
I believe it originates from hardware design:
A hardware developer would create a device, then plug that device into a "test bench", which would then run sample inputs and verify that the output on the pins of the device was correct. It was basically the first (automated?) unit testing.
Flash forward to today, it's a synonym for something that performs unit tests. A TestFixture class in Nunit is analagous to a test bench: You "plug" your class into the TestFixture, and it does its thing similar to how a physical test bench works for hardware.