#163 Code coverage is computed even if shell variable SASUNIT_COVERAGEASSESSMENT is set to 0

[Johannes Lang]

In the SASUnit batch start script, the shell parameter SASUNIT_COVERAGEASSESSMENT is set to 0.
But the code coverage metrics are computed anyway, see attached screenshot.

If the parameter SASUNIT_COVERAGEASSESSMENT is set to 0, these statistics should not be computed.

[Johannes Lang]

Thanks to Klaus Landwich, I know now what the cause was: The parameter must be passed to the %initSASUnit macro, which has a corresponding parameter i_testcoverage.

But nevertheless, I think there should be an improvement:
- When the shell parameter SASUNIT_COVERAGEASSESSMENT is defined, but the macro parameter i_testcoverage is not filled, SASUnit should issue a warning that indicates this missing link.
- And/Or: SASUnit should report the passed value of the macro parameter i_testcoverage on the overview report page.
- These suggestions also apply for other parameters which are handled this way. The SASUnit user does not automatically know that shell parameters must be manually mapped to %initSASUnit macro parameters in order to work properly.

Any comments?

[Klaus Landwich]

Yep,

there you ar definitely right.

I will issue a warning if a shell parameter differs from the passed parameter.
Also I will add both values in the over page.