The message you described is the description that goes along with "Events" in the test log. Events such as "Click" or "Keys" or other such things coded specifically to log that information as you described it as a debug description of what is happening. Events can fill up a test log with a lot of stuff which is why I usually start my automation out with a Log.LockEvents() call to shut down the event logging.
I would actually recommend that for you. Then, for those actions that you want to output for your user manual, you can write your own "Log.Message" calls in order to give the custom text you want.
Robert Martin
[Hall of Fame]Please consider giving a Kudo if I write good stuff
----
Why automate? I do automated testing because there's only so much a human being can do and remain healthy. Sleep is a requirement. So, while people sleep, automation that I create does what I've described above in order to make sure that nothing gets past the final defense of the testing group.
I love good food, good books, good friends, and good fun.
Mysterious Gremlin Master
Vegas Thrill Rider
Extensions available
