Correct estimation of the operation execution time about rpa-python HOT 2 OPEN

Example of a script:

r.click('Start_menu.png')
r.click('Open_file.png')

How can I determine that the first line of the script has already been executed? Do I understand correctly that a screenshot of the screen is compared before the operation and after the operation? If the screenshots do not match, then there is some result after the click and you can set the result of the function to True? Do I understand the logic correctly?

from rpa-python.

Hello!
Conducted the following research on measuring the execution time of a test script:
Source data:
A qemu/kvm-based virtual machine.
AlmaLinux OS 9, office suite R7-Office

The script uses the following algorithm (turbo_mode = True):

1. Open the home folder [r.click()]
2. Select the Download folder [r.click()]
3. Open the Excel file [r.dclick()]
4. Confirm the message about the trial version office suite [r.click()]
5. Open the drop-down menu in the row numbers field of the table [r.click()]
6. Select "Add line" [r.click()]
7. In the added line, fill in all the fields [r.keyboard() + modifier [tab]]
8. Click the "Save document" icon [r.click()]
9. Exit from the Office programm [r.click()]

Time measurements were performed in 3 ways:

1. r.timer() after each command was executed, then the sum of the time values of all points was completed
2. datetime.datetime.now(), the start time before point 1 and the finish time after point 9, then the difference between them is calculated
3. Manual measurement + manual execution of all stages - stopwatch on a smartphone

The values obtained:

1. sum_rtimer = 44.39
2. delta_datetime = 32.64
3. Stopwatch = 34.90 (human factor)

The analysis of the timer() function showed that no measurements are made inside rpa-python, but simply the contents of the file are read rpa_python.txt , which creates an external tagui component, which presumably contains the execution time of the next request (operation). Logically, it is fair to take time costs directly from the query executor. But it is unclear why the results are so big? Or does it imply other information?

from rpa-python.