Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implicitly activate debug flag when code coverage is activated #365

Open
dennis-behm opened this issue Jun 12, 2023 · 0 comments
Open

Implicitly activate debug flag when code coverage is activated #365

dennis-behm opened this issue Jun 12, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@dennis-behm
Copy link
Member

Customer feedback:

Since the --debug parameter is always required when the -cc parameter is specified, why not just activate the --debug parameter whenever the -cc parameter is specified and NOT have the user have to also specify it? It would be clearer (+cleaner) to me if the user just had to specify one parameter to activate Code Coverage.

The existing implementation does not implement the dependency between the two options and the debug flag could be turned on when -cc is passed:

dbb-zappbuild/build.groovy

Lines 424 to 434 in 85e0df0

// set code coverage flag
if (opts.cc) {
props.codeZunitCoverage = 'true'
if (opts.cch && opts.ccp) {
props.codeCoverageHeadlessHost = opts.cch
props.codeCoverageHeadlessPort = opts.ccp
}
if (opts.cco) {
props.codeCoverageOptions = opts.cco
}
}

@dennis-behm dennis-behm added the enhancement New feature or request label Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant