The topic could be something like "Stabilize a server product in one week".
My idea is to provide straight-to-the-point methods to ensure the quality of an application server.
The article would try to answer the challenges in these scenarios:
a) Catastrophy. The server is to be launched very soon but there are no means for testing it.
b) Early bird. There is a very early build done and we would like to get some initial knowledge of it's reliability/performance. No commercial test tool available (yet). Also there are yet no stabilized test interfaces in the product.
In practice my intention is to present some very simple Perl tools for performance testing. In between the lines there could be a continuous very simplistic test strategy discussion based on common sense.
Could this be a useful article in a professional testing magazine? Or is it too much of a "tutorial" for newcomers? Other viewpoints/ideas?