Postman Collection Run History Badge

WHAT IT DOES

This userscript adds a compact run history monitor to your Postman collection pages. It reads collection run history entries from the page—including run timestamps, status (passed, failed, error), duration, and request count—and displays a color-coded badge directly in the collection header. The badge summary shows the total number of runs and the latest run status with a color indicator: green for passed, red for failed, and yellow for error. A detailed history list shows recent runs with color-coded status indicators, relative timestamps, duration, and request count. Average duration is calculated across all runs for performance insights. A "View Runs" button opens the full run history, and a "Copy" button exports the history to your clipboard. This is invaluable for API developers, QA engineers, and DevOps teams who need to monitor test run results, track performance trends, and quickly identify failing tests without navigating away from the collection page.

WHERE IT RUNS

The script runs on all Postman web application pages at *.postman.com/*, with automatic detection of collection pages and workspace views (paths containing /collection/ or /workspace/). It works across all Postman interfaces by using multiple selector strategies to find run history entries, status indicators, durations, and request counts. The script detects dynamic content loading and re-renders the badge when the run history updates. It runs across the entire Postman domain, ensuring coverage whether you're viewing a collection, a workspace, or the runs list.

HOW TO USE

Install the script via the BotGentz extension and navigate to any Postman collection page. The run history badge will appear in the collection header automatically. The badge summary shows total runs and the latest run status with a color indicator. The detailed history list displays recent runs with color-coded status, relative timestamps, duration, and request count. Average duration is shown below the history list. Click the "View Runs" button to open the full run history tab. Click the "Copy" button to export the full history to your clipboard for reporting or analysis. Use the panel controls to customize your experience: toggle the run history badge on or off, show or hide the detailed history list, enable or disable the average duration display, or adjust the number of recent runs to show (3-50). The "Refresh" button manually rescans the page for updated run history.

THE MECHANISM - RUN HISTORY EXTRACTION, STATUS DETECTION, AND METRICS AGGREGATION

This script identifies run history entries by scanning the DOM for known Postman run elements. It uses a cascading selector strategy that looks for run entries (.run-entry, .run-item, .history-item, .collection-run), then extracts timestamps from date elements or relative time strings, status from status badges or class names, duration from duration elements, and request counts from count elements. Status is normalized to "passed," "failed," or "error" using text matching and class analysis. The script calculates average duration across all runs with positive duration values. The badge is built as a DOM element with inline styles and inserted into the collection header. The history list displays runs in reverse chronological order with color-coded status indicators. The "View Runs" button attempts to locate and click the runs tab or history link using selectors.

THE PANEL

The control panel appears as a floating, draggable element that you can position anywhere on the Postman page. Drag by the header to reposition it, and the position is saved per site using GM_setValue so it stays where you left it across sessions. Release the panel near any edge and it snaps into place, keeping your workspace organized. Click the panel header to collapse it into a small bubble showing only the document emoji (📅), minimizing distraction while keeping controls accessible. Drag from the bubble to restore the full panel. The panel automatically resizes to fit its content and includes all setting toggles, the recent count control, action buttons, and a status legend. Press the Escape key to quickly collapse the panel to its minimized state. The panel remains visible across page navigation within Postman, with the run history updating automatically as you move between collections.

PLEASE NOTE

This script requires the free BotGentz extension to function. It is designed for Postman users who need to monitor collection run history and test results. The script reads only visible run history data from the DOM—it does not access Postman's API, your account credentials, or any sensitive information. All settings (badge visibility, history list toggle, average duration toggle, recent count, and panel position) are stored locally using GM_setValue and never leave your browser. The script does not modify your Postman data—it only reads and displays visible run history. The run history extraction relies on the run entries being present in the DOM; if the runs tab is not loaded, the script may show limited information. If Postman updates its website structure, the script may need to be updated to match new selectors. The "View Runs" button attempts to find the runs tab; if the button location changes, you may need to navigate manually.