Keep em' coming
Although that said, this one is going to take a little longer to find a fix for than the last one.
It varies from bug to bug if we write the tests before or after. In the bugs you've reported it was quicker to put the scripts into small tests and run them there than it was to start SSMS every time I made a change.
We have a large set of integration tests (~50,000) that run against test databases every time a build on our build server is completed and then another set of slow running ones overnight. I'm currently trying to move more of our tests into small, quick running unit tests that just mock a database where needed - these are really cool with NCrunch since they can be run every keypress making the feedback if a test fails/passes almost immediate.
It is really interesting to work on, especially as the parser needs to handle incomplete syntax and figure out all the things user might enter at each point (without being too slow!)