Help Contents
-
System Administration
-
User Guide & Application Administration Guide
-
Using Enterprise Tester
-
Application Administration
-
Searching & TQL
-
Simple Search
-
Advanced Search
-
Testing Query Language (TQL)
-
Aggregation
-
Fields
-
Accumulated Actual Duration
-
Actual Duration
-
Affected Version
-
Agile Runs Count
-
All Packages
-
AllParents
-
Assigned To
-
Assignee
-
Assignment
-
Assignment Id
-
Assignments Count
-
Attachment Count
-
Automated Tests Count
-
Blocked
-
Change Comment
-
Comment
-
Component
-
Created At
-
Created By
-
Description
-
Destination
-
Difficulty
-
Difficulty Level
-
Directly Related To
-
Editor
-
Editors
-
Entity Type
-
Errors
-
Estimated Duration
-
Estimated Less Actual Duration
-
Execution Totals
-
ExternalId
-
ExternalKey
-
ExternalUrl
-
Failed
-
Fields / Organisation
-
Fields / Package
-
Fields / Project
-
Fields / Relationship
-
Fields / Script
-
Finished At
-
Fixed Version
-
Has Agile Runs
-
Has Assignments
-
Has Attachments
-
Has Automated Tests
-
Has Coverage
-
Has Incidents
-
Has Requirements
-
Has Scripts
-
Id
-
Imported At
-
Incident Count
-
In Progress
-
Iterations
-
Key
-
Last Comment
-
Last Synchronized At
-
Last Updated At
-
Last Updated By
-
Name
-
Notes
-
NotRun
-
Number
-
Objective
-
Order Number
-
Organisation
-
Package
-
Parent
-
Parent And This Package
-
Parent Package
-
Passed
-
Post Condition
-
Pre Condition
-
Priority
-
Project
-
Provides Coverage
-
Query
-
Raised By
-
Related To
-
Related To All Packages
-
Related To All Parents
-
Related To Entity Type
-
Related To Fields
-
Related To Id
-
Related To Organisation
-
Related To Package
-
Related To Parent
-
Related To Priority
-
Related To Project
-
Related To Status
-
Related To Type
-
Relationship
-
Relationship Depth
-
Relationship Direction
-
Relationship Id
-
Relationships
-
Relationship Type
-
RelationshipTypeKey
-
Relationship Type Key
-
Remaining Estimate
-
Requirements Count
-
Resolution
-
Run By
-
Run Number
-
Script
-
Script Id
-
Script Priority
-
Script Status
-
Script Step Count
-
Script Type
-
Skipped
-
Source
-
Started At
-
Status
-
Step Actual Results
-
Step Data
-
Step Description
-
Step Expected Result
-
Step Notes
-
Summary
-
Test
-
Test Assigned To
-
Test Id
-
Test Scripts Count
-
Text
-
Ticket Id
-
Ticket Key
-
Ticket Url
-
Total Nodes
-
Total Results
-
Tracker
-
Type
-
Undetermined
-
Version Number
-
Version Of Script
-
Warnings
-
Accumulated Actual Duration
-
Functions
-
Indexes
-
Operators
-
Order By
-
SET
-
TQL For JQL Users
-
Types
-
Values
-
Aggregation
-
Simple Search
-
API
-
Using Enterprise Tester
-
Platform Plugins
-
Troubleshooting
-
Earlier Versions of this Documentation
-
Support & Bug Fixes
-
NextGen
-
Enterprise Tester 6.7.1
Execution Totals
Overview
When managing the execution of tests, it is valuable to be able to get an overview of not only progress, but a breakdown of testing outcomes (passes, failures etc.)
If you are using manual tests only (test scripts) or do not have a Duette license, then this can often be achieved by just using a "GROUP BY" on the status of script assignments:
GROUP BY Status { COUNT } WHERE EntityType = ScriptAssignment
If you are using Duette and have a mix of automated and manual test results, you will often want to get a combined view of progress across all tests. To do this, you can use the following "Total" fields.
Execution Totals
Other Totals
- Assignments Count
- Attachment Count
- Automated Tests Count
- Incident Count
- Iterations
- Requirements Count
- Script Step Count
- Test Scripts Count
- Total Nodes
- Total Results
How They are Calculated
For automated tests, these fields will provide counts as present in the imported result files.
For manual tests (test scripts) these counts will have a value of either 0 or 1, if the status matches the type of the field, this also means that some counts (such as Warnings, Errors, Iterations etc.) will always be 0, as they are not supported as possible outcomes for a script assignment (manual test).
Examples
To generate the execution status information (as used to display the "Execution Status" graph displayed above the execution grid) you can use the following query:
SUM(InProgress) AS 'In Progress', SUM(Undetermined) AS 'Undetermined', SUM(Errors) AS 'Errors', SUM(Failed) AS 'Failed', SUM(NotRun) AS 'Not Run', SUM(Passed) AS 'Passed', SUM(Skipped) AS 'Skipped', SUM(Warnings) AS 'Warnings', SUM(Blocked) AS 'Blocked' WHERE Project = 'Project X' AND Package = 'Cycle 1'
Here is what the results will look like:
This next example splits all the automated test assignments into two groups - those that have 1 or more errors OR 10 or more warnings, and the remainder which are considered "OK":
FACETED OrArgs(GreaterThan(Errors,0), GreaterThan(Warnings,10)) AS "Require Review", Unmatched() AS "OK" { COUNT } WHERE EntityType = TestAssignment
Here is what the results will look like for that query: