The run duration field is calculated by just taking the number of seconds by the time a user clicks run in ALM to the time that the user ends the run in ALM. Often times this field does not match what is displayed in the ''Exec Time'' column for the steps. The reason for this is because the run duration is the overall time and the ''Exec Time'' just shows when that particular step was passed. So for example, if a user goes to run a manual test and they click run then ''Begin Run'' the timer starts, then oftentimes the user will go through the steps of the test, then afterward they will highlight each step and select pass which will record the time that the test step was passed. The discrepancy in time that you see is how much time that the user spent before actually passing the first step. The run duration is really in place to keep users from ''fast passing'' tests, that way you can tell that they actually spent time with the test runner open and actually ran the test instead of going in and clicking ''pass all.'' If you want to try and reproduce you can run a manual test and then click begin run, then let a few minutes pass and pass the steps and end the run, if you do this you should end up with a similar scenario of what happened in the run that you mentioned above.