The submitted headline makes bold claims not actually contained in the article. I would recommend using the original title instead: "Hunt The Bugs With Mutation Testing."
The guidelines ask to use the original title https://news.ycombinator.com/newsguidelines.html There are some exceptions, when the title is a linkbait or not descriptive. Anyway, in general the dry titles are preferred here, people will complain otherwise.
You can edit the title of the post for a time after it was submitted. Probably 2 hours, but I'm not sure. The interval may change from time to time.
Another possibility is to write to the mods and ask them to change it, in case you made a horrible mistake. But this is not horrible.
Just remember to use the original title next time you post something.
(Note that if you are the author and use as the original title something like "Totally amazing program that will blow your mind!!!" and use the original title here, people <bold>will</bold> complain.)
It looks like you are the author of the blog post and/or the developer of the software. Next time add a small comment explaining that and offering to answer questions. It's not mandatory, but sometimes people is more friendly if the submitter is the author and replies the questions in the thread.
Mutation testing looks really fun until you use it. It has two problems, that false positives and false negatives abound, and that it doesn't scale well as code gets larger. Suppose you modify code, then how long does it take the mutation testing framework to retest the relevant code? On the other hand, mutations can do a good job of estimating test coverage. In particular, they can help to prioritize tests by finding tests that cover the most mutations.
"...understand why they are testing." That's interesting. There is an information-theoretic measure for test quality that asks how effective a test is by asking how closely it examines a test output. For instance, does it "smoke test" that the output isn't NULL, or does it look at a returned data structure and enforce invariants in detail. It's the flip-side of asking in how much detail a test exercises the code. Well, keep having fun. Testing is a great way to think about code.
Another suggestion: Don't repost too much. A few repost are ok, https://news.ycombinator.com/newsfaq.html , but you reposted the same article 7 times in 2 days. Users will get angry and flag your posts, and the mods will notice and may ban your site and your account.
The rules are not clear about how often you can repost, but in my opinion it's like a week, perhaps 2 or 3 days. At most 1 per day, but 1 per day is too much for my taste.
Also, reposting the same article more than 5-10 times will make people complain...
