Interview Question

[Matt L]

That's not a unit test, that's an integration text. My previous job implemented a 80% code coverage rule on a system that had no unit test (or test friendly code) on there. So even if you changes a single character in a method, you needed at least %80 code coverage. Very mixed opionions on the usefulness but after a number of years and after we tied the tests into TFS's nightly builds, it really started to pay dividends. It's a real tough start but I'm all for it. I remember someone wrote a unit integration test that only worked the 4th time is was run because it needed the other tests to populate the DB with enough test accounts for it to work :wtf: