Timeline for Should I have unit tests for known defects?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2018 at 15:25 | comment | added | Captain Man | @RubberDuck There isn't really any ideal situation here (other than fixing the bug now haha). To me, at least seeing in the test results "10 passed, 0 failed, 1 skipped" is at least some indication something is fishy to people not familiar with it. I prefer the @Ignore approach. The reason using just a comment doesn't seem like a good idea to me is because I don't think people will often open unit tests to check them (unless they are failing, or (hopefully) when they wonder why something is being skipped). | |
| May 24, 2018 at 15:25 | comment | added | Captain Man | @RubberDuck There isn't really any ideal situation here (other than fixing the bug now haha). To me, at least seeing in the test results "10 passed, 0 failed, 1 skipped" is at least some indication something is fishy to people not familiar with it. I prefer the @Ignore approach. The reason using just a comment doesn't seem like a good idea to me is because I don't think people will often open unit tests to check them (unless they are failing, or (hopefully) when they wonder why something is being ignored). | |
| May 24, 2018 at 9:55 | comment | added | RubberDuck | This is nearly exactly what I do on the rare occasions I can’t fix the bug now for some reason. I’d love to hear how you handle the situation @CaptainMan | |
| May 23, 2018 at 14:23 | comment | added | Silviu Burcea | @CaptainMan I agree, I have updated my answer to provide a better way of the dev team being aware of a bug without failing the build. Your downvote was justified for the original answer I posted 3 years ago, I believe the current answer is more appropriate. Would you do it another way? | |
| May 23, 2018 at 14:21 | history | edited | Silviu Burcea | CC BY-SA 4.0 | added 947 characters in body |
| May 22, 2018 at 14:50 | comment | added | Captain Man | This is bad advice. No one will ever attempt to fix it. People are only going to open up old unit tests if there are compilation issues or test failures. | |
| Jan 31, 2014 at 12:50 | history | answered | Silviu Burcea | CC BY-SA 3.0 |