Also, it's sort of hard to separate "writing code" from "writing tests" at this point. It more or less becomes a big blur. Test writing leads to design decisions, design decisions lead to tests, etc.
On Tue, Nov 24, 2015 at 10:19 AM, Stewart Mckinney <[email protected]> wrote: > "Normal" is hard to gauge. I would say I spend about a third to half my > time writing tests, but I'm not sure if my situation is "normal". > > > On Tue, Nov 24, 2015 at 10:07 AM, <[email protected]> wrote: > >> For a "normal" project, how much time would I have to calculate goes for >> writing tests vs writing the "real" code? >> >> Thanks for any thoughts! >> >> Eric >> >> -- >> You received this message because you are subscribed to the Google Groups >> "AngularJS" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/angular. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
