How to create test cases that don't introduce risk?

I’m just learning about testing in UiPath, and I have a general question. It seems the “UiPath way” to test a workflow is to create a test case and then put a verification activity in the THEN section that uses the same UiPath activity which you are trying to test.

My general question is a logical one. If there is a bug in an activity, how would using the very same activity to test it catch the flaw? Is there a “best practice” way to verify a UI activity without using the very same one?

@Terry_Marr

Verify execution can be done in may ways like with ui element,with a value as well and comprisions

I agree with your point…but in verify execution you need to soecifically verify for last element but would verify for something that would be appearingn or happening after the last step of tested xaml is executed …

Cheers

thank you Anil. My follow up question: is there a way, then, to verify using an OR situation? For example: verify that one element appears OR that the URL says x?

@Terry_Marr

Yes you can …you can use a parallel activity and use two verify states…and if either of it is successful then verification eould be successful

Cheers

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.