Timeline for Change-detector tests considered harmful
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 10, 2019 at 10:43 | history | edited | Martin Spamer | CC BY-SA 4.0 | added 4 characters in body |
| Sep 13, 2017 at 8:21 | history | edited | Martin Spamer | CC BY-SA 3.0 | added 37 characters in body |
| Mar 21, 2017 at 0:24 | comment | added | Maybe_Factor | But the real purpose of the code under test is to delegate to other units to get the desired behaviour. The contract for firstPart.process and secondPart.process specify the behaviour that each of them must implement, so those behaviours should be tested as part of the implementation of those objects. Don't forget we should also have integration/functional tests to test that the units all behave nicely together to achieve the expected result... unit testing should test what a single unit does and only what that unit does. | |
| Mar 20, 2017 at 21:59 | history | edited | Martin Spamer | CC BY-SA 3.0 | added 48 characters in body |
| Mar 20, 2017 at 21:15 | history | answered | Martin Spamer | CC BY-SA 3.0 |