Contributions
Re: WaitWinFormsObject no longer working with wildcards?
I'm running them in 14.7. I happened upon a page that indicates TestComplete now only supports specific versions of DevExpress controls and the version these applications use is 18.2.6, which falls between the 18.1.3 and 19.something versions that the page says will work with TC.676Views0likes1CommentWaitWinFormsObject no longer working with wildcards?
I have a set of tests that use WaitWinFormsObject quite often to wait for specific forms to appear. All the forms are DevExpress XtraForm subclasses. Some of them use wildcards for the in the type, caption, or both. All the ones using wildcards have stopped working. Is there a setting somewhere now that toggles wildcards on/off? Or has something else changed? These tests were migrated from v12 and used to work without any problems, so perhaps there's something that needs to be changed in the calls to WaitWinFormsObject that isn't stated in the documentation for the method? Or is it a problem that was introduced by DevExpress (the applications used to use DevExpress 16.x, but are currently on 18.x. They don't often see a lot of work on them, so they've not yet been upgraded to v20).694Views0likes3CommentsRe: Add Support for Code Completion in Other Code Editors
I don't use TC for editing at all. It's not designed to be used for editing scripts. One does have to be aware of limitations - TC maintains only a logical structure, so having a folder hierarchy built in an external editor fails when trying to run the scripts in TC, at least in Python.2.7KViews0likes0CommentsRe: Python - Parameters in ADO queries
Hi Unfortunately the ADOCommand.Parameters doesn't have either a ParseSql or ParamByName. It turns out that SQLOLEDB doesn't support those, only Jet does. Also, none appear to support query parameters for anything other than select statements. Thanks for trying. Craig1.8KViews0likes2CommentsRe: Refresh files
I've already put in the feature request, but I fully expect that to come to nothing. If a feature like that isn't there, considering other basic features that are missing, I have no doubt that there's no intention of ever putting it in. And I can't bring myself to use the TC editor because it's just not designed for editing code. Or anything, really. Thanks for your time.340Views0likes0CommentsRe: Refresh files
Yes, but that's more of a waste of time than having to make an unnecessary change and save the file again so that TestComplete asks if I want to refresh them. Less than making unnecessary commits to source control and pulls from source control (though that has the virtue of probably taking enough time to let the current test execution complete even though it does pollute source control until I take the time to squash all the commits). TestComplete already monitors the files when tests are not running. What I find suprising is that it doesn't check when a test run completes, or even while a test run is in progress. Either of those would allow it to offer a refresh after test execution completes without additional steps by the user. It won't matter much when changes become rarer, but right now the changes are happening quickly as tests are created, updated and fixed. The frustration of not having general auto refresh or a way of forcing a refresh within TestComplete (since a command in TestComplete would presumably allow me to set up a shortcut or use an existing one) adds up quickly when there are lots of changes being made.1.5KViews0likes2CommentsRe: Refresh files
"Either way... TestComplete cannot use new script code while the automation is running. It's not a dynamic project like a web page that updating script and hitting "refresh" will cause new code to be used right away." And again, that's not what I'm trying to do at all.1.5KViews0likes4CommentsRe: Refresh files
Thanks Lino. I can see that working for your situation. Unfortunately I'm in the process of creating and updating tests, including moving from v12.6 to v14. If I run a test and it fails, I look at what might be wrong. If I can see what's wrong I go and fix it. Or, if a change I made fixes a problem, I go and fix anywhere else I know that problem exists. In the meantime I let the tests carry on running - there's cleanup to do so that the tests can be run again, such as closing the app under test, possibly removing a database, whatever. So now I've made changes and I want to test again. But because I made changes while the tests were running I have to change at least one file again and save it again so that Test Complete recognises that a file has changed. Since I'm making a lot of changes as the tests are added or updated, this ends up adding up to a lot of extra time and frustration. So right now my process is Make a change Run the test applicable to the change If the test runs successfully, move on to the next change while any cleanup is run. Otherwise look for what's wrong and, if found, fix the problem. If all changes are finished before the cleanup is finished and the test run completes, change a file again and save it so that the files are refreshed in TC. Run the test again (or run the next test if the previous test was successful). Only once I have the tests running (or if I'm done for the day) will I commit them. Once the tests are all done, I'll switch to running them all, but at this point they're being developed, so I'm just running the parts of the project that are applicable. I'm used to development IDEs and general code editors which refresh files automatically when they're changed by other software whether they're in the middle of a debug session or not. So if I change a config file or pull code from a repository or otherwise change a source file, the IDE immediately refreshes the file. The code changes don't generally become part of the executing code unless a new debug session is started (or if edit and continue is enabled and the code stops at a break point). But they're always there without any intervention from me apart from possibly having to do what TestComplete requires when tests aren't running - accepting the file changes.1.5KViews0likes0CommentsRe: Refresh files
The company I work for has a TestComplete license, so that's what I work with. Also, I imagine that creating tests to run with TestExecute would be excruciatingly difficult since one would have to know how to create all the files required for the tests to run, not just the scripts. The license also isn't the only part that is ridiculous. I'm pointing out that every time I need to refresh files I have to do some unnecessary steps. His suggestion was that I get around doing those extra steps by doing many more and far more time consuming steps. In other words, that post wasn't an attempt to help since it was presenting an approach that is clearly far far worse. He has responded to other questions with actual help, so I assume that the post about using git wasn't intended to be helpful. If the best way to use TestComplete is to waste lots of time waiting around for tests to complete (and not, that's not because one has to run a full test suite or anything like that, but even having to wait over and over for parts of test suites that are being set up/modified/fixed adds up pretty quickly), then what you're really saying is that the best way to use TestComplete is to use some other tool instead. I can't see how there's anything unorthodox about using a working editor designed to for editing code rather than the TestComplete editor. TestComplete already monitors files for changes (so long as tests aren't running). That means that using external editors has at least been partly considered, so it's not possible that it's unorthodox.1.5KViews0likes2Comments