steve4king
Occasional Contributor
Joined 15 years ago
User Profile
User Widgets
Contributions
Stop displaying log every time I execute a test
I dunno about the rest of you, but when I'm creating test cases, I execute them several times, oftentimes just making minor tweaks. Every time I do this it displays the log.. I don't care about the log at this point and it takes a good 5-10 seconds for me to get back to my test page. (or more if I have several tabs going) Is it possible to disable logging while building tests, or at the very least stop it from switching from my current test window to the log display? Thanks, -Stephen9.2KViews0likes1CommentRe: Parameters with a default value return "undefined"
Thanks David. Paul replied to a support request this morning about this and was able to replicate. I'll post his note below so that others can benefit: Hello Stephen, I have reproduced the problem. When running a test with an optional parameter with a specified default value, the test run results will be different depending on the way you are running the test: - when running the test from within the Project Explorer, the test is run with an undefined parameter value; - when running the test from within the Keyword Test editor, from script or as a test item, the test is run with the specified default value. I have registered this issue in our database. Currently, to avoid the problem, do not run keyword tests from within the Project Explorer. You can find possible ways to run a keyword test in the "Running Keyword Tests" ( http://www.automatedqa.com/support/viewarticle/12564/ ) help topic. Best regards, Paul670Views0likes0CommentsParameters with a default value return "undefined"
Running version 8.0.290.7 on Windows XP 32bit I've created several interdependent keyword tests. For example. I have one to test the time-clock in our application. My timeclocktest is very simple and just has two parameters: the login username and password that I want to test. It logs in -> clocks in -> logs out, then logs in -> clocks out -> logs out. All using the parameter defaults I assign prior to running the test. However, about 30% of the time.. the parameters have been ignoring their defaults. Example: I launch timeclocktest with default parameters of User: "Steve" and Pass: "pword" The test first checks to see whether that user exists, and if not, it creates it with full permissions. 30% of the time however, it's checking to see whether user "" exists, then tries creating a new user with user: "" and password: "". When I originally created these tests, this did not happen. I just had to change the highest level parameter and every associated test utilized that. I don't know what has changed, but any help would be appreciated. Thanks, -Stephen9.5KViews0likes2CommentsStop on Window Recognition error - never stops..
I know the documentation says, "Not counting Auto-Wait Timeout cases.." But everything that calls a window has an auto-wait timeout.. so how can I force this to trigger? I'm trying to handle unexpected (not technically modal) windows.. and 90% of the time, I don't want my test to continue running down the list if one window doesn't exist. It looks like I'm going to have to add annoying little loops at every user interaction to look for non-modal error messages that prevent the test from progressing. Main question I guess.. How can I get stop on window recognition error to fire? (How do I disable auto-wait timeout for certain operations so that it will fire?) Thanks! -Stephen10KViews0likes1CommentRe: Bug/Error clicking a cell/field in a Delphi grid
Hmm.. so I'm not going to be able to apply this testing on a production build of our software?(We don't want to leave debug information in a shipped product) Seems odd that I can retrieve the row-count from the control, but I cannot perform a mouse-click, focus, or get the grid1.wValue(x,y) for a particular part of the control. I ended up using keystrokes in a 'for loop' tied to the row count to select the control. Slower than I'd like but it works for 95% of the cases I need. Thanks -Stephen769Views0likes0CommentsBug/Error clicking a cell/field in a Delphi grid
I've got a grid which may have one record and it may have three thousand. I need to be able to select the last value from the 7th column. Both of these work fine and I'm able to pull the row/column count. Aliases["ofcstar"]["TimeClock"]["Grid1"]["RowCount"] Aliases["ofcstar"]["TimeClock"]["Grid1"]["ColCount"] However, I'm unable to actually select the cell. (To simplify I hardcoded the numbers, so my code snippet is exactly this: Aliases["ofcstar"]["TimeClock"]["Grid1"]["ClickCell"](26,6) When I execute I see this Error: "An Error has Occurred" Possible reasons: 1. The application stopped responding. 2. The application was compiled incorrectly (see the Open Applications topic in the help system). 3. An error occurred in TestComplete. Technical information: 97 0x80020006 (Unknown name.) FRowCount. Aliases["ofcstar"]["TimeClock"]["Grid1"] (Sys["Process"]("ofcstar")["VCLObject"]("TimeClock")["VCLObject"]("Grid1")) (on a different note.. can I set the default to period(.) rather than brackets/quotes? So much harder to read after it converts it that way)12KViews0likes3Comments