Contributions
SessionCreator - improve password security
From its description, we believe SessionCreator could solve several of the problems we've encountered by letting us run a truly headless session, but password security is preventing us from being able to use it. The user account(s) running our tests have access to highly-regulated data and we simply cannot pass the authentication details it in the command line or store it in plain text in a file. Please add support for encrypted passwords, re-using an existing session based on a key of some kind, or some other method so we do not have to have passwords visible in plain text.2.3KViews1like7CommentsRe: Running TE with a list of tests
What's the organization of your tests? Different project suites? One suite with multiple projects? One project with multiple test items? We have a setup where the test itself determines what needs to be tested based on different criteria. So from the command line, we send in things like an environment, client name, etc., and whether we're running an entire project suite, or a single project. Then within each project, the test items determine whether they need to be executed based on the command line parameters and what is found on the screen. Kicking off tests in an automated way, and knowing what tests to run has been a negative for TestComplete for some time. We've figured out workarounds, but it'd be nice if more was supported out of the box.1KViews0likes0CommentsRe: determine whether testexecute is running or testexecute
For the paramstr option, it's my understanding that builtin.paramcount is 0 unless it's being executed via command line. So if you execute tests manually and via command line, that code would only work when run via command line. That's how I'm determining whether the run is an automated run vs. a manually executed run. getcurrentprocessid is a a better way than my proposal to check for the process, I wasn't aware of this method. Thanks!1.8KViews0likes1CommentRe: Internet Explorer is becoming non-responsive
This is definitely a thing that I've been fighting for a while now. There's some kind of memory leak in IE that doesn't occur when running the same test in Firefox. Luckily, we've been able to just run in FF instead of IE. I have run into a situation where FF memory skyrockets (over 2gb virtual memory consumed by the process), but that seems to be tied to a specific sequence in our app.2.1KViews0likes1CommentProvide Evaluation Dialog functionality outside of a running test
I frequently find myself having to create temporary subroutines just so I can test out some string parsing or date formatting or other syntax. The Evaluation Dialog allows for some of that, but it's only available during a test run. It would be great if we could have that functionality outside of a run. I don't need the overhead of a run (log file) just to see if I got my syntax/commands right for my date formatting (for example). Give me a text area (not just text box) where so I canrun some free-form code and get a result and I would be a happy camper.703Views1like0CommentsRe: Filter out events from the log
I feel the same way. I found a workaround that seems to work, although it isn't ideal. Assuming the events will almost always have Additional Text populated, Iuse that to identify the system-generated log items. So I added an event handler which I applied to Events, Messages, and Warnings. When I want to manually log one of these items, I'll either not supply Additional Text, or will prefix itwith a ^ (which I check for). I've been using this approach for about a year and haven't found any instances wheresomething is getting excluded that shouldn't, and everything Ido want excluded has been. function GeneralEvents_SuppressSystemLogging(Sender, LogParams) if len(logparams.additionaltext) > 0 then if aqstring.find(LogParams.additionaltext ,"^", 0, false) = -1 then logparams.locked = true GeneralEvents_SuppressSystemLogging = true else logparams.locked = false logparams.additionaltext = aqstring.replace(logparams.additionaltext, "^", "", false) GeneralEvents_SuppressSystemLogging = false end if else logparams.locked = false GeneralEvents_SuppressSystemLogging = false end if end function3.7KViews0likes0Comments