Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Stryker doesn't ignore methods if they are not called on an object
See original GitHub issueDescribe the bug
Practically, that means that Dispose cannot be ignored, and this is how I discovered the problem.
But then I started to play around with this and it looks like whatever method a class has, it won’t be ignored if needed.
That is, in case I have DoSomething among ignored methods:
someObject.DoSomething() will be ignored
DoSomething() won’t be ignored
Expected behavior These methods are ignored, just like others are.
Desktop (please complete the following information):
- OS: Windows
- Stryker Version: beta 0.22.4
Additional context
This probably used to work as Dispose is mentioned in this issue which is resolved. Although it’s there among many other things, I don’t know if Dispose in particular was verified.
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@psfinaki The failing builds are due to our CI infra being flaky unfortunately. Nothing serious to worry about.
Not yet. When it’s released we will remove the fixed in master label.