As a Tester, I need Field Validation in Test Runs and Executions

Analyze the possibility of adding Field Validation within Test Runs.

For instance, numerical validation:
"someone writing a test can specify that the expected result is a number with an acceptable range of values. Ranges could be specified with lower and upper bounds (e.g., 4 to 6), via tolerance (e.g., 5 +/- 1), or as an operator (e.g.,>, <, <=, etc.). When the test is run, a value must be entered into the Actual Result field (or a test run custom field configured by the user). Xray would compare the actual result value to the expected result value. If the expected result is satisfied, the step auto passes. If the expected result is not satisfied, the step auto fails, and a defect is required."

This can also include other data types like strings, dates, etc.:
"the expected result could be specified to be an exact string. The actual result entered by the user is then compared to the expected string."

The functionality should be configurable on a step-by-step basis:
"For example, in a 10-step test, only steps 2 and 10 require this functionality; the remaining steps function the same way Xray currently functions."