Timeline for Automated test for code that takes a bunch of input data and outputs a bunch of data - should it be split up?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 23, 2016 at 11:42 | comment | added | RubberDuck | No time for a proper answer, but I think you're on the right track. Only, I would make sure to have at least several of these top level tests. At least one happy path with valid input, and several failing cases with invalid input to make sure you know when you're really done. | |
| Feb 23, 2016 at 11:38 | answer | added | gbjbaanb | timeline score: 1 | |
| Feb 23, 2016 at 10:56 | history | edited | Jayy | CC BY-SA 3.0 | edited title |
| Feb 22, 2016 at 19:05 | history | asked | Jayy | CC BY-SA 3.0 |