Not recommendations, per se – My use of
markWarning is wholly non-standard.
That’s precisely what I do (see my second screenshot above). The text file is then read back in to a second HTML file and presented in the browser with the text report inserted into an HTML
But like I said, that’s non-standard use of regular Katalon APIs. Warnings, as you can see, are benign. Being yellow, they stand out from the general noise of loginfo messages. I keep my log viewer like this:
I only depress “Info” when I’m investigating an issue more closely.
In answer to the question, “What if you get a real warning? Aren’t yours obscuring real warnings?”…
All apart from “This test passed”, they are indented by a half-dozen spaces. Regular warnings are not, so no, I don’t have that problem. Regular warnings sit back hard left on the line(s).
That’s precisely why I work this way. I’m in control and I want access to fails first and quickly. For working tests, all the rest of the info is just noise.
I can’t hand-on-heart recommend you work the way I do. I’m a relatively competent programmer and generally able to fix issues unaided. The last thing I would want is for someone else to try to copy my strategies and expect similar outcomes. That said…
If you’re comfortable writing warnings/messages/reports to a text file, go for it. I, along with many other knowledgeable programmers, am usually around if you get stuck.