Comments for Schauderhaft

Comment on Properties of a Good Unit Tests by Pedro Newsletter 19.07.2010 « Pragmatic Programmer Issues – pietrowski.info

Mon, 19 Jul 2010 21:20:16 +0000

[...] Properties of good unit tests – check how many properties your test have. [...]

Comment on Properties of a Good Unit Tests by Nirav Assar

Nirav Assar — Mon, 19 Jul 2010 14:19:54 +0000

Couple additions:

- test code should be “clean” and treated just like production code. The understandability of test code is just as important as production code as it must be maintained and is vital to integrity of the product

- test should cover boundary cases and attempt to gain optimal code coverage. It should cover all (most) paths

- Practicing TDD (test first) should produce tests that are less brittle and focus on testing the behavior of the code and not be dependent on the structure. However, unit tests, due to mocks will be dependent on implementation up to a point certainly.

Comment on Properties of a Good Unit Tests by Lars Girndt

Lars Girndt — Sun, 18 Jul 2010 13:41:02 +0000

Hi,

Absolutely, but some additions:
Fast: one thousand tests should run in less than a minute. This allows an extensive test suite to run often during development. If your tests are slower, you might be doing integration tests.

I think this is even too long. In an IDE runner, a thousand tests should not take not longer than 5s. An efficient code-test-fix-cycle should be as fast as possible. waiting for a test suite to finish will drastically reduce the motivation to do TDD.

Reliable: For the same code base a test should produce the same result every time. A test that fails every 10th time will fail for a real bug and you won’t know it.

An even stronger requirement: A test has to be deterministic. This means no random, no new Date() or whatever.

And finally, what i think is most important: A test has to be maintainable. This means refactoring a system under test should yield in efficient and small changes in the test. This could be a realized by finding a proper abstraction level even within test classes. in additional this will also result in even more readable code.

Comment on New Feature of JUnit: Rules by Νέα χαρακτηριστικά στο JUnit 4 « Java Hellenic User Group

Νέα χαρακτηριστικά στο JUnit 4 « Java Hellenic User Group — Tue, 13 Jul 2010 14:14:36 +0000

[...] JUnit Rules [...]

Comment on Scrum is a Social Thing by jens

jens — Fri, 09 Jul 2010 07:23:17 +0000

@bob ama
regarding 1 day-2 weeks: Most of the time these differences are based on different assumptions, which then get clarified, resulting in a close match between estimates. But I guess it does happen. But if it happens, and the story actually takes 2 weeks, this will get obvious within 1 or 2 days, and then the team should go “F*** he said it all the time, we better listen to him next time”. If this doesn’t happen your team has room for improvement.

regarding changing requirements mid-scrum: Its the task of Scrum Master and Product Owner to prevent that. If it just isn’t possible you at least have one reason for failure visible to everybody. Actually this puts quite some social pressure even on high ranking managers.

Nobody said it is easy. (At least I didn’t)

Comment on Scrum is a Social Thing by bob ama

bob ama — Thu, 08 Jul 2010 20:58:34 +0000

“Everybody in the team makes an estimates, everybody commits to the sprint back log, so noone can go “I said all the time it doesn’t work”

So if everyone else says ‘1 day’, and you say ‘2 weeks’, I fail to see how you have a choice other than to accept the ‘intelligent’ majority.

Scrum = 1 stand up meeting per day
Burndown charts that look like ski-jumps
The business constantly changing what the hell they want mid-scrum.
It’s a nice idea though…

Comment on Why SQL Sucks by rolfen

rolfen — Sun, 04 Jul 2010 21:51:17 +0000

So, what’s the alternative?

Comment on How to Tune a SQL Statement by Dimityr

Dimityr — Wed, 30 Jun 2010 07:38:43 +0000

Nice milestones, but it will be better if examples were shown.

Comment on How to Tune a SQL Statement by ivan

ivan — Tue, 29 Jun 2010 08:34:58 +0000

what about query & query result caching ?

Comment on How to Tune a SQL Statement by stunaz

stunaz — Tue, 29 Jun 2010 03:16:06 +0000

Thank you for that,but its not helpful. What we need is examples, or how to really tune. i mean examples with cases
thanks