Contributions
Re: Running Windows Batch Files
i had the same problem using the example from Allan (The system cannot find the file specified), and tried the suggested change from jsmunroe, which worked, but I’m relatively new to coding and don't understand why my original path in mypath didn't work, and why the one from jsmunroe did. Therefore, why does inserting additional "\"'s on either side of the path correct the problem? var obj = Sys.OleObject("WScript.Shell"); var mypath = "C:\\PixelPOS\\TestComplete\\Default INI and Policies\\XMLPolicies Reset.bat" obj.Run("\"" + mypath + "\"");6.1KViews0likes2Comments- 2KViews0likes1Comment
Re: is there anyway to NOT log a test?
LOL :manlol: yes, this is what I was trying to do initially, but, by your level of code example, I could now see why I wasn’t getting anywhere. :smileyfrustrated: This is way beyond my programing skill level at the moment, however, I’m currently taking a programming course, and I will decipher your example and should therefore be able to understand it in a very short while. (: Note: I do understand the For logic and structure, it’s the syntax (the ++’s and &&’s etc.) that I need to learn. I also don’t understand the ‘*’’s and the ",0" inside the parenthesise i.e. ('*' + processName + '*',0) Very much appreciated.2KViews0likes3CommentsRe: is there anyway to NOT log a test?
Hi, Marsha. My programing knowledge is very limitetd, and the examples in the article (see directly below) doesn't give me an example of how to apply it directly. function LockEvents() { // Disables posting events Log.LockEvents(); // No event messages are posted to the test log Log.Event("This message won't be posted to the test log."); // Enables posting events Log.UnlockEvents(); // Event messages are posted to the test log Log.Event("A test event message."); } Any chance you can show me an example applied to an actual case? Very basically, I'm trying to do the following: function terminate_authmanager() { LockEvents(Sys.Process("PixelAuthorizeManager").Terminate()); } where I don't want this logged. PS Been playing around, where i've tried breaking out the functions into seperate line statements, including putting the Log.LockEvents() statement before and after the process I don't want logged, but I'm still seeing this being logged. function Terminate_AuthManager() { Log.LockEvents(); Sys.Process("PixelAuthorizeManager").Terminate(); Log.LockEvents(); }2KViews0likes6CommentsRe: "If Object Exists" is still running child opeations when object DOES NOT exits
hi, Ryan. I had to play with the child indents and finally got it to work. I had to unindent the first Else Statement so that I does not become a child (this dosen't make sense), but this worked. So, I tried un-childing the second Else as well, and it didn't work. :/ I finally re-childed the second Else under the first one, and now the second one works as well. (go figure) (see below) Thanks again for your help. Awesome!1.8KViews0likes1CommentRe: "If Object Exists" is still running child opeations when object DOES NOT exits
Thank you for your help. I understand the concept, and I understand and know how to drill down to various properties with the Property Checkpoint, but just to let you know that my coding skills are limited. :smileyfrustrated: :smileylol: I therefore revised my keyword tests, but I’m still getting the same results, that is, the test continuers with the child operations, even though the IF…Then statement is not being met. I’ve tried two variations of as per your suggestion: Variation #1. Created a Property Check to check for the Visible property of the object I want, then used an If... Then statement set for last operation = True. This failed, and continued onto the child operation when the last operation came back False Variation #2 I got rid of the property check all together and configured the If…then statement to check the object’s property (Visible) directly, with the same result. In both variations, if the objects (my three different form scenario) are present, then the scripts work correctly and run when they should. It’s just when the object.visable are not visible that the script still tries to run the script.1.8KViews0likes2CommentsRe: "If Object Exists" is still running child opeations when object DOES NOT exits
you are right. :-D the object(s) Exist, but are not set to Visable. Therfore, how would you use If Object to check against a property? The Test Action itself does not allow you to drill down to the ojebect's properties. I've tried the follwing in the command line, but If Object does not understand what I'm trying to do: Aliases.PixelPointPOS.wndSystemObject.FormShape_InnerPanel.Panel.PixelButton.Visable Aliases.PixelPointPOS.wndSystemObject.FormShape_InnerPanel.Panel.PixelButton.Visable=true1.9KViews0likes4Comments