The Framework for Integrated Tests (Fit)
Every few years, someone in the tools and practices community has a great idea for improving the process of software development; one that is important enough for anyone with a role in software development to stop and take notice. Fit (Framework for Integrated Tests - http://fit.c2.com) is a tool for expressing application acceptance tests using tables, and one that solves a fundamental need in software development: capturing business rules in an easily accessible and executable form.
Get creative with Wicked Cool Java
Summary
Every now and then, a really interesting and helpful Java book appears: Wicked Cool Java is one example. In this article, Jeff Friesen reviews this book chapter by chapter and concludes with a brief interview with its author, Brian D. Eubanks. (2,000 words; March 20, 2006)
In pursuit of code quality: Resolve to get FIT
Try FIT and JUnit for a requirements testing workout!
Build your own profiling tool
Create an ideal profiler using the Java 5 agent interface and AOP
Profiling is a technique for measuring where software programs consume resources, including CPU time and memory. In this article, software architect Andrew Wilcox explains the benefits of profiling and some current profiling options and their shortcomings. He then shows you how to use the new Java™ 5 agent interface and simple aspect-oriented programming techniques to build your own profiler.
Plug memory leaks in enterprise Java applications
Strategies for detecting and fixing enterprise memory leaks
Summary
Because Java uses automatic garbage collection, developers think Java programs are free from possible memory leaks. Although automatic garbage collection solves the main cause of memory leaks, they can remain in a Java program. Specifically, such memory leaks in complex multitiered applications can be extremely daunting to detect and plug. This article analyzes the main causes of memory leaks in Java Enterprise Edition (Java EE) applications, and suggests strategies for detecting them. (3,200 words; March 13, 2006)
WebApp Monitoring made easy : J2SE 5.0 and then Mustang
WebApp Monitoring made easy : J2SE 5.0 and then Mustang
If you haven't tried this... feel free to try this out... using jdk1.5 and java options set JAVA_OPTS=-Dcom.sun.management.jmxremote and start the tomcat or any other appserver... then launch JDK_HOME\bin\jconsole.exe and when asked for attaching pick the tomcat process to attach. Mustang is more matured than tiger... planning to check that out soon...
If you haven't tried this... feel free to try this out... using jdk1.5 and java options set JAVA_OPTS=-Dcom.sun.management.jmxremote and start the tomcat or any other appserver... then launch JDK_HOME\bin\jconsole.exe and when asked for attaching pick the tomcat process to attach. Mustang is more matured than tiger... planning to check that out soon...
用 Cobertura 测量测试覆盖率
Cobertura 是一种开源工具,它通过检测基本的代码,并观察在测试包运行时执行了哪些代码和没有执行哪些代码,来测量测试覆盖率。除了找出未测试到的代码并发现 bug 外,Cobertura 还可以通过标记无用的、执行不到的代码来优化代码,还可以提供 API 实际操作的内部信息。Elliotte Rusty Harold 将与您分享如何利用代码覆盖率的最佳实践来使用 Cobertura。
