Timeline for Is it bad practice to repeat logic being tested in unit tests?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 11, 2019 at 8:28 | answer | added | Joop Eggen | timeline score: 0 | |
| Jun 10, 2019 at 21:17 | answer | added | Berin Loritsch | timeline score: 1 | |
| Jun 9, 2019 at 1:50 | answer | added | VoiceOfUnreason | timeline score: 3 | |
| Jun 8, 2019 at 16:55 | answer | added | Robert Harvey | timeline score: 6 | |
| Jun 8, 2019 at 16:48 | comment | added | Adam Thompson | @RobertHarvey the example is completely contrived. | |
| Jun 8, 2019 at 16:34 | comment | added | Robert Harvey | What does conditionOne and conditionTwo actually accomplish? What is the real-world concept that is being captured? | |
| Jun 8, 2019 at 16:24 | comment | added | Adam Thompson | @jonrsharpe so much less maintainable and takes so fewer lines of code to write though.. but I see where you are coming from. I'm torn. | |
| Jun 8, 2019 at 16:03 | comment | added | jonrsharpe | Rule of thumb: if you have the same logic in the test as you do in the code it's testing, it's not a good test. The table test is the best balance of dumb and DRY there, I think. | |
| Jun 8, 2019 at 15:50 | history | asked | Adam Thompson | CC BY-SA 4.0 |