Timeline for Why are my unit tests so expensive? [duplicate]
Current License: CC BY-SA 3.0
19 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 8, 2015 at 13:39 | history | closed |
gnat user53019 user22815 durron597 user40980 |
Duplicate of Are unit tests really that useful? [closed] | |
| Apr 8, 2015 at 10:31 | answer | added | soru | timeline score: 1 | |
| Apr 8, 2015 at 7:49 | answer | added | Julia Hayward | timeline score: 1 | |
| Apr 7, 2015 at 21:29 | review | Close votes | |||
| Apr 8, 2015 at 13:39 | |||||
| Apr 7, 2015 at 21:29 | answer | added | leo | timeline score: 11 | |
| Apr 7, 2015 at 21:14 | comment | added | gnat | see also: How to explain the value of unit testing. "...Add a couple of them whenever I change code, without trying to thoroughly cover all the code (which would take an inordinate amount of time)" | |
| Apr 7, 2015 at 21:04 | answer | added | Doc Brown | timeline score: 13 | |
| Apr 7, 2015 at 21:02 | comment | added | user40980 | Some examples on C2 had the ratio of code to unit test and the reciprocal unit test to code... along with a bit of discussion about it. Realize that you can write a fair bit code in tests themselves. | |
| Apr 7, 2015 at 20:41 | comment | added | Dunk | @Michal - By any chance do you develop your code in the context of a working application? That's how I typically develop. Thus, unit tests (at the class level) don't typically reveal many bugs for me either. That's why I write subsystem level tests instead and only test individual classes when they have non-trivial processing going on. If you design your subsystem interface well then most internal redesigns tend not to affect the interface and don't invalidate the test cases. | |
| Apr 7, 2015 at 20:37 | comment | added | Michal Krasny | scriptin: 4 classes, 16 methods totally (taken from GIT). The preparation of the tested objects and assertions are rather complex, I'm testing work with domain objects, that have approximately 15 members each, some of them are structured objects. | |
| Apr 7, 2015 at 20:36 | answer | added | Telastyn | timeline score: 7 | |
| Apr 7, 2015 at 20:26 | history | edited | Michal Krasny | CC BY-SA 3.0 |
added 291 characters in body
|
| Apr 7, 2015 at 20:26 | comment | added | scriptin | How many tests have you written in those two days and how trivial/complex are they? How much code (approximately) was tested (# of classes, methods)? | |
| Apr 7, 2015 at 20:22 | comment | added | Michal Krasny | I did not express myself well. I'm doing unit tests after I finish some functionality. I'm coding on the project for about 1,5 months at the moment, but the time I spend unit testing is approximately 20% of my productive time. That means I test quite small amount of my code. | |
| Apr 7, 2015 at 20:14 | answer | added | SurrealSyntax | timeline score: 2 | |
| Apr 7, 2015 at 20:13 | comment | added | Doc Brown | So you were doing "two days of just unit testing"? And since you work upfront and spend the same time for coding as for writing tests, does that mean you did two days of coding without any testing, and could not find more than a minor bug? Sounds strange. | |
| Apr 7, 2015 at 20:06 | comment | added | Telastyn | It sounds as though you're doing it right, albeit a little slowly - probably because you're new to it. Though I'd like to point out that it's very uncommon for everyone on your team to write clean code, short methods, with SRP, etc. | |
| Apr 7, 2015 at 20:04 | review | First posts | |||
| Apr 7, 2015 at 21:09 | |||||
| Apr 7, 2015 at 20:03 | history | asked | Michal Krasny | CC BY-SA 3.0 |