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

Ignore halts #93

Open
PalumboN opened this issue Feb 27, 2024 · 2 comments
Open

Ignore halts #93

PalumboN opened this issue Feb 27, 2024 · 2 comments

Comments

@PalumboN
Copy link

If any test arrives at a halt during the mutation, then the debugger is open (and stops the analysis until proceed).

I would like to interpret this as a fail (broken the test), so the mutator should be killed automatically.

@PalumboN
Copy link
Author

PalumboN commented Feb 27, 2024

I think that I could manage it by changing this line to this extension method:

"*MuTalk-Model"
TestSuite >> runStoppingOnFirstFailOrError: aResult
    self tests do: [:each |
        self changed: each.
        [ each run: aResult ] on: Halt do: [ :ex | ^ ex sunitAnnounce: each toResult: aResult ]. "<<------"
        (aResult failuresSize > 0 or: [ aResult errorsSize > 0]) ifTrue: [ ^ self ]]

But the behavior is not the expected, I'm getting them as Terminated Mutants instead of Killed
image

@PalumboN
Copy link
Author

I also have mutants like this:

image

There are tests that probably arrived to one exception (MNU, OutOfBounds, etc.) and the mutant could change the code, so probably it's related.

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

No branches or pull requests

1 participant