Tag Archives: Unit Testing
How to estimate effort for unit testing?
Is that a right question to ask at all during effort estimation stage? When taking workshop with software developers involved SCRUM methodology, I came across some of the following answers in relation with effort estimation vis-a-vis unit testing: No task was created for unit tests and hence, no effort was estimated. Thus, we didn’t write any unit tests. We had to deliver and we were running short of time; hence, we skipped unit testing? There are effort estimation done for functional tests by QA engineers; Then, why unit tests? Interestingly, some stakeholders on client end said about of software developers on offshore side not asking for tasks to be estimated …
Unit Tests & What do they say?
Ask software developers about what do they mean by unit testing, and if they believe in it? And, the answer you get are some of the following: Unit testing is about writing tests for each of the method of the class. It is written only when you get some extra time after the code completion? Unit testing is done only when we are asked by our customers. Unit testing takes additional time and hence, done only if time permits. Test-driven development… What is that? Not sure if there are any benefits by writing unit tests? Test coverage… What is that? Why do we write unit tests when we are software …
I found it very helpful. However the differences are not too understandable for me