Tech Tips & Tricks: Test Run-to-Test Case Coverage

Welcome to another installment in our series of tips and tricks from the Polarion Software Technical Support team, in which we share solutions we provided to customers for real-world use cases that. The same tips might help you too, or others on your team. Today’s post is a quickie: easy reporting on Test Run – Test Case coverage using SQL.

Use Case

You want to trace Test Cases to Test Runs. Specifically, you need to identify Test Cases that are not included in Test Runs at any given time.


As with the last several posts, we find that Lucene, while fine for many querying needs, doesn’t deliver information like this… at least not in a way the doesn’t tax the system too much. Here’s some Wiki page mark-up you can use to find your Test Cases that are not part of any Test Run.
1 Test Cases Not Included in Test Runs

1 Query
#set($myQuery = “SELECT test.C_PK FROM WORKITEM test, PROJECT proj WHERE =>
test.FK_URI_PROJECT = proj.C_URI AND proj.C_ID = ‘${page.getProject()}’ AND =>
test.C_TYPE = ‘testcase’ AND NOT EXISTS (SELECT record.* FROM =>
* $myQuery

1.1 TestCases

=> indicates continuation on the same line.

Jiri Jandl is a Senior Support Engineer with Polarion Software’s European tech support team. He is based in Prague, Czech Republic.

Banner: It's all about solutions - Polarion Silver and Gold Support

Want to stay up to date on news from Siemens Digital Industries Software? Click here to choose content that's right for you

Leave a Reply

This article first appeared on the Siemens Digital Industries Software blog at