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.

Sign up for GitHub

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

Jump to bottom

Add an example how plugin configuration parameters could be read #2

Open
szpak opened this issue Aug 10, 2015 · 1 comment · May be fixed by #4
Open

Add an example how plugin configuration parameters could be read #2

szpak opened this issue Aug 10, 2015 · 1 comment · May be fixed by #4

Comments

@szpak
Copy link
Contributor

szpak commented Aug 10, 2015

To make it a little bit easier people wanting to use that feature.

There could be a new simple plugin which reads all plugin configuration parameters and print them (which could be potentially useful also in functional tests in Maven/Gradle builds) + a link to the plugin in documentation.
szpak added a commit to szpak/pitest-plugins that referenced this issue Sep 8, 2015
@szpak
[hcoles#2] Add plugin configuration reporter plugin
fb39a6c 
Artificial plugin created for acceptance tests in Gradle module.
@szpak szpak linked a pull request Sep 8, 2015 that will close this issue
Open
@szpak
Copy link
Contributor Author

szpak commented Sep 5, 2017

@hcoles In addition to old (legacy?) plugin parameters (#4) it would be good to also have another plugin with some features (hcoles/pitest#365) provided to use it in integration/functional tests for the Gradle plugin.

@szpak szpak mentioned this issue Aug 16, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[#2] Add plugin configuration reporter plugin szpak/pitest-plugins
1 participant
@szpak