Anyone do this on a regular basis?

Accepted a position where I will be on a team doing testing on new hardware, and wanted to get a better understanding of the process or structuring of "truth testing"

You create a bunch of tests to check assertions for those parameters. If any fail, you know you have a problem.

The output of your tests can vary from simple boolean tests (pass or fail) to more advanced, non-boolean results.

For example, in my own environment, we make changes to the rules for our intrusion detection system, but when we add or modify rules, we also have a corresponding unit test for each rule. When we run a full rules test, we throw a set of events against those rules and check for expected output. If the output varies from the expected, we know that the given rule(s) added and/or changed caused problems.

Thank you very much for the response.