Do you test your code? What about your tests? Your tests are code, you need to write, refactor and maintain them. This is not cheap so how do you make sure you are testing enough but not too much? Discover Mutation Testing, a fun tool to make your code better by introducing bugs. -- The first part of the talk is about the costs of the tests to introduce what problem mutation testing is solving. The tests themselves are code, requires to be written and maintain and as such are far from being free. Depending of the maturity level of your application and your deadlines, you need to adjust the level of testing. Mutation testing is a technique that can provide a reliable metric to know how much of your code is actually tested (as opposed to unit test coverage which shows what code has *not* been tested) and as such provides a tool for both the team to control their level of tests and the business to have a trustworthy metric. The second part is about mutation testing itself: the theory, a demo of the PHP library Infection, pros/cons of that solution and the further development planned for this tool


Comments are closed.

Interesting approach, it seems somehow out of reach, though, maybe for the youth of the technology

Alessandro Lai at 15:32 on 11 May 2018

Talk was about nice and strong concepts; I would work a bit on English pronunciation and on the theoretical part of the talk, which was a bit long, even if interesting.

Tomasz Durka at 15:57 on 11 May 2018

Great talk with some fresh (in fact old) topic. Definitely will try it out. Great presentation with academical, in-depth approach. I hope the slides will be available online soon :)

Samuele Lilli at 19:38 on 11 May 2018

Interesting subject.
Maybe if the tools were around for more time other suggestion could be given but actually the concepts behind the topic were interesting and well explained.

Nice talk! Thanks for the part with tactics to speed things up.

Ani Sinanaj at 22:04 on 12 May 2018

This is one thing I knew nothing about and now I'm going to try to include it in as many projects as I can

Interesting even for those who do not use (yet :-o ) tests