TruClient error handling
Unless I am missing something that is right in my face, there is no way I can trap an error message on a page and then fail a transaction.
In the HTTP world, I would very simply:
web_global_verification("Text/IC=An unexpected error has occurred.","Fail=Found","ID=unexpected error", LAST);
If someone can show me how I am being an idiot, please do so.
Adding this comment to bump the vote and attempt to expedite the long time due solution.
Are there any workarounds or recommended best practices to carry out the same ? Its also critical to get some data used by script for that failure points and adding verify for each step will be a overkill for performance testing perspective. This isn't a functional validation in the sense where time trade-offs are done for accuracy. If we add verify for each step then achieving target rates for hits or transactions per unit time will be challenging as each script will be slow due to spending lot of time in verification itself.
Everyone one wants that catch and finally blocks sooner if they want to use this technology in more robust way for performance.
This is a very old thread and is probably not relevant in current versions.
Please indicate the exact issue you're experiencing and more details (like version and application details) in a new thread.
Hi @Edo Nir
- Init - Login to Salesforce. Close open tabs if any and landup on Dashboard page.
- Action - Two blocks
- 1. Mainflow - User navigates from Dashboard to other pages and completes the intended user journey. The end state should be user is back on Dashboard (similar to Init).
- 2. Catch block to capture any error occured in the Mainflow and handle it.
- The catch block includes logging out of the application and then logging back into the application; followed by closing any open tabs leftover in previous steps. The end state should be user is back on Dashboard (similar to Init).
- End - Log out
I have two solutions. The first as described is a handler which calls a handler-function() to clear up my staff. Works fine, but returns to the place where my script stepped into the errorsituation.
The second one is to add a Exit(Action) with status Fail which ends all running transactions.
Hope that helps