Timeline for JUnit Testing in Multithread Application
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 10, 2015 at 13:16 | history | tweeted | twitter.com/#!/StackProgrammer/status/597389812933464064 | ||
| May 9, 2015 at 4:29 | history | protected | gnat | ||
| Jun 4, 2013 at 10:58 | vote | accept | Sebastian van Wickern | ||
| Jun 4, 2013 at 10:58 | answer | added | Sebastian van Wickern | timeline score: 7 | |
| Feb 19, 2013 at 20:37 | audit | Suggested edits | |||
| Feb 21, 2013 at 10:56 | |||||
| Feb 5, 2013 at 17:10 | answer | added | Gary | timeline score: 5 | |
| Feb 5, 2013 at 14:15 | comment | added | Zachary K | Don't share mutable state | |
| Feb 5, 2013 at 11:02 | comment | added | Sebastian van Wickern | @ratchetfreak thank you for the mocking reference, that will help in testing, but it seems to be every other week that we encounter a new threading problem (we are in an alpha stage, soon to be beta), which is not very suprising in an applications which is highly optimized to run on an indefinit number of cores, but it's still annoying... | |
| Feb 5, 2013 at 10:54 | review | First posts | |||
| Feb 5, 2013 at 11:01 | |||||
| Feb 5, 2013 at 10:49 | comment | added | ratchet freak | keyword you are looking for is mocking, essentially you immitate the analysation part without doing the analysis, and test the analysers separately, but testing thread safety is a very hard problem in general and no prefab solutions are available | |
| Feb 5, 2013 at 10:38 | history | asked | Sebastian van Wickern | CC BY-SA 3.0 |