JMockit
Testing Newsletter - 2012/03
Submitted by Tomek Kaczanowski on Thu, 03/01/2012 - 13:17Summary on what happened in JVM (Java, Groovy, Scala) developers testing world in February 2012. Links to the most interesting articles and blog posts. News from JUnit, TestNG, Mockito, Selenium, Arquillian, mutation testing and many more. Enjoy!
Testing Newsletter - 2012/01
Submitted by Tomek Kaczanowski on Wed, 01/04/2012 - 13:52Summary on what happened in JVM (Java, Groovy, Scala) developers testing world in December 2011. News from JUnit, TestNG, Mockito, Selenium, Arquillian, mutation testing and many more. Also links to some good articles and blog posts. Enjoy!
Testing Newsletter - October 2011
Submitted by Tomek Kaczanowski on Tue, 11/01/2011 - 11:09Summary on what happened in JVM (Java, Groovy, Scala) developers testing world in October 2011. Byteman tutorial, Cargo 1.1.3, Selenium 2.9, links to the best articles and blog posts from the last month. Enjoy!
Testing Newsletter - September 2011
Submitted by Tomek Kaczanowski on Thu, 10/06/2011 - 11:06Summary on what happened in JVM (Java, Groovy, Scala) developers testing world in September 2011. News from JUnit, TestNG, Selenium, mocking frameworks, Arquillian and many more. Also links to some good articles and blog posts. Enjoy!
Developers' Testing Dilemma: Aim for Verification or Design?
Submitted by Tomek Kaczanowski on Sun, 12/05/2010 - 21:20Few notes on two approaches to testing. Some people seem to be more interested in verification, others aim for better design.
"Untestable" code - JMockit
Submitted by Tomek Kaczanowski on Sun, 04/20/2008 - 20:13This is a part of "Untestable code" series. See the introduction to know what is it all about (yes, you really should go there, do it).
The main idea of the series is to write unit-tests for a particularly nasty piece of code. In this part I will use JMockit library to write test cases.
Untestable Code - introduction
Submitted by Tomek Kaczanowski on Tue, 01/01/2008 - 18:34This is the first part of series of posts dedicated to the problems of unit-testing of some "untestable" code.
Sometimes, (more often than I'm ready to admit), I stumble over a piece of code which makes me doubt completely in my testing skills and sometimes even in unit testing in general. I've spend a lot of time trying to deal with such a "untestable" code. In this series of posts I'm gonna show you what I've learned.
This used to be my blog. I moved to http://tomek.kaczanowscy.pl long time ago.