Test Executions

Execute tests, record results, and collaborate with your team.

Understanding Test Executions

Test Executions represent the actual testing work in TestPilot - where test cases are executed, results are recorded, and defects are discovered. A Test Execution is an instance of a test case within a test run. When you add a test case to a test run, an execution record is created that tracks current status, assigned tester, execution history, time tracking, test results, linked defects, and team comments.

Key Features: Status Tracking, Evidence Collection, Defect Management, Team Collaboration

View Modes

List View (Default)

Comprehensive table view.

Best For:

• Detailed status tracking
• Data export and reporting
• Bulk operations
• Granular filtering

Features:

• Sortable columns
• Resizable columns
• Column visibility toggle
• Inline editing
• Bulk selection
• Quick actions menu
• Row expansion for details

Kanban View

Visual board layout by status.

Best For:

• Visual progress tracking
• Team collaboration
• Agile workflows
• Quick status updates

Features:

• Drag-and-drop status updates
• Visual workflow representation
• WIP limits per column
• Color-coded priority
• Assignee avatars
• Card quick actions

Tree View

Hierarchical organization.

Best For:

• Complex test suites
• Module-based testing
• Large test runs (200+ tests)
• Organized execution

Features:

• Collapsible/expandable folders
• Test set organization
• Label grouping
• Module categorization
• Parent-child relationships
• Bulk selection by folder

Test Statuses

Status	Description	Required Information
Passed	Test executed successfully, all steps completed as expected, no defects found	Execution time (auto-tracked), Environment notes (optional), Screenshots (optional)
Failed	Test executed but failed, defect or issue identified, requires bug logging	Failure reason (required), Steps to reproduce, Expected vs. Actual results, Screenshots/videos, Bug ticket link
Blocked	Cannot execute test, dependency or resource issue, requires resolution	Blocking issue description (required), Required resolution, Estimated unblock date, Responsible party
Not Run	Test not yet executed, default status for new tests, pending execution	No information required
In Progress	Test currently being executed, tester actively working on it, temporary status	Auto-set when test opened for execution
Skipped	Test intentionally not executed, not applicable for this run, requires justification	Skip reason (required), Approval (if required), Alternative coverage

Execution Interface

When you open a test execution, you see a comprehensive modal with multiple tabs:

Header Section

• Test case ID and title
• Priority and complexity badges
• Current status dropdown
• Assigned tester
• Execution duration timer

Details Tab

• Test case description
• Preconditions
• Test data requirements
• Environment setup

Steps Tab (Primary)

• Numbered test steps
• Expected results per step
• Actual results input
• Step-by-step status marking
• Screenshot attachment per step

History Tab

• Execution history
• Previous results
• Status change timeline
• Comparison with past executions

Defects Tab

• Linked bugs
• Create new defect
• Bug details and status
• Resolution tracking

Attachments Tab

• Screenshots
• Videos
• Log files
• Test data files
• Evidence collection

Defect Management

Quick Defect Creation

1. Mark test as Failed
2. Click "Log Defect" button
3. Defect form pre-populated
4. Adjust as needed
5. Submit

Auto-filled fields:

• Title: From test case name
• Description: Test steps + actual results
• Priority: Derived from test priority
• Component: From test label/set

Link Existing Defect

1. Mark test as Failed
2. Click "Link Defect"
3. Search defects
4. Select matching bug
5. Link

Benefit: Connect test to already reported bugs

External Bug Tracker

1. Mark test as Failed
2. Click "Create Jira Issue"
3. Jira form opens (integrated)
4. Fill additional Jira fields
5. Submit to Jira

Result: Jira issue created and automatically linked

Collaboration Features

Comments & Notes

• Test-level comments: General discussion
• Step-level comments: Specific step issues
• @mentions: Notify team members
• File attachments: Share evidence
• Rich text formatting: Better clarity

Execution History

Tracks:

• Status changes
• Comments added
• Assignments changed
• Test cases added/removed
• Configuration updates
• Reports generated

Real-time Updates

Provides:

• Live status changes
• Team activity feed
• Auto-refresh every 30 seconds
• Instant notifications
• Collaborative editing indicators

Advanced Features

Custom Fields

Examples:

• Browser Version (for web testing)
• Device Model (for mobile testing)
• Test Data Set Used
• Customer Account ID
• Transaction ID
• API Endpoint

Execution Templates

Benefits:

• Standardize documentation
• Required sections enforced
• Auto-populated fields
• Consistent quality

Execution Macros

• Pass and Next: Mark passed, open next test
• Fail and Log Bug: Mark failed, create bug
• Bulk Pass Smoke: Pass all smoke tests

Best Practices

Execution Strategy

1. Phase 1: Smoke Tests (Quick validation)
2. Phase 2: Critical & High Priority
3. Phase 3: Medium Priority
4. Phase 4: Low Priority

Quality Documentation

• Passed: Brief note, execution time
• Failed: Detailed steps, screenshots, bug link
• Blocked: Clear blocker description, resolution needed
• Skipped: Justification, approval if required

Evidence Collection

• Full screen screenshots (not partial)
• Include browser chrome (URL visible)
• Clear error messages shown
• Proper naming convention
• Videos for complex issues

Troubleshooting

Cannot update test status

1. Verify test run is "In Progress" status
2. Check user permissions
3. Refresh browser to renew session
4. Contact admin if permissions issue

Attachments not uploading

1. Check file size (max 25 MB per file)
2. Use supported formats (jpg, png, pdf, mp4, zip)
3. Upload one file at a time
4. Try different browser if issue persists

Slow performance

1. Enable pagination (50 tests per page)
2. Use filters to reduce visible tests
3. Switch to List view (faster than Kanban)
4. Disable auto-refresh if not needed

Next Steps

• Test Runs - Manage test campaigns
• Reports & Analytics - Generate execution reports
• Best Practices - Execution strategies
• Dashboard - Monitor progress