What you will achieve
By the end of this tutorial you will have:- A custom field on the test run object that stores checklist data
- The checklist rendered and editable on the test run’s report page
- A test run template that pushes the checklist automatically to every test run created from it
$checklistService.getChecklistView().testRun($testRun).checklist("testDone").render(), which renders the testDone checklist inline.
Prerequisites
- Administrator access to the Polarion project (Project Administration)
- Checklist installed and licensed on your Polarion instance
- At least one existing test run or test run template to work with
1
Create a custom field to hold the checklist
The checklist itself is stored as plain text in a custom field on the test run object.
- Go to Project Administration > Custom Fields.
- Create a new custom field of type Text (multi-line plain text).
- Give it a short, memorable ID — for example
testDone.
Text (multi-line plain text).Multiple checklists are fineYou can create more than one checklist custom field on the test run object — for example one for
testDone and another for a separate review gate. Each is configured and rendered independently.2
Show the checklist on the Test Run Report page
Next, expose the checklist field on the report page that testers actually see.Replace
- Open your test run, click the gear/actions menu, and choose Customize Test Run Page.
- Choose Customize Shared Report if it’s available, so the same layout applies to both the test run and its template. Otherwise you will need to repeat this step for every individual test run.
- Drag a Script Block Widget onto the report page, wherever you want the checklist to appear.
- Enter the following line into the Script Block Widget:
testDone with the ID of the custom field you created in Step 1.- Save the report.
3
Define a checklist template
Rather than typing checklist items by hand on every test run, define them once on a test run template so every new test run starts pre-populated.
- Open your test run template by clicking the template link in its properties.
- If the checklist widget is not visible on the template’s report page, repeat Step 2 for the template itself.
- Enter your checklist items directly into the checklist form extension on the template.
testDone field is populated with a copy of the same checklist items defined on the template (for example Smoke tests pass, Regression pass, Sign-off recorded).Verify in applicationWhether template item edits made after a test run is already created automatically re-sync into that existing test run’s checklist should be confirmed in your environment before relying on it for audit purposes.
Next steps
- Your First Checklist — the equivalent walkthrough for work items
- Set Up a Plan Checklist (Tutorial) — apply the same pattern to Polarion plans
- Concepts — understand result states, templates, and workflow gates before configuring gate enforcement on your test runs
Sources
Sources
KB Articles
- Setup New Plan Checklist
- Setup New Test Run Checklist
- Setup new Work Items checklist
proc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistServlet.javaproc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/ChecklistConf.javaproc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/IChecklistService.javaproc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/wf/ChecklistMandatoryChecked.javaproc-checklist-src/com.nextedy.polarion.checklist/src/com/nextedy/polarion/checklist/internal/ChecklistService.java