My test is BROKEN! NOTHING WORKS! HELP ME!
Relax. We get it. We really do. There are some pretty smart and clever people on this forum, but you must realize, they are not magicians or wizards or gods. They cannot see your code, they can’t see your errors and they don’t even know what your AUT is meant to do even though it might seem perfectly obvious to you.
So please relax and follow the advice below, before you start writing your post. The advice below will tell you the exact information we need from you. If you take the time needed to do this properly, it will save your time, as well as ours, and…
Help us to help you.
1. We need to see what you are dealing with
Post a screenshot of the page that is failing in your first request for help.
2. We need to see the underlying HTML of the page
Post the relevant section of HTML in your first request for help.
Example HTML screenshot:
See section 8 below to learn how to do capture the live HTML from your browser.
3. We need to see the Test Case code you are having difficulties with
Post the relevant lines of Text Case code in your first request for help.
Example Test Case code:
4. We need to see ALL errors from the console
If you don’t know how to interpret error messages, please copy-paste them, don’t retype a brief version, paste the WHOLE ERROR MESSAGE.
Usually, there is a Caused by statement something like this:
Example Exception Text:
Notice the error above begins with “Caused by”. This information usually leads to a solution. For example, you could try pasting any key terms in the Katalon forum search bar. Perhaps someone else has had the same issue and the solution to your issue is just a few clicks away.
.
Sometimes, though rarely, the problem lies within Katalon itself. In those rare cases, the Katalon runtime log can prove very helpful (@ThanhTo). You can access the runtime log via the menu:
* If your runtime log is huge, please zip it before posting it!
5. Integration issues
If you are having integration issues, (Jenkins et al), please attach any relevant logs. They will help enormously.
6. Tell us what you have tried to fix it
Tell us everything you tried to fix it yourself.
7. Mention ANYTHING that you think might help
There’s no such thing as too much information.
8. Learn to Use DevTools.
Finally, many of the points above rely on YOU understanding how to use the Browser Developer Tools (aka DevTools).
[Learning DevTools] is absolutely must-have knowledge for anyone trying to learn test automation. (@Brandon_Hein)
You can follow THIS GUIDE to help you learn how to use DevTools.
And finally, a piece of writing on Getting Answers, for those of you who are interested.
[Updated April 3, 2023] by @albert.vu
In an effort to reduce the number of duplicated questions and poorly-formatted topics on our forum, this topic now includes a Policy section at the end, where you are required to click on “I have read, understood, and acknowledged this topic” to signal that you would follow Russ’ guide every time you create a topic.
