Timeline for Managing code: Unit tests with source or separate?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2021 at 21:31 | answer | added | Archimedes Trajano | timeline score: 0 | |
| Mar 9, 2018 at 16:21 | answer | added | Adam B | timeline score: 6 | |
| Mar 9, 2018 at 13:56 | answer | added | Arcones | timeline score: 4 | |
| Oct 8, 2016 at 6:29 | history | tweeted | twitter.com/StackProgrammer/status/784641972367724544 | ||
| Jul 24, 2015 at 14:13 | comment | added | BobDalgleish | One purpose to keeping the tests in a separate set of folders is to make packaging the deployed product more straightforward. Java builders that I'm familiar with (Ant, Maven) will package up entire folders. In your method, you will have to explicitly enumerate all and only the objects you want to be finally deployed | |
| Jul 24, 2015 at 14:07 | history | edited | Kilian Foth | CC BY-SA 3.0 | fix spelling |
| Jul 24, 2015 at 14:03 | history | asked | drekka | CC BY-SA 3.0 |