-
Notifications
You must be signed in to change notification settings - Fork 3
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
Upgrade pitest-maven-plugin 1.7.6 -> 1.16.0 #274
Open
Picnic-Bot
wants to merge
1
commit into
master
Choose a base branch
from
renovate/pitest-maven-plugin-1.x
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Suggested commit message:
|
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.14.1
Upgrade pitest-maven-plugin 1.7.6 -> 1.14.2
Jun 25, 2023
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
June 25, 2023 22:06
3e91112
to
ca6e8b3
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.14.2
Upgrade pitest-maven-plugin 1.7.6 -> 1.14.3
Aug 10, 2023
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
August 10, 2023 22:02
ca6e8b3
to
e810d86
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.14.3
Upgrade pitest-maven-plugin 1.7.6 -> 1.14.4
Aug 17, 2023
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
August 17, 2023 22:02
e810d86
to
4eace71
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.14.4
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.0
Sep 24, 2023
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
September 24, 2023 22:02
4eace71
to
5ac543d
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.0
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.1
Oct 11, 2023
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
October 11, 2023 04:22
5ac543d
to
50bff3c
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.1
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.2
Oct 25, 2023
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
October 25, 2023 22:02
50bff3c
to
49bc09a
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.2
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.3
Nov 1, 2023
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
November 1, 2023 23:02
49bc09a
to
b06fe87
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.3
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.4
Jan 21, 2024
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
January 21, 2024 23:02
b06fe87
to
f20c82b
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.4
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.6
Jan 24, 2024
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
January 24, 2024 23:03
f20c82b
to
b7e8105
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.6
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.7
Feb 6, 2024
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
February 6, 2024 23:03
b7e8105
to
bd1b770
Compare
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.7
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.8
Feb 13, 2024
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
February 13, 2024 23:02
bd1b770
to
0564255
Compare
See: - https://github.com/hcoles/pitest/releases/tag/1.16.0 - https://github.com/hcoles/pitest/releases/tag/1.15.8 - https://github.com/hcoles/pitest/releases/tag/1.15.7 - https://github.com/hcoles/pitest/releases/tag/1.15.6 - https://github.com/hcoles/pitest/releases/tag/1.15.5 - https://github.com/hcoles/pitest/releases/tag/1.15.4 - https://github.com/hcoles/pitest/releases/tag/1.15.3 - https://github.com/hcoles/pitest/releases/tag/1.15.2 - https://github.com/hcoles/pitest/releases/tag/1.15.1 - https://github.com/hcoles/pitest/releases/tag/1.15.0 - https://github.com/hcoles/pitest/releases/tag/1.14.4 - https://github.com/hcoles/pitest/releases/tag/1.14.3 - https://github.com/hcoles/pitest/releases/tag/1.14.2 - https://github.com/hcoles/pitest/releases/tag/1.14.1 - https://github.com/hcoles/pitest/releases/tag/1.14.0 - https://github.com/hcoles/pitest/releases/tag/1.13.2 - https://github.com/hcoles/pitest/releases/tag/1.13.1 - https://github.com/hcoles/pitest/releases/tag/1.13.0 - https://github.com/hcoles/pitest/releases/tag/1.12.0 - https://github.com/hcoles/pitest/releases/tag/1.11.7 - https://github.com/hcoles/pitest/releases/tag/1.11.6 - https://github.com/hcoles/pitest/releases/tag/1.11.5 - https://github.com/hcoles/pitest/releases/tag/1.11.4 - https://github.com/hcoles/pitest/releases/tag/1.11.3 - https://github.com/hcoles/pitest/releases/tag/1.11.2 - https://github.com/hcoles/pitest/releases/tag/1.11.1 - https://github.com/hcoles/pitest/releases/tag/1.11.0 - https://github.com/hcoles/pitest/releases/tag/1.10.4 - hcoles/pitest@1.10.2...1.10.3 - hcoles/pitest@1.10.1...1.10.2 - https://github.com/hcoles/pitest/releases/tag/1.10.1 - https://github.com/hcoles/pitest/releases/tag/1.10.0 - https://github.com/hcoles/pitest/releases/tag/1.9.11 - https://github.com/hcoles/pitest/releases/tag/1.9.10 - https://github.com/hcoles/pitest/releases/tag/1.9.9 - https://github.com/hcoles/pitest/releases/tag/1.9.8 - hcoles/pitest@1.9.6...1.9.7 - https://github.com/hcoles/pitest/releases/tag/1.9.6 - https://github.com/hcoles/pitest/releases/tag/1.9.5 - https://github.com/hcoles/pitest/releases/tag/1.9.4 - https://github.com/hcoles/pitest/releases/tag/1.9.3 - https://github.com/hcoles/pitest/releases/tag/1.9.2 - https://github.com/hcoles/pitest/releases/tag/1.9.1 - https://github.com/hcoles/pitest/releases/tag/1.9.0 - https://github.com/hcoles/pitest/releases/tag/1.8.1 - https://github.com/hcoles/pitest/releases/tag/1.8.0
Picnic-Bot
changed the title
Upgrade pitest-maven-plugin 1.7.6 -> 1.15.8
Upgrade pitest-maven-plugin 1.7.6 -> 1.16.0
Apr 9, 2024
Picnic-Bot
force-pushed
the
renovate/pitest-maven-plugin-1.x
branch
from
April 9, 2024 22:04
0564255
to
fa8dc4c
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. ⚠ Warning: custom changes will be lost. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.7.6
->1.16.0
Release Notes
hcoles/pitest (pitest-maven-plugin)
v1.16.0
Compare Source
+funmodifiablecollection
filter for defensive codeApi change in #1321 is backwards compatible, but plugins written against 1.16.0 may not work with earlier versions.
v1.15.8
Compare Source
#1310 Filter mutations to Collections.unmodifiable*
#1309 Replace fields in argLines imported from surefire config
#1308 Bump maven vcs versions
The filtering for #1310 is off by default. To activate it add the filter string
+funmodifiablecollection
.#1309 adds a new maven property
parseSurefireArgLine
. This is set to true by default, but surefire argline parsing can now be disabled by setting it to false.v1.15.7
Compare Source
#1305 Coverage not recorded for code in packages name com.sun*
A filter intended to pickup legacy JDK classes in the "com.sun.*" package was missing a
'
, resulting in no code coverage being registered if the code under test happened to be in a package starting with "sun".v1.15.6
Compare Source
Invoke dynamic call tracking for static initializer code will be reintroduced when additional logic to suppress mutation filtering for delayed execution code has been implemented.
v1.15.5
Compare Source
v1.15.4
Compare Source
Note, maven users who have previously needed to duplicate argline parameters between surefire and pitest's jvmArgs and argline parameters may need to adjust their configuration when upgrading. Entries supplied to surefire will now automatically be added to pitest.
v1.15.3
Compare Source
v1.15.2
Compare Source
#1267 will ensure that previously hidden errors encountered by the JUnit5 plugin will now be reported. This is a backwards compatible api change. It will have no effect until the JUnit5 plugin is updated to use the expanded api. The updated plugin will not be compatible with earlier versions of pitest.
v1.15.1
Compare Source
v1.15.0
Compare Source
extrafeatures
param for maven to allow features to be added on commandline without overwriting existing list#1251 updates several existing interfaces. Plugins (eg the arcmutate kotlin plugin) using these interfaces must also be updated when upgrading.
v1.14.4
Compare Source
v1.14.3
Compare Source
v1.14.2
Compare Source
#1221 - Unified percentage calculate (thanks @Vampire)
#1218 - Thread safety for results collection when tests run in parallel (thanks @Vampire)
#1225 - Prevent error when non archive files included on classpath
#1229 - Mutate Iterables to emptyList
#1227/1232 - Fix MethodMutator interface to depend on abstract types
v1.14.1
Compare Source
v1.14.0
Compare Source
#1212 Largely resolves the issue of keeping the pitest-junit5-plugin version in sync with the junit5 version for maven users.
When used with 1.2.0 of the pitest-junit5-plugin, pitest will now automatically select a version of junit-platform-launcher which is compatible with the version of junit5 used by the system under test.
Issues remain for gradle users who may still encounter api compatibilities when using 1.2.0 of the pitest-junit5-plugin. These can however now be resolved by manually adding the correct version of junit-platform-launcher to the classpath.
It is hoped that a future version of the pitest gradle plugin will implement a fix similar to the pitest-maven solution.
v1.13.2
Compare Source
v1.13.1
Compare Source
**.
pattern in globs (thanks @Pfoerd)v1.13.0
Compare Source
v1.12.0
Compare Source
Adds new extension points to allow plugins to make changes in the environment in which tests are run.
v1.11.7
Compare Source
#1178 Commas in killing test name break csv export (thanks @Bonajo)
#1177 Apply features in a consistent order
#1176 Upgrade to ASM 9.5
v1.11.6
Compare Source
#1171 Prevent double instantiation of features
#1170 Update links to https (thanks @romani)
v1.11.5
Compare Source
v1.11.4
Compare Source
#1161 Prevent duplicate clinit when synthetic clinit present
#1162 Auto add kotlin source dirs to maven when present
v1.11.3
Compare Source
The line coverage data displayed on the console previously included all targetted
code, while the figures shown in the report were implicitly limited to mutated classes.
This caused considerable confusion.
The console stats are now also limited to include only mutated classes.
v1.11.2
Compare Source
The line coverage stats reported on the console included code lines for the entire project, even when filters were applied. This resulted in dramatically low coverage scores.
v1.11.1
Compare Source
#1156 Prevent synthetic lines being counted in coverage
Synthetic methods were being included in the line coverage calculations resulting in an over calculation of coverage. For some kotlin classes this could result in more code lines having coverage than actually existed in a file. #1156 fixes this, but still intstruments the synthetic methods used to implement lambdas in java classes.
v1.11.0
Compare Source
Note that #1150 includes breaking interface changes which may require updates to third party plugins.
v1.10.4
Compare Source
excludedRunners
parameter to command line interface and Antv1.10.3
Compare Source
v1.10.2
Compare Source
v1.10.1
Compare Source
v1.10.0
Compare Source
As a result of #1067 it is important that mutations are only created for a single class for each JVM. The MutationGrouper extension point has therefore been removed as this allowed this constraint to be violated. Any third party plugins using this extension are no longer supported.
Releases also includes multiple changes to internal data structures. Any third party plugins relying on these structures may need to be updated.
1116 provides a coarse way to exclude auto-generated code not picked up by pitest's other filters. It is disabled by default as it may exclude code that is valid for mutation in some situations, but can be enabled by adding the feature string +nofirstline.
v1.9.11
Compare Source
v1.9.10
Compare Source
v1.9.9
Compare Source
#1098 Include case values in switch mutation descriptions
v1.9.8
Compare Source
#1094 Search for source files outside of package dirs
Adds support for languages such as Kotlin where source files may not be within a directory structure which matches their package. Note that if the same filename occurs in more than one location, pitest cannot guarantee to resolve the correct file.
v1.9.7
Compare Source
v1.9.6
Compare Source
Note that 1085 changes the default behaviour so reports are no longer written to timestamped directories by default. If you require this behaviour you will need to explicitly enable it.
v1.9.5
Compare Source
1078 is a breaking interface change, but is included in a point release as it is believed there are currently no external clients.
v1.9.4
Compare Source
v1.9.3
Compare Source
1054 Moves support of auto adding headless=true (to prevent keyboard focus being stolen on Macs) into a feature.
It is enabled by default, but can be disabled by adding
-MACOS_FOCUS
to the features string.1055 adds the option to guess the appropriate number of threads for the current machine by adding
+auto_threads
the features string. This option is disabled by default and designed for local use. It is not recommended
for use on a CI server.
v1.9.2
Compare Source
v1.9.1
Compare Source
#1047 Mitigation for intemittent process hangs
v1.9.0
Compare Source
dependencyDistance
parameterThis release greatly improves the speed and efficiency of the coverage analysis performed before mutation analysis begins (particularly if you are using JUnit 5).
As a result of #1040 any external pitest test plugins (eg JUnit 5, TestNG, arcmutate accelerator) must be updated to a compatible version (1.0.0) when upgrading.
The
dependencyDistance
parameter is no longer supported.History files from earlier releases are incompatible and should be deleted when upgrading.
v1.8.1
Compare Source
v1.8.0
Compare Source