Friday, May 03, 2013

New MySQL System QA blog


It has been a while since I last posted, but I wanted to post about my teams NEW blog page.

New System QA Blog

As always, we look for ways to improve QA and your feedback is always welcomed.
Best Wishes,


Laurynas said...

A great way to improve QA would be, for an open-source database, to have an open-source testsuite. The argument of "crashing testcases == exploits, thus must be withheld" does not fully apply, as Oracle seems to be withhelding much more than that. For example, non-exploitable testcases that use crash/fault injection, see bug A new 5.6 code adds extensive fault injection sites yet no (public) testcases for exercising them.

In this area the community is able to log (hopefully) useful bug reports even without testcases, see,, and I'm sure with the testcases the community QA would be even more helpful.

jbm said...

I appreciate the constructive feedback. I will forward it to my manger.

Mark Callaghan said...

Would be great if you eventually released all tests, especially for crashing bugs. It would not be great if I hit one of the bugs for which test cases are withheld while modifying MySQL. I have to modify MySQL to keep it happy in production. Alas, you don't have to share all of the tests with me.

Consider running linkbench for performance testing -

jbm said...

Hi, I know that linkbench is on the list of to do's.

As for the testcases, that is way above me.

I spend most of my time doing test automation and performance regression testing.

As promised, I forwarded the comment.

Thanks for the feedback.