Merge branch 'cw/enhanced-outcomes-design-doc' of github.com:inspec/inspec into cw/enhanced-outcomes-design-doc

This commit is contained in:
Clinton Wolfe 2022-06-23 11:13:34 -04:00
commit c5daae36d3

View file

@ -1,58 +1,54 @@
# Enhanced Outcomes
Enhanced Outcomes refers to the addition of several new control outcomes to the InSpec vocabulary.
Enhanced Outcomes refers to the addition of new control outcomes to the InSpec vocabulary.
## Test Outcomes vs Control Outcomes
## Test Outcomes vs. Control Outcomes
It is important to be clear that Enhanced Outcomes refers to new **control outcomes** - the results of running a control. The results of running a test - a `describe block` are determined by RSpec, and are limited to Pass, Fail, and Skip. Test outcomes are much more difficult to extend than control outcomes.
It is essential to understand that Enhanced Outcomes refers to new **control outcomes**, the results of running a control.
The results of running a test, a `describe block` are determined by RSpec and are limited to `Pass`, `Fail`, and `Skip`.
Test outcomes are much more difficult to extend than control outcomes.
## New Control Outcomes
Enhanced Outcomes adds three new control outcomes to the existing Pass, Fail and Skip outcomes.
Enhanced Outcomes adds three new control outcomes to the existing `Pass`, `Fail`, and `Skip` outcomes.
### Error
The Error outcome represents the situation when the system has encountered an error when attempting to evaluate the control code. But to a technical limitation, an accurate outcome is not possible to be obtained.
In the first iteration of Enhanced Outcomes, Error outcome will be detected:
In the first iteration of Enhanced Outcomes, the Error outcome is detected:
* if the message of any test includes the text "Control source error" OR
* the result of any test includes a backtrace
then the entire control should be marked Error.
Then the entire control should be marked `Error`.
Additional means of detecting Error may be developed in the future.
Additional means of detecting error may be developed in the future.
Error's abbreviation is ERR.
Error's UI color assignment is Indigo.
Error's abbreviation is `ERR`. Error's UI color assignment is `Indigo`.
### Not Applicable
If the control is not in Error and the impact of a control is 0.0, then the control's outcome is Not Applicable.
If the control is not in `Error` and the impact of the control is `0.0`, then the control's outcome is `Not Applicable`.
Not Applicable's abbreviation is N/A.
Not Applicable's UI color assignment is Sky Blue.
Not Applicable's abbreviation is `N/A`. Not Applicable's UI color assignment is `Sky Blue`.
### Not Reviewed
If the control is not in Error or Not Applicable and all test results are Skipped, then the control outcome is Not Reviewed.
If the control is not in `Error` or `Not Applicable`, and all test results are `Skipped`, then the control outcome is `Not Reviewed`.
Not Reviewed replaces Skipped as a control outcome.
Not Reviewed replaces `Skipped` as a control outcome.
Not Reviewed's abbreviation is N/R.
Not Reviewed's abbreviation is `N/R`. Not Reviewed's UI color assignment is `Amber`.
Not Reviewed's UI color assignment is Amber.
## The --enhanced-outcomes option
## The `--enhanced-outcomes` option
A new CLI option will be introduced for `inspec exec`, `inspec shell`, and `inspec schema` that controls the Enhanced Outcomes functionality.
### InSpec 5
In InSpec 5.x, a user must request the enhanced outcomes functionality explicitly by adding the --enhanced-outcomes option.
In InSpec 5.x, a user must request the enhanced outcomes functionality explicitly by adding the `--enhanced-outcomes` option.
### InSpec 6
In InSpec 6.x, --enhanced-outcomes will default to true. A user may request disabling the enhanced outcomes functionality by adding the --no-enhanced-outcomes option.
In InSpec 6.x, --enhanced-outcomes will default to `true`. A user may request disabling the enhanced outcomes functionality by adding the `--no-enhanced-outcomes` option.