The recently added test framework has a tool called the ProfileParser which started as a tool for analyzing run times of single-fragment queries. Over time, it evolved to compare planned and actual cost for multi-fragment queries.
This ticket requests that multi-fagment support be added to the printing of run times.
If a query is single-thread, print the query as in the prior version:
If the query is multi-fragment and forms a tree, use the format used to display planning vs. actual info: