PR #172 added various error handling for when OTP generation failed, and also added a retry of the OTP generation.
The underlying cause was fixed in PR #182 (issue #170 ) and in that PR the code was PR #172 was reverted, which was generally good. We do not want to automatically retry OTP generation in the tests, we now want it to fail straight away if something goes wrong.
But it will be nice if it fails more nicely, and gives more clue about what went wrong.
Put back the error checking code from PR #172 that waits for the Verified text to come on the UI, and that checks isErrorMessagePresent. And if something goes wrong, then fail with a nice message.
PR #172 added various error handling for when OTP generation failed, and also added a retry of the OTP generation.
The underlying cause was fixed in PR #182 (issue #170 ) and in that PR the code was PR #172 was reverted, which was generally good. We do not want to automatically retry OTP generation in the tests, we now want it to fail straight away if something goes wrong.
But it will be nice if it fails more nicely, and gives more clue about what went wrong.
Put back the error checking code from PR #172 that waits for the
Verifiedtext to come on the UI, and that checksisErrorMessagePresent. And if something goes wrong, then fail with a nice message.