Same Timer name in different scripts
We have a question in regarding to custom timer in Silk Performer.
We have two different test scripts in our project and will run together. We like to time how much time it takes to open up a Task in our product.
Script 1 will open the task from a report page. Script 2 will open the task from the search result page. The navigation path is different in both scripts, but the landing page "Edit Task" page is the same. We are not timing the whole navigation flow. If we just time it from the moment we click on the Task Name, till the Edit page is opened, and this operation is same in both scripts, should we have a timer with same name in both scripts. What is the good practice here?
Our current scripts.
What are the benefits for having a timer with same name in different script and what are the disadvantages for it?
We are timing the same operation here, and it is that to open the task. The navigation flow is different, but at the end, we just timing to open the task. For this kind of case, should we use the same timer name since the operation is the same, and just the navigation flow is different.
Also, if we have same timer name in two different scripts, what that mean to the report result at the end if we run both scripts in a suite?
I'd keep them named the same - in the final report, if you ran multiple scripts as part of the load test there will be a section for each script that ran during the test - it will be clear which timer belongs to which script.