Hi
Why don't we start writing unit tests for MySQL code?
I have been experimenting with the google unit testing framework lately.
I started out with something simple, some of the list classes.
Then I went on to write tests for the 'metadata locking' classes.
This was all presented at the runtime team meeting a couple of weeks ago.
My results have been pushed to
bzr+ssh://bk-internal.mysql.com/bzrroot/server/mysql-6.0-codebase-bugfixing-gtest/
For information about googletest, see here:
http://code.google.com/p/googletest/
-- didrik
PS: here's a snippet from the high-level description of worklog 5077:
>> MySQL has a fairly extensive set of system tests, for testing
>> features, functionality, failure handling etc. of the overall
>> system. There are however very few unit tests, and the ones we *do*
>> have are not executed as part of pushbuild. The goal of this worklog
>> is to illustrate that given the right tools, it is easy to write unit
>> tests for parts of the MySQL codebase.
>>There are several benefits of unit testing which are not covered by
>> system/integration testing:
>>- earlier testing: new code/classes/features can be tested *during
>> development* rather after integration
>>- it simplifies integration with the rest of the system, since
>> designing code for testing tends to lead to cleaner interfaces.
>>- certain features, e.g. failure handling, are much easier to
>> verify in a unit test, than in a system test.
>>Note that we do *not* want to replace the existing system test
>> framework.
