自定义博客皮肤VIP专享

*博客头图:

格式为PNG、JPG,宽度*高度大于1920*100像素,不超过2MB,主视觉建议放在右侧,请参照线上博客头图

请上传大于1920*100像素的图片!

博客底图:

图片格式为PNG、JPG,不超过1MB,可上下左右平铺至整个背景

栏目图:

图片格式为PNG、JPG,图片宽度*高度为300*38像素,不超过0.5MB

主标题颜色:

RGB颜色,例如:#AFAFAF

Hover:

RGB颜色,例如:#AFAFAF

副标题颜色:

RGB颜色,例如:#AFAFAF

自定义博客皮肤

-+
  • 博客(1)
  • 资源 (2)
  • 收藏
  • 关注

原创 junit和testng对BeforeClass和AfterClass注解的不同要求

如果某一个方法在单元测试中被beforeclass和afterclass标注,那么,如果该单元测试是给予junit框架的,那么两个方法必须声明为静态的方法,否则编译失败。但是如果是给予testng单元测试框架时,没有该限制。具体的实验可以参考下面的代码。单例模式的实现类package pattern.design;public class Singleton {

2015-09-24 22:35:33 1807 1

Next Generation Java Testing TestNG

Doing the right thing is rarely easy. Most of us should probably eat better, exercise more, and spend more time with our families. But each day, when confronted with the choice of being good or doing the easy thing, we often choose the easy thing because, well, it’s easier. It is the same way with software testing. We all know that we should spend more effort on testing, that more testing will make our code more reliable and maintainable, that our users will thank us if we do, that it will help us better understand our own programs, but each day when we sit down to the computer and choose between writing more tests and writing more application code, it is very tempting to reach for the easy choice.

2015-10-08

OCA Java SE 7 Programmer I Certification Guide

OCA Java SE 7 Programmer I Certification Guide

2014-03-17

空空如也

TA创建的收藏夹 TA关注的收藏夹

TA关注的人

提示
确定要删除当前文章?
取消 删除