Exporting Test Results

Test results can be exported as a formatted PDF report or as an Excel workbook, for both automation runs and manual test runs. The PDF carries the result summary, run details, execution parameters, and optionally the execution detail of every step in a test case. Export a single job on its own, or select several and roll them into one consolidated report under a name you choose. This article covers both.

1. Start the export

To export one job, select its row in the Test Results grid and choose Export Results, then Export as PDF. The same options are available from the row's action menu, and from the download option inside an open test result.

To export several jobs at once, tick the rows you want and use Export, then Export as PDF, in the toolbar that appears at the bottom of the grid. You get one document covering the whole selection rather than a file per job.

Tick several rows, then export the whole selection as one PDF.

2. Choose what to include

The Export PDF dialog asks how much detail you need. The header tells you how many test cases are in scope before you commit.

• Test case summary. Pass or fail status for each test case, with the failure message shown inline. The lighter option, and the right one for sharing an outcome.
• Step-level detail.  Adds the inputs, outputs, and status of every step inside each test case. A step here is a Scenario step, the Action being invoked, rather than the individual commands within it. It includes the summary, so you never trade one for the other.

Your last choice is remembered for next time.

The Export PDF dialog for a single test job.

Naming a multi-job report. When more than one job is being exported, a Report Name field appears. It becomes the report's title inside the PDF, appears in its Report Details panel, and is used for the downloaded file name. It is limited to 100 characters, and Generate stays disabled until you enter one. A single-job export needs no name; the file is named after the test job.

A multi-job export needs a report name before it can be generated.

3. Generate and download

Choose Generate. A progress dialog appears while the report is compiled, and you can Cancel while it works. The file then downloads through your browser and an Export completed confirmation appears. Single-job files are named after the test job, multi-job files after your report name.

What the PDF contains

A single-job report opens with a header banner carrying the job ID, test job name, environment, start time, status, and duration. Below it sit result count cards with the pass rate, a link back to the live result in ACCELQ, run details, any execution parameters the job used, and the test case summary. Choosing step-level detail adds a per-test-case block with a table of its steps.

A multi-job report opens with your report name, combined result counts across the whole selection, a report details panel, a Jobs Included table, and one continuous table of every test case tagged with the job it came from. With step-level detail, each job then follows in full, starting on its own page.

If the run was aborted or errored, a red banner sits directly under the header so nobody reads partial numbers as a final outcome.

Manual test runs

Manual test results export in exactly the same way. The same entry points, the same dialog and options, and the same consolidation when you select several runs at once. A single run exports on its own; a multi-run selection produces one report under the name you give it.

What differs is the execution detail. Step-level detail carries each test case's steps with their expected result and the outcome the tester recorded, in place of the inputs and outputs an automated step produces.

How re-runs are handled

A job and its re-runs appear as separate rows in the grid. Selecting a re-run together with its parent consolidates the two, so a test case is never reported twice and each one reflects its latest execution. A re-run selected without its parent has nothing to consolidate into, so it is reported as a job in its own right. The dialog header always states what will be produced before you generate.

Re-runs whose parent is also selected are folded into the parent job's result.

Exporting to Excel

Choose Export as Excel from the same menus. A single job produces one workbook of its results. Selecting several jobs produces one workbook with each job on its own sheet, which keeps a multi-job export readable rather than merging everything into one long table.

Excel carries the result data rather than the formatted report layout, so reach for it when you need the numbers for analysis and for PDF when you need something to share or archive.

Good to know

• The links are live.  Job IDs, scenario IDs, and test case IDs in the PDF open the corresponding result in ACCELQ for anyone who has access to it, so the document stays connected to the full evidence.
• You can export mid-run. Automation jobs that are still in progress can be exported, giving you a snapshot of results so far.
• Large step-level exports take time. Past roughly a hundred test cases a size warning appears next to the option. It is advisory, so you can still generate, but expect a long document and a longer wait.
• Times are shown in UTC. Start times, run windows, and the generation time are printed in UTC, so the document reads identically for every reader.
• Screenshots stay in ACCELQ.  The PDF covers steps with their inputs, outputs, status, and failure messages. For screenshots and the command-level log inside a step, open the result in ACCELQ.
• Some rows cannot be exported. Scheduled, recurring, and CI entries, runs still in setup, and errored jobs with no executed test cases have no result content to export.
• If you see Result too large. The stored result is too big for the server to return. Export with test case summary instead of step-level detail, or export fewer jobs at a time.