I believe that if they are going to add some value then they are worth adding/using. Most often I don't see the value in going back and retro fitting tests to existing code that 'doesn't get touched'.
For code that is actively build on its often good to have a strategy that touches on various areas of the SDLC lifecycle including unit, integration, functional and performance type tests to give you more breadth in what your testing might be able to expose.
As with everything this is context dependant, Ie : a highly critical application may need a lot more tests that a one page web app
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi,
I believe that if they are going to add some value then they are worth adding/using. Most often I don't see the value in going back and retro fitting tests to existing code that 'doesn't get touched'.
For code that is actively build on its often good to have a strategy that touches on various areas of the SDLC lifecycle including unit, integration, functional and performance type tests to give you more breadth in what your testing might be able to expose.
As with everything this is context dependant, Ie : a highly critical application may need a lot more tests that a one page web app