Timeline for Unit-Testing functions which have parameters of classes where source code is not accessible
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Jun 26, 2013 at 8:34 | vote | accept | McMannus | ||
| Jun 25, 2013 at 7:26 | answer | added | Frederik P. | timeline score: 5 | |
| Jun 19, 2013 at 0:10 | answer | added | Joppe | timeline score: -1 | |
| Jun 19, 2013 at 0:00 | comment | added | Joppe | I think James means Moles, not Pex (pex is more of a test generator). Often used together. | |
| Jun 18, 2013 at 12:19 | answer | added | jk. | timeline score: 5 | |
| Jun 18, 2013 at 10:39 | comment | added | Doc Brown | @JamesSnell: I tried PEX some months ago and found it very disillusioning. It's a nice research project, but I don't think it really helps to to test the important things. And it does not solve the OP's problem. | |
| Jun 18, 2013 at 10:32 | answer | added | Doc Brown | timeline score: -1 | |
| Jun 18, 2013 at 10:29 | comment | added | Bart van Ingen Schenau | How about the obvious: in the preparation of your test, you create an InternalClass and InternalElement instance and manipulate those (through their interfaces) into the right state for your test. | |
| Jun 18, 2013 at 10:27 | comment | added | James Snell | Thinking out loud a bit here, but would this be a good use case for PEX? (research.microsoft.com/en-us/projects/pex) | |
| Jun 18, 2013 at 10:16 | history | asked | McMannus | CC BY-SA 3.0 |