Timeline for Are (database) integration tests bad?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 11:33 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Mar 11, 2017 at 15:50 | history | edited | user3198764 | CC BY-SA 3.0 |
added 2 characters in body
|
| Mar 11, 2017 at 15:43 | comment | added | user3198764 | I think it depends on the project. On smaller projects with fewer resources where a developer is more overall responsible for testing and regression testing because of a lack of testers and keeping documentation in synch with code, if I'm going to spend any time writing tests, it's going to be ones that gives me the most bang for my buck. I want to kill as many birds with one stone as possible. If most of my logic and bugs come from database stored procedures which are generating reports, or from the front end JavaScript, having full unit test coverage in the middle tier doesn't help much. | |
| Mar 10, 2017 at 10:55 | comment | added | BЈовић | it is so obvious that you do not understand the difference between unit and integration tests | |
| Mar 9, 2017 at 18:48 | review | Late answers | |||
| Mar 10, 2017 at 10:55 | |||||
| Mar 9, 2017 at 18:33 | review | First posts | |||
| Mar 21, 2017 at 11:57 | |||||
| Mar 9, 2017 at 18:29 | history | answered | user3198764 | CC BY-SA 3.0 |