Timeline for How do you write tests for code that depends on concrete external implementations that can't be mocked?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 24, 2011 at 10:50 | vote | accept | Wayne Molina | ||
| May 20, 2011 at 20:39 | comment | added | Péter Török | +1 for good advice, this is what we do in our current project. We built a custom toolset for doing the PDF comparison, which allows us to omit changing parts in the documents such as timestamps. Caveat: switching to a different (version of the) PDF renderer may cause subtle changes in the layout, causing direct binary comparison to signal heaps of false positives. | |
| May 20, 2011 at 19:01 | comment | added | Gary | +1 because you're only interested in the final result at this level. If you change the implementation of how you arrive at getting the PDF you shouldn't have to change your functional test. | |
| May 20, 2011 at 17:46 | history | edited | Michael K | CC BY-SA 3.0 | added 3 characters in body |
| May 20, 2011 at 17:42 | history | answered | Steven A. Lowe | CC BY-SA 3.0 |