how to make sure that element is clickable at least 98% time in blueprism?

[Pooja_Kumari_411]

Is there a way to achieve 98% success rate on clicking any element, lets say Submit button in a web page .

------------------------------
Pooja Kumari
------------------------------

[VivekGoel]

What's the logic behind 98% success rate?.. Whether the button is clickable or not ,depends on the end application and your connection speed.
 It's always a good practice to use the wait stage to do a check on the button (if its problematic) if it has appeared before it's clicked. Also if you see abnormality in the button load times, you can build a retry logic to try clicking on the button after say 5 seconds for 3 times before giving up..
That way you build resilience in the CLICK of that button,

------------------------------
Vivek Goel
"If you like this post, please press the "Recommend" Button.
------------------------------

[Pooja_Kumari_411]

That's true, but my question is how to ensure that out of 100 times , element should be working 98 times atleast. Is there a definite way to make sure of that?

------------------------------
Pooja Kumari
------------------------------

[Yeswa_Vaibhav_1]

Hi Pooja,

But why are you searching for atleast 98% click success ratio of button. Are you facing any issue? Could you please explain it more clearly.

Regards,

------------------------------
Yeswa Vaibhav Alwar Nerella
Associate Consultant
Capgemini
Asia/Kolkata
------------------------------

[wleung · Accepted solution]

Hello Pooja,

As the others have asked, we can probably provide more help if we understand what the actual requirement is.

When automating an application, whether the button (or any element) has a specific attribute is completely up to an application. For example, if you can imagine a very simple JS enabled web application where the "Submit" button is enabled based completely on a random value generator (say enabled if the randomly generated value between 0 and 1 is > 0.5.) Such an application can artificially have a Submit button that is enabled around 50% of the time whenever the page source (and the JS code) executes. In these cases, no automation solution can "guarantee" a 98% success rate on click.

From you simple description, I almost wonder if the use case isn't to leverage the RPA solution to do application testing and you are trying to load test a web application to ensure the capabilities of certain elements. If that is the case, then I think you question isn't so much as how to ensure an element can be clicked 98% of the time but that the element is presenting/behaving correctly 98% of the time. There would be many ways to capture this metric but probably the simplest way would be to create a Work Queue Item for each execution record. So every time a test is run, create a work queue item for that run. If the run hits a problem on certain UI elements then mark that run as an exception and in the exception details add the information about that UI element. Finally, you can then run a regular report on the Work Queue to retrieve information such as: 1)total number of runs where no element caused a problem; 2)collate on specific exception details which contains "Submit Button" for example to get instances where application failed because the Submit button was not available on the page. This will also allow you to find out, over any defined time period, what is the success rate of the Submit Button (when does it load correctly so Blue Prism can detect it as available and is able to click on it.)

Hope those ideas help.


------------------------------
Wing Ling Leung
Senior Product Consultant
Blue Prism Professional Services
------------------------------