Skip to content

Instantly share code, notes, and snippets.

@dylanbeattie
Forked from pawelsawicz/opis.txt
Last active June 12, 2016 21:13
Show Gist options
  • Save dylanbeattie/2028bf3ce37aca936ccf983a0ea6e2da to your computer and use it in GitHub Desktop.
Save dylanbeattie/2028bf3ce37aca936ccf983a0ea6e2da to your computer and use it in GitHub Desktop.
Old :
Session is about mutation testing, why and when you should mutate your code.
What benefits comes by mutating your code. Simply test your own tests.
It's very helpful tool with TDD where you are exposed to a lot of wrong
assumptions and simple syntactic errors that can propagate other errors.
New :
You write your unit tests to guard your code, but who will guard your unit tests ?
We put a lot of trust into our unit tests, but should we really ? We are humans, and we make mistakes.
This presentation will provide an overview of a very important practice - mutation testing.
You will learn why you should use mutation testing, and why you shouldn't trust your tests and your test coverage, and we will try to come up with a more meaningful definition of 'test coverage'.
Mutation testing is a very powerful pattern when used with TDD, where you are exposed to a lot of wrong assumptions
and simple syntax errors that can propagate other errors.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment