Archives
Jailer 3.1.2 released
Submitted by Opensourcetesting.org - latest news on Tue, 14/07/2009 - 10:59.Jailer is a Database Subsetting Tool. It exports consistent, referentially intact row-sets from relational databases. It removes data w/o violating integrity, generates DbUnit datasets, hierarchically structured XML and topologically sorted SQL-DML.
The Plague of Amnesia
Submitted by noreply@blogger.com (James Whittaker) on Tue, 14/07/2009 - 16:24.By James A. Whittaker
Memory is supposed to be the first thing to go as one ages but in the grand scheme of engineering, software development can hardly be called elderly. Indeed, we’re downright young compared to civil, mechanical, electrical and other engineering disciplines. We cannot use age as an excuse for our amnesia.
Software Testing Categorization
Submitted by noreply@blogger.com (Misko) on Tue, 14/07/2009 - 20:53.by Miško Hevery
You hear people talking about small/medium/large/unit/integration/functional/scenario tests but do most of us really know what is meant by that? Here is how I think about tests.
Unit/Small
Lets start with unit test. The best definition I can find is that it is a test which runs super-fast (under 1 ms) and when it fails you don't need debugger to figure out what is wrong. Now this has some implications. Under 1 ms means that your test cannot do any I/O. The reason this is important is that you want to run ALL (thousands) of your unit-tests every time you modify anything, preferably on each save. My patience is two seconds max. In two seconds I want to make sure that all of my unit tests ran and nothing broke. This is a great world to be in, since if tests go red you just hit Ctrl-Z few times to undo what you have done and try again. The immediate feedback is addictive. Not needing a debugger implies that the test is localized (hence the word unit, as in single class).
You hear people talking about small/medium/large/unit/integration/functional/scenario tests but do most of us really know what is meant by that? Here is how I think about tests.
Unit/Small
Lets start with unit test. The best definition I can find is that it is a test which runs super-fast (under 1 ms) and when it fails you don't need debugger to figure out what is wrong. Now this has some implications. Under 1 ms means that your test cannot do any I/O. The reason this is important is that you want to run ALL (thousands) of your unit-tests every time you modify anything, preferably on each save. My patience is two seconds max. In two seconds I want to make sure that all of my unit tests ran and nothing broke. This is a great world to be in, since if tests go red you just hit Ctrl-Z few times to undo what you have done and try again. The immediate feedback is addictive. Not needing a debugger implies that the test is localized (hence the word unit, as in single class).
Changing Gears
Submitted by Danny Faught on Tue, 14/07/2009 - 22:08.There has been a big change at Tejas Software Consulting. I am now working full-time at New York Air Brake at their Train Dynamic Systems division in Fort Worth, Texas. It’s the first time I’ve worked close to home in Fort Worth. I’m working on train simulators that are used to train locomotive engineers. Another [...]