Skip to content

Custom Campaign Exports

This reporting feature enables you to generate a custom export for a campaign, iteration, or test suite thanks to a wizard that helps you select the perimeter and the data to export.

Custom exports are in .csv format.

You can generate a custom export from the Reporting workspace via the button Ajouter, then Add a custom export.

Create a custom export

Custom Export creation page

A custom export creation page is divided in two parts:

  • on the left, there is the export name, panel to select the perimeter, and summary of the selected attributes;
  • on the right, the list of the attributes that you can select, organized by entity.

To save a custom export, you must:

  • enter its name;
  • select its perimeter;
  • select at least one attribute.

Once you have saved the custom campaign export, from its consultation page, you can modify it by clicking on the button Modify custom export or download it by clicking on the button Download custom export.
From this page, it is also possible to choose whether to export only the last execution or all executions of each test plan item.

Choose the perimeter

For custom exports, what you can select as a perimeter can be:

  • a campaign folder;
  • a campaign;
  • an iteration;
  • a test suite;
  • a multi-selection.

Select attributes

The entities that contain the attributes you can select are:

  • Campaigns;
  • Iterations;
  • Test suites;
  • Test cases;
  • Executions;
  • Execution steps;
  • Issues.

You can select each attribute independently from the others.

To select an attribute, you must drag and drop the attribute from the panel Select the attributes on the right to the Selected attributes one on the left.

For the entities Campaigns, Iterations, Test suites, Test cases, Executions, and Executions steps, you can select their associated custom fields as attributes. The color of the pill tag is then slightly lighter than for the Squash native attributes. The custom fields appear according to the selected perimeter.

Custom fields

Structure of the Custom Export file

Column Name in ExportDescription
CPG - LabelCampaign label
CPG - IDCampaign ID
CPG - ReferenceCampaign reference
CPG - DescriptionCampaign description
CPG - StateCampaign status
CPG - Progress rateCampaign progress rate
CPG - MilestoneMilestone associated to the campaign
CPG - Scheduled start onCampaign scheduled start on
CPG - Scheduled end onCampaign scheduled end on
CPG - Actual start onCampaign actual start on
CPG - Actual end onCampaign actual end on
IT - LabelIteration label
IT - IDIteration ID
IT - ReferenceIteration reference
IT - DescriptionIteration description
IT - StateIteration status
IT - Scheduled start onIteration scheduled start on
IT - Scheduled end onIteration scheduled end on
IT - Actual start onIteration actual start on
IT - Actual end onIteration actual end on
SUI - LabelSuite label
SUI - IDSuite ID
SUI - DescriptionSuite description
SUI - Execution statusSuite execution status
SUI - Progress rateSuite progress rate
TC - ProjectName of the test case's project
TC - MilestonesMilestone(s) associated to the test case
TC - LabelTest case label
TC - IDTest case ID
TC - ReferenceTest case reference
TC - DescriptionTest case description
TC - StatusTest case status
TC - WeightTest case weight
TC - NatureTest case nature
TC - TypeTest case type
TC - DatasetTest case dataset
TC - PrerequisiteTest case prerequisites
TC - Number of associated requirementsNumber of requirements associated to the test case
TC - Linked requirement IDID of the requirements linked to the test case
EXEC - IDExecution ID
EXEC - Execution modeExecution mode (manual ou automatic)
EXEC - StatusExecution status
EXEC - % PassedExecution success percentage
EXEC - UserLogin of the user who executed the test case
EXEC - Execution dateExecution date
EXEC - CommentsComments linked to the execution
EXEC_STEP - Number of test stepExecution step number
EXEC_STEP - ActionExecution step action
EXEC_STEP - ResultTest step expected result
EXEC_STEP - StatusTest step execution status
EXEC_STEP - UserLogin of the user who executed the test step
EXEC_STEP - Execution dateTest step execution date
EXEC_STEP - CommentsComment linked to the execution step
EXEC_STEP - Number of linked requirementsNumber of requirements linked to the execution
EXEC_STEP - Requirement linked to test stepID of the requirements linked to the execution step
BUG - Number of issues linked to the executionNumber of issues linked to the execution
BUG - ExecutionKey(s) of the issue(s) linked to the execution
BUG - Number of issues linked to the execution stepNumber of issues linked to the execution step
BUG - Execution stepKey(s) of the issue(s) linked to the execution step