-
Notifications
You must be signed in to change notification settings - Fork 139
Save mutation stats for use with CI/CD pipeline #460
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
Open
mpownby
wants to merge
2
commits into
boxed:main
Choose a base branch
from
mpownby:main
base: main
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 hidden or 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
…nally take action on the results
Owner
|
I think it makes more sense if this is a separate command. There is already saved data, so such a command could read that and write this simplified json for your use case. |
Author
|
Are you referring to the mutmut-stats.json file? I could be wrong but it
appears that this file is generated before the tests start getting run with
mutations so it appears not to contain the data that I am looking for.
What would you envision the command to be called?
…On Wed, Jan 21, 2026 at 10:45 PM Anders Hovmöller ***@***.***> wrote:
*boxed* left a comment (boxed/mutmut#460)
<#460 (comment)>
I think it makes more sense if this is a separate command. There is
already saved data, so such a command could read that and write this
simplified json for your use case.
—
Reply to this email directly, view it on GitHub
<#460 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR4ABBU5OMIMPZSJBGRQGD4IBPZDAVCNFSM6AAAAACSOSKZU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBSGYYDENJTGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Owner
|
I don't remember the details but the mutmut TUI needs this data so it does exist on disk for sure. On 22 Jan 2026, at 19:08, mpownby ***@***.***> wrote:mpownby left a comment (boxed/mutmut#460)
Are you referring to the mutmut-stats.json file? I could be wrong but it
appears that this file is generated before the tests start getting run with
mutations so it appears not to contain the data that I am looking for.
On Wed, Jan 21, 2026 at 10:45 PM Anders Hovmöller ***@***.***> wrote:
*boxed* left a comment (boxed/mutmut#460)
<#460 (comment)>
I think it makes more sense if this is a separate command. There is
already saved data, so such a command could read that and write this
simplified json for your use case.
—
Reply to this email directly, view it on GitHub
<#460 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR4ABBU5OMIMPZSJBGRQGD4IBPZDAVCNFSM6AAAAACSOSKZU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBSGYYDENJTGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: ***@***.***>
|
…cation of 'mutmut run'
Author
|
ok I pushed a new change that hopefully is more in line with your vision.
thanks!
On Thu, Jan 22, 2026 at 12:13 PM Anders Hovmöller ***@***.***>
wrote:
… *boxed* left a comment (boxed/mutmut#460)
<#460 (comment)>
I don't remember the details but the mutmut TUI needs this data so it does
exist on disk for sure. On 22 Jan 2026, at 19:08, mpownby ***@***.***>
wrote:mpownby left a comment (boxed/mutmut#460)
Are you referring to the mutmut-stats.json file? I could be wrong but it
appears that this file is generated before the tests start getting run
with
mutations so it appears not to contain the data that I am looking for.
On Wed, Jan 21, 2026 at 10:45 PM Anders Hovmöller ***@***.***>
wrote:
> *boxed* left a comment (boxed/mutmut#460)
> <#460 (comment)>
>
> I think it makes more sense if this is a separate command. There is
> already saved data, so such a command could read that and write this
> simplified json for your use case.
>
> —
> Reply to this email directly, view it on GitHub
> <#460 (comment)>, or
> unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/ABR4ABBU5OMIMPZSJBGRQGD4IBPZDAVCNFSM6AAAAACSOSKZU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBSGYYDENJTGQ>
> .
> You are receiving this because you authored the thread.Message ID:
> ***@***.***>
>
—Reply to this email directly, view it on GitHub, or unsubscribe.You are
receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#460 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABR4ABFIOSCWIDAIN74QRKL4IEONFAVCNFSM6AAAAACSOSKZU6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOOBWGIZDEMBXGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
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 is a simple to change to save mutation stats after printing them so a CI/CD pipeline can optionally take action on the results.
Use case:
If mutation score is below a threshold, I want to block PR's from being merged and/or blocked a pipeline from advancing to the next stage.
Just testing the waters to see if you would be open to this change. I read your contribution guidelines and didn't see anything that would make this an auto rejection.