Test Case Note Recorder

WHAT IT DOES

Provides a structured note recorder for test cases and quality assurance activities. The script displays a comprehensive log with configurable fields including Test Case ID, Test Name, Status (Pass/Fail/Blocked/Skipped), Actual Result, Expected Result, Steps to Reproduce, Environment, Browser/Device, Tester, Notes, and Test Date. Each entry is automatically timestamped, and you can add custom tags for easy categorization. The log includes search and filter capabilities by status, tester, or test case ID. You can export the log as formatted text or JSON for test reporting, audit trails, and QA documentation. Per-test-session logs are saved per test run identifier or project name.

WHERE IT RUNS

Works on all websites (match pattern *://*/*), making it perfect for test management platforms, QA dashboards, CI/CD pipelines, bug tracking systems, or any web-based quality assurance workflow. Each test run or project gets its own independent log, allowing you to manage multiple test sessions simultaneously. The log state is saved per test run identifier, ensuring continuity across sessions and page reloads.

HOW TO USE

Install the script and the test log appears in the panel. Enter a test log identifier or project name to associate the log with a specific test run. Fill in the test result details: Test Case ID and Test Name (required), select a status, optionally add tester, environment, browser, expected result, actual result, steps to reproduce, notes, and tags. Click "Add Test Result" to record it. Use the search field to filter entries by ID, name, tester, or tags. Use the status filter to show only Pass, Fail, Blocked, or Skipped results. Add custom statuses to match your workflow. Use the export buttons to copy the log as text or JSON to your clipboard. The script saves your progress automatically as you work.

REAL MECHANISM: TEST-RUN-KEYED PERSISTENCE WITH MULTI-FIELD QA CAPTURE AND FILTERABLE LOGGING

This script uses a test-run-based storage architecture where each test session gets its own isolated log state. The getTestLogId() function retrieves the current log identifier from GM_setValue or generates a new one. Data is stored using GM_setValue with a key format of "test_log_" plus the log ID, ensuring data isolation between test runs. The data structure includes an entries array where each entry has an id, testCaseId, testName, status, tester, environment, browser, expectedResult, actualResult, steps, notes, tags (array), and timestamp. The statuses array stores user-customizable status names with default colors mapped via statusColors. The renderTestLog() function applies dual filtering: text filtering using includes() on testCaseId, testName, tester, tags, and notes, and status filtering using exact match. Entries are sorted chronologically (newest first) using sort((a,b) => b.timestamp - a.timestamp). Each entry is rendered as a flex row with a colored left border matching the status color, with test case ID and name, status badge, timestamp, tester, environment, browser, expected result, actual result, steps, notes, and tags rendered as chip-style spans. Timestamps are formatted using toLocaleString() for human-readable display. The export functions generate formatted text with a header, entry count, and each entry's fields in a structured QA report format, or JSON with the full data structure including statuses. All operations are reactive, with automatic persistence and UI updates through saveTestLogData() and re-render.

THE PANEL

Drag the panel anywhere on screen by clicking and holding the header. It snaps to screen edges when released. Collapse it to a small bubble by clicking the minimize button, and expand it back by clicking the bubble. Resize the panel from any corner. Press Escape to close the configuration panel. Your position and size preferences are saved automatically per site.

PLEASE NOTE

This script requires the free BotGentz browser extension which provides the BGPanel framework and storage APIs. All data (entries, statuses, tags, and test log identifiers) is stored locally in your browser using GM_setValue and never sent anywhere. No analytics, no tracking, no external calls. The script only reads the current test log identifier to isolate test records and never accesses user data, passwords, or sensitive information. Logs are saved per test run identifier, so ensure you enter a unique identifier for each test session or project you track.