Key word testing and disabling logging on property checks
I have a bunch of drop and drag keyword setup scripts that I do not want to log test results as the Property/Region checkpoints looks for a status of where we are on the webpage and fails as it should - but it logs it in the test results - Is there a way to create a keyword test script that shuts logging on and off before actual test compares starts?
Solved! Go to Solution.
I guess a question in my mind is this: Why do you have property checkpoints in what amounts to a setup/utility routine? Just because it's called a "keyword test" doesn't mean it actually has to test anything. Checkpoints are just that - checkpoints. Activities that you add in order to validate whether or not the application undertest has met some sort of expected result.
Personally, while manipulating the Log.Enabled property of the logging object may be one solution, probably the more obvious one would to use some other method (if then, for example) for doing the necessary checks without logging a checkpoint result.
[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