The time taken to get the result is identified in the selenium test itself

The time taken to get the result is identified in the selenium test itself based on what is going on with the UI of the extension window.

Actually, It can be taken from the browser extension since its already stored in the browser extension local storage with the ff two options

1. store the value in hidden HTML and get it from this one. this option worked but it goes in the unproper way, because to get the HTML element, the extension should be opened in a new tab as a page which is not good.

2. get from local database getting the local database of the chrome extension with the selenium test is a bit challenging.

so due to these problems identifying the time taken in the selenium itself based on what is going on the browser extension window is quite a good option.

For this what I did is.

After the icon gets clicked the timer starts and then it checks for the result page using the status detection text means the ff image. It checks for this image again and again if it founds it means the fetch ended and then the timer ends, if not it just simply calls the check function again and again.

here some problem might occur, if the user clicks other parts of the screen and the extension windows get closed, the sikuli library couldn't find the image over the current screen, it just simply loops through check loading function over and over. so to avoid this problem its good idea to simply sit and look the screen while the selenium test is testing this extension.

Closes #4 (closed)