Communication is everything, and the field of software testing is no exception there. What benefit do well-executed tests deliver when the results are not properly communicated between testers, project managers, developers and users?
A simple tool to support the communication is a testing blog. This is not a blog about testing, but a blog in which the continuous test results such as test protocols and other test-related content such as the testing strategy is published.
On such a blog, you will get a very quick overview of test activities and tracked inadequacies. The blog format is perfect for reading the test protocol and more appropriate than, for example a PDF, because no page breaks will disrupt.
The blog is not for representing any bug fixing workflow, but is merely designed for reading. A blog is not a special testing tool, so various stakeholders also may have a look at it, without having any prior knowledge in special tools.
I have not used the testing blogs so far in any "industrial project", but I think that such a testing blog can be quite useful for the end user.
It provides the information to the users which otherwise one would not have been shared. Ultimately it's a question of where the Line of Visibility of its service would be drawn.
Maybe one confuses the customer, because he suddenly sees how many errors are there at an early stage. Perhaps he especially gains trust because he gains insight into the testing process. Probably he even adds beneficial comments to test runs, regarding features that are good or bad.
A few months ago I had this idea for the first time. The manual creation of test protocols in a blog was completely impractical, for example, each screenshot must be saved on your desktop, then uploaded and linked to the blog.
Therefore, I have developed a plug-in for Quality Spy, which allows to publish Quality Spy projects and test runs on WordPress.com. Self-hosted blogs initially have to install the JetPack plugin, which provides the wp.com JSON API. A detailed description of the plugin can be found under qualityspy.wordpress.com/2013/12/02/blogging-your-test-project.
For me, testing blogs are the icing on the cake, the best thing you can make from test protocols, if you want to promote a communications-intensive test.