Skip to content

Instantly share code, notes, and snippets.

@pawelsawicz
Last active June 12, 2016 21:38
Show Gist options
  • Save pawelsawicz/28f5c6d90bbc13245bf2025009d6be4f to your computer and use it in GitHub Desktop.
Save pawelsawicz/28f5c6d90bbc13245bf2025009d6be4f 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 test to guard your code, 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 do mistakes.
My presentation will give you an overview of a very important pattern which is mutation testing.
You will learn why you should use mutation testing, why you shouldn't trust your tests and your test coverage.
During presentation, we will try to redefine current test coverage definition to more meaningful description.
Mutation testing runners are very helpful tool with TDD, where you are exposed to a lot of wrong assumptions
and simple syntax errors that can propagate other errors.
You write your unit test to guard your code, who will guard your unit tests ?
We put a lot of trust into our unit tests. But should we really ?
My presentation will give you an overview of a very important pattern which is mutation testing.
You will learn why you should use mutation testing, why you shouldn't trust your tests and your test coverage.
During presentation, we will try to redefine current test coverage definition to more meaningful description.
Mutation testing runners are very helpful tool with TDD, where you are exposed to a lot of wrong assumptions
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment