{"id":690,"date":"2018-03-26T07:01:49","date_gmt":"2018-03-26T07:01:49","guid":{"rendered":"http:\/\/redmonk.com\/fryan\/?p=690"},"modified":"2018-03-26T17:25:29","modified_gmt":"2018-03-26T17:25:29","slug":"a-look-at-unit-testing-frameworks","status":"publish","type":"post","link":"https:\/\/redmonk.com\/fryan\/2018\/03\/26\/a-look-at-unit-testing-frameworks\/","title":{"rendered":"A Look at Unit Testing Frameworks"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Testing is perhaps the most frequently spoken about, but most often ignored aspect of software development. As we have noted before CI is the onramp to cloud native,<\/a> and to be successful with CI you need to continuously improve your testing.<\/p>\n

The most basic level of testing that you can put in place are unit tests. It is, however, amazing to us the amount of people we talk with that do not even have basic unit testing in place. Part of this is historic, part of this is technical debt and part of it is a fear of what may be uncovered if more rigorous testing is put in place.<\/p>\n

This last aspect, the fear of what may be uncovered, is perhaps the most insidious. It is also the easiest to address, just adding in a single test per developer per day on a project for existing functionality quickly adds up. Matt Curry<\/a> of Allstate had a lovely comment about this at SpringOne Platform<\/a> last year:<\/p>\n

\n

I think of my test suite like my bank account\u2026 I don\u2019t get to just park $1mn in one day, but if I put in $10 a day, with compounding interest, it adds up \/@mattjcurry<\/a> on test automation #SpringOne<\/a><\/p>\n

— DormAIn \ud83e\udddf\u200d\u2640\ufe0f (aka "part of the problem") (@DormainDrewitz) December 5, 2017<\/a><\/p><\/blockquote>\n