Search Results

I'm a big proponent of unit testing (I'd love to be involved in test driven development). … What have you done to help justify more unit testing investment, in terms of measured results or other data? Bug tracking results will help, but looking for additional ideas. …

However, with the advent of TDD and automated testing it is much more reasonable to rewrite and refactor code. Does anyone know if there is a TDD tool that can be used for porting old code? … The alternative would be to split step 1 into "Write up unit tests in language 1" and "Port unit tests to language 2", which significantly increases effort required and is difficult to justify if the old …

Sometimes they fail because the System Under Test has been changed because the requirement changed, but the unit test hasn't been changed. … Some errors might be caught a bit later as a result (during testing instead of before the pull request), but perhaps the cost saved in not writing unit tests could offest the delay in catching the bugs …

Now others say that this is more expensive that doing manual test. … So what I did was to replace developer manual testing with automated testing (unit and integration tests) and that's what management wants to revert. …

So the question is: What size of code base justifies writing unit tests? Is unit testing overkill for a project of this size? … Or do the reasons to write unit tests for larger projects apply here as well? Please note that I am aware of the great advantages of having unit test coverage of the code base. …

I typically write long unit test descriptions that link the test to a user story. … The test is as much about justifying why the code exists and how it fits into the larger system as it is about testing for correctness. …

It sounds like a good idea, but I honestly can never justify the extra work involved. I work hard to be forward-thinking in my design. … In my situation, would you still find a way to make unit testing a regular practice, or am I justified in avoiding that overhead? …

I have been researching TDD for quite a while now, and although it is easy to realize its benefits for larger applications, I am having a hard time trying to justify the time to begin using TDD on the … I understand its advantages in automating testing, improving maintainability, etc., but on our scale, writing even basic unit tests for all of our components could easily double development time. …

While all of those points seem to have some merits, I think they don't justify the massive increase in number of classes the defining interfaces preemptively entails. … Mocking classes without interfaces is easy with Mockito or other Unit Testing Frameworks. …

I've been writing a lot of unit tests lately and have become somewhat obsessed with code coverage. … However, I'm struggling justifying going for 100% code coverage, when so many tests would be a redundant, and really clutter up my unit tests. For example, imagine an customer endpoint of an API. …

What facts do you have that justify unit testing is worth the effort you put into it? … If your management team don't agree to investing what they see as an additional 150 hours on unit testing, perhaps you can convince them to invest in one small area of the product (or even agree to suck …

I would like to implement unit testing, change from a procedural to OO approach, automate testing, use a better logging system, fully validate all input, implement better error handling and many other … It is going to be hard to justify taking the time to refactor, especially if we can't bill the time to a client. …

First of all this should be tested by system/acceptance tests that cover what ever feature needs this class for unit tests I'd say the answer is mostly no, there is nothing useful to test here, the only … time I would unit test is if it was more effort to justify why I'm not testing this class than to test it (sometimes the case with safety related stuff) …

I'm a junior developer that is given the ability to help shape my team's processes if I can justify the change, and if it helps the team get work done. … a consolidated issue tracking process (we have a tool, the process is still being developed) a unit, system, regression, or manual testing suite or list documentation on business logic and processes a …

Unit testing is all about testing units of your code. It is up to you to define what a unit is. Your coworkers define units as API elements. … If some part of code has not been reached, give your coworkers three choices: define another test case for covering that part, analyze code for justifying why it cannot be covered in the context of unit …