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

Starting single integration test by gradle inside IDE does not use developer settings #3830

Closed
de-jcup opened this issue Jan 27, 2025 · 0 comments · Fixed by #3822
Closed
Assignees

Comments

@de-jcup
Copy link
Member

de-jcup commented Jan 27, 2025

Situation

With

it became clear that the filtering of integration tests is a problem for local IDE gradle based exeuction of tests.

While fixing it, another problem appeared:

~/.sechub/sechub-developer.properties
containing:
sechub.integrationtest.running=true

were still skipped after the fix.

Analyze

The reason is, that the files are not fetched in case of gradle builds, means also local gradle builds.
This comes very inconvenient and is also extreme confusing.

Wanted

A gradle build shall search for the ~/.sechub/sechub-developer.properties as well.
If its not existing, nothing shall happen.

Solution

Remove the special gradle handling

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant