转载：http://ericanderson.us/2008/05/08/using-eclemma-to-write-better-unit-tests/
创新互联网站建设公司提供网站设计和自适应建站服务。团队由有经验的网页设计师、程序员和市场专家组成，能够提供从
H5技术，网站制作，
广告投放平台，模板建站到
微信平台小程序开发等全方位服务。 以客户为中心，致力于为客户提供创新、高效的解决方案，帮助您打造成功的企业网站。
If you don’t already write unit tests you should be. (Hey, why aren’t you writing unit tests?) Unit testing has so many benefits and the upfront developer cost to write some unit tests can pay huge dividends later when you aren’t spending time debugging broken code nor attempting to save face due to clueless mistakes. You can also use them as a contract to the expectations of your implementations.
[@more@]
So, assuming you have some unit tests, how useful are they if they don’t test everything? At some level you will want to have a good idea that you’re testing everything. (NOTE: I mean everything really important. Writing perfect 100% coverage like this would likely be too expensive for the entire codebase.) This is where Emma comes in (and more importantly for us, EclEmma, an Eclipse plugin for Emma). Emma is a code coverage tool which lets you visual which parts of your code get executed during some execution (regular or JUnit).
Lets walk through using EclEmma to ensure that we have adequate testing being done. Lets test the following two classes.
GuessTheNumber.java:
view sourceprint?
分享文章：UsingEclEmmatoWriteBetterUnitTests-创新互联
本文网址：
http://cdkjz.cn/article/dgpggi.html
