-
Notifications
You must be signed in to change notification settings - Fork 31
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
docs(site): Add metaphor-free TL;DR to Introduction #608
Conversation
I had a lot of trouble understanding this page because it immediately forces me into a mental model of 'mutants' and 'mutations' that only serve to distract me from understanding the gist of mutation testing. Mutation itself is even confusing because it make me think of network calls that do data mutations. It also confuses me because it reminds me of mutable vs immutable approaches in code. This TL;DR summarises the page in a way that I believe would have made me got the concept right away.
✅ Deploy Preview for stryker-mutator ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
I think this simplifies things a bit too much. Mutations can and do occur outside of return statements. |
How about:
|
@nicojs I'm not sure what to think of this. Personally I think the text we have now is fine, however we have a clear user request for clearer language so.. It's probably bias and we should do something with this.
|
@rouke-broersma What you're citing there sounds perfect to me. That isn't yet on the site, is it? |
No it's my proposal. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your feedback. What do you think about my suggestion?
Co-authored-by: Nico Jansen <jansennico@gmail.com>
I had a lot of trouble understanding this page because it immediately forces me into a mental model of 'mutants' and 'mutations' that only serve to distract me from understanding the gist of mutation testing. Mutation itself is even confusing because it make me think of network calls that do data mutations. It also confuses me because it reminds me of mutable vs immutable approaches in code.
This TL;DR summarises the page in a neutral way, without references to metaphors, that I believe would have made me got the concept right away.