I've noticed recently that a bunch of bugs fixes are going in without regression tests. We must not do that. We need these regression tests so that WebKit keeps getting better instead of playing "Whac-a-Mole" <http://en.wikipedia.org/wiki/Whac-a-Mole#Colloquial_usage>.

    - Please make a reduced test case into a standalone test. This can help us figure out what the bug is, and saves the person fixing the bug precious time.

    - Please write a test. Anders even suggests writing the test before fixing the bug, which I think is a great idea. And if you can't write a test, please make a note in the change log explaining why.

    - Please do review-minus if there's no test, even if the fix is otherwise correct.

    - If the reviewer forgot to ask for a test, mark the bug review-minus.

I am one of the recent offenders here! At the end of the message I list eleven recent check-ins that:

    1) look to me like bug fixes

    2) don't mention any new tests that were added (either manual tests or tests in LayoutTests)

    3) don't give any excuse for the lack of tests

For these we should write some tests now, or update the change log to show the tests we did land and forgot to mention or to give excuses.

    -- Darin