Dashboard – how do we communicate what we know?

In the Coverage – did we test the right things well enough? section, we mentioned the low-tech testing dashboard. Earlier in this book, we mentioned that having access to the most important bugs can yield a quick summary of the software testing process. The low-tech testing dashboard we looked at previously talked about coverage. We also mentioned the idea that a census of risks can drive quality. Other common components of communicating test information include the build status, the automated pipeline, and the history of the automated pipeline (what features frequently fail). This yields a potential test dashboard that is a single web page that continually updates itself. Some components of a test dashboard might look something like this:

Figure 9.2 – Assembling the puzzle pieces to make a whole process dashboard. This image is only for layout representation purposes; text readability is...