Timeline for How to convince team members of the existence of a "mandelbug"
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 30, 2013 at 21:32 | comment | added | gnat | I see, thanks. Sounds interesting, I need to give it some thought... | |
| May 30, 2013 at 21:28 | comment | added | Karl Bielefeldt | That might fall into my code inspection exception, but you can also trigger race conditions by introducing a delay in one of the threads. Often you can accomplish this by delaying an external stimulus, or less ideally, you can put the delay directly into the code during testing. | |
| May 30, 2013 at 21:20 | comment | added | gnat | how do you do an automated test for stuff like that? (to avoid misunderstanding, everything else you wrote matches my own experience and beliefs) My most recent bug like that was data race for unsync'd concurrent access, both the bug and fix were very easy to prove by code inspection but I can't imagine how to reliably auto-test that. (I mostly have little problems designing tests for concurrent stuff but can't figure test code to prove absence of data race) | |
| May 30, 2013 at 21:09 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |