UI testing vs unit testing?

Unit testing aims to test small portions of your code (individual classes / methods) in isolation from the rest of the world.

Unit testing aims to test small portions of your code (individual classes / methods) in isolation from the rest of the world. UI testing may be a different name for system / functional / acceptance testing, where you test the whole system together to ensure it does what it is supposed to do under real life circumstances. (Unless by UI testing you mean usability / look & feel etc.Testing, which is typically constrained to details on the UI.

) You need both of these in most of projects, but at different times: unit testing during development (ideally from the very beginning, TDD style), and UI testing somewhat later, once you actually have some complete end-to-end functionality to test. If you already have the system running, but no tests, practically you have legacy code. Strive to get the best test coverage achievable with the least effort first, which means high level functional tests.

Adding unit tests is needed too, but it takes much more effort and starts to pay back later. Recommended reading: Working Effectively with Legacy Code.

And a fat +1 for referencing Working Effectively with Legacy Code. – Steven Mar 2 at 11:05.

Unit test should always be done. Unittests are there to provide proof that each UNIT (read: object) of your technical solution delivers the expected results. To put it very (maybe too) simple, user testing is there to verify that your system fulfills the needs and demands of the user.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.