QOT

 With this post I want to start the practice of writing short weekly summaries of QOT activities.

This week I was able to work on some bug reports: #12 #13 #14 #15. Some trivial crashes, some of which were already fixed before. As I wrote in my previous post, I have changed the way I do the releases so if you want to have all the latest features and fixes be sure to use the latest Launchpad version of QOT.

Besides the bugs I started to rework my testing environment. Earlier I had a set of C++ - based unit-tests. I used while-box approach which was very convenient when the project had a smaller codebase and it was important to make core features work without having a defined user interface yet. But now it takes more and more time to write tests this way. That’s why I started to migrate to the MySQL Test Framework. It’s a very powerful tool based on very simple idea - you run the program, collect its output and compare to a pre-saved correct value. A test case there is a script consisting of SQL, shell and other commands. This way it becomes very easy for example to make QOT to generate an index and check if the index is really used by server. The work still in progress, but one interesting thing I noticed is that inside the tool I have lot more useful information than I show in output so now I’m also thinking about extending the QOT report format.

So far that’s it! See you next week