Well, Russ, I’m trying to make sure the UI doesn’t return blank, which
is what it’s doing some times. Everything looks fine-ish to the user,
but it’s really not. So, I’ll probably just write the API test to
include with my tests so that we can tell easily that it’s not working
and be able to mitigate the issue when it arises.
And that’s completely fine, Amanda. You know your intent and you know what you need to do to “mitigate the issue”. Said another way, rules and guidelines are fine, to a point, but when they don’t quite fit, or they seem to actively prevent you from moving forward, you gotta do what you gotta do.
Confession: I’ve never looked at the Katalon API testing stuff - it might be fantastic and perfectly fine, but I see so many requests for help using it, I do wonder. So, yeah… I use JS directly for all webservice-type/API testing.
But again, that’s just me B)
Hope that clarifies?
As to your “sometimes it returns blank” problem…
This, to me, is a signal that the app itself has issues that need to be addressed. I’d first be absolutely certain that the underlying code is handling all asynchronous calls correctly. From your description, I believe it is not. Fixing this is not your job, this is a developer’s job. Your job (at this stage) is to point out that:
the app is behaving inconsistently under some conditions making it very difficult if not impossible to test (using automation testing, of course).
Don’t pull your punches - be forthright, tell them, just like that.
Further, if this issue manifests itself in a situation where a user may lose work (i.e. loss of data and/or significant work-time), raise it as a critical bug on the bug tracking system (I assume you/they have one of those?) and be even more forceful as to the untestability of the current state of the app.
Hope that’s helpful.