Message-ID: <1059691200.2761.1427609692719.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2760_1464088018.1427609692719" ------=_Part_2760_1464088018.1427609692719 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Unit tests are what keep your code on the straight and narrow pa= th. A Lack of Unit Tests is analogous to the moral Deadly Sin of sloth, whi= ch is sometimes called moral laziness, and sometimes defined as not doing t= he things you should do.
Unit tests help keep bugs and regressions from slipping into production = code. And when you make a change to existing code, they help you know that = you didn't break it. They are your backstop in refactoring, and give you co= nfidence, when you're eliminating duplications or reducing complexity, that= you haven't just thrown a monkey wrench into the works.
If you're dealing with legacy code that doesn't have unit tests, it like= ly wasn't written with unit tests in mind. In that case, don't be intimidat= ed by the volume of work you'll need to do to add tests. Instead, focus on = covering your new code, and add tests for existing code as you can.
Data on unit tests and code coverage can be displayed on a project dashb= oard by adding the SCM Activity plugin= a>, code coverage on new code (added or modified) is displayed.
For more details, see: