Timeline for Unit Testing Module-Internal Functions
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 4, 2020 at 22:14 | vote | accept | Woodrow Barlow | ||
| Feb 7, 2016 at 9:22 | history | tweeted | twitter.com/StackProgrammer/status/696262825786875904 | ||
| Feb 4, 2016 at 17:07 | vote | accept | Woodrow Barlow | ||
| Oct 4, 2020 at 22:14 | |||||
| Feb 4, 2016 at 12:54 | answer | added | soru | timeline score: 0 | |
| Feb 3, 2016 at 20:19 | comment | added | TMN | If you're testing all your external functions, doesn't that imply that they're calling all your internal functions? If not, why are those functions there? | |
| Feb 3, 2016 at 18:42 | answer | added | Tom Penny | timeline score: 2 | |
| Feb 3, 2016 at 9:07 | answer | added | cauchi | timeline score: 6 | |
| Feb 2, 2016 at 21:58 | history | edited | Woodrow Barlow | CC BY-SA 3.0 | deleted 2 characters in body |
| Feb 2, 2016 at 17:05 | comment | added | Woodrow Barlow | @DanPichelman personally, i do agree with you. my team does not. they've mandated a static code coverage target. | |
| Feb 2, 2016 at 17:04 | comment | added | Dan Pichelman | I would argue that you shouldn't unit test internal functions - see also Unit testing internal components. In theory, internal functions can be added, removed, or rewritten at will without out harming anything, provided the external functions continue to pass their unit tests. | |
| Feb 2, 2016 at 16:59 | history | asked | Woodrow Barlow | CC BY-SA 3.0 |