I would like to propose to add a native, built-in timer to the test execution view in Testiny that allows testers to track time effortlessly while running tests, automatically populating the Time Spent field upon submission.
The Problem
Currently, tracking how long a test execution takes requires manual effort - either starting an external stopwatch, jotting down timestamps, or guessing the duration after the fact. This introduces friction, human error, and inaccuracies into our test logs.
Proposed Solution
-
Integrated Timer Widget: Include a clean start/stop timer widget directly within the test execution interface.
-
Workflow Integration:
-
The timer can be initiated upon opening the test or via a prominent “Start Timer” button when beginning execution.
-
It runs quietly in the background as the tester works through the steps.
-
-
Automatic Population: When the tester is ready to submit their result (Pass/Fail/Blocked), stopping the timer automatically inputs the elapsed duration into the Time Spent field on the result form. (Testers should still retain the ability to manually adjust or override the time if needed, e.g., if interrupted).
Value & Benefits
-
Zero Friction: Removes the need for external tools or mental estimations.
-
Higher Data Accuracy: Captures precise execution durations rather than rough estimates.
-
Better Forecasting: Feeds accurate, consistent time metrics into run-level analytics, improving resource planning and duration forecasting for future test runs and cycles.