aalikhalid
Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: TestComplete 'Jenkins Job' with parameters
Hi Tanya, I'm having trouble implementing step 3 and 4. "In the TestComplete Test build step, you can pass those parameters to TestComplete via ${ParameterName}" - Where are we supposed to specify the parameters, int eh 'additional command line arguments"? I am writing the values there but it's not working In TestComplete, you will need to modify your project accordingly to your parameters. - Do you mean 'project variables' should be the same, or the test items parameters should be of the same name? Tried both, did not work for me. Thanks a bunch.4.8KViews0likes0CommentsPass and receive parameters from Selenium / Java based tests
The current support for selenium as I understand is to just run items and get results. The problem there is, we don't get complete integration with any tests written on that platform except getting results of pass and fail. In my case I was writing API tests with RestAssured, I can perhaps trigger the tests, but cannot pass or receive back data from my tests. Our UI automation would help a lot if we could create some pre-req test data using API calls. For that my test data needs to go from within TestComplete and get a response string in case of any failure messages etc. This is a very crude description, all I'm trying to say there is just too much out there which complex automation systems need these days. It might not be possible to implement them all, would be great if we can have seamless integrations that would make things a lot more scalable.1.7KViews0likes1CommentRe: TestComplete upgrade for chrome v63
I did contact support, they helped out with the 'deactivation started' problem where the license would not deactivate, but did not mention a different flow for upgrading. I've done these updates around 10 times since we have been using TestComplete (since v10.3), and each time there is a new problem I come across. The key here is if during upgrade the install hits a problem whih it usually does with the Sentinel licensing tool, that turns into a long story. I find it safer to deactivate and then upgrade. Since I have to do at least 5 VMs, eventually I do ruin into problems with at least on VM. Another issue here I think is using a node lock on a VM, the licensing structure makes it really hard to upgrade in this configuration, for understandable reasons, but the user suffers too.1.7KViews0likes1CommentRe: TestComplete upgrade for chrome v63
So after doing the last upgrade, here are the steps when I followed did not run into a roadblock: Deactivate the license. If you have to go through manual deactivation, I don’t have a solution for that Important: Once deactivated, confirm the license has been deactivated on your SmartBear account’s license page. If the license is not deactivated and you uninstall, that’s going to take some time to rectify Restart the machine / VM (so the license manager service is not running) Uninstall TestComplete Upgrade Chrome in case it is not updated yet to latest version Restart the machine / VM Install the new TestComplete version Activate the license Run Chrome and make sure the TestComplete extension is enabled If not, go the Chrome patch page on SmartBear’s website and download the latest patch for TestComplete and Chrome version, install it and test again Again, this is not the way suggested by SmartBear's support, but by hit and trial this is what I have found to cause less problems.1.8KViews0likes3CommentsRe: TestComplete upgrade for chrome v63
Well, as per the general process we should not have to, but for some reason I have ran into problems when the license was not deactivated first. For instance, if the installation process gets jacked up somehow (which it does very easily since last two upgrades), you would have to deactivate the existing license first, which then becomes a huge problem. So I found it better off to deactivate it already Just In Case.1.8KViews0likes0CommentsTestComplete upgrade for chrome v63
After every few months due to Chrome updates we have to update TestComplete. Having a node lock license its a pain. I end up spending hours for each upgrade running into new issues every time no matter how carefully done.The process I use for new release: Deactivate license Uninstall TC (if version change instead o patch, e.g. 10.6 -> 12.1) Upgrade new version Activate license Some of the problems I run into: - License does not deactivate - - Have to do offline deactivation, - then offline deactivation does not work, - then when it does complete finally, it does not deactivate on my licence page. - Sentinel (the license manager) with TestComplete does uninstall correctly, restart the VM and do the whole process again - Then sometime we run into problems with regenerating licenses - Then it does not activate, have to do offline activation sometimes. We have 5 VMs and I start getting nightmares when I have to upgrade.1.8KViews0likes6CommentsRe: New Chrome window page object not recognizing.
Thank you for the reply Alex, your reply turned on a few light bulbs in my head. Some background: We don't use name mapping, all the objects are searched dynamically. We find the page object, then the screen object (down a few hierarchies in the application's DOM structure) then object.find(); to locate the actual object. About using additional parameters, how to use additional parameters when finding the page object, I could not find any example of that, oh we can use Sys.Browser(Chrome).find(); instead of Sys.Browser(Chrome).page().. But then I couldn't find any properties differing between the two pages except the URL, I'll dig more to find something or perhaps a child object. I'll get back once I have tried these (plus the case sensitive property, on top of my head it should not affect the project, but you never know its a 250KLOC project!).1.1KViews0likes0CommentsNew Chrome window page object not recognizing.
When our application opens a new screen in a new browser window, TestComplete is not able to capture the new page object, keeps returning the old page object. Sys.Browser("Chrome").Page("http://v303m5qa/m5web/presentation/outerframe/M5Shell.aspX"); The existing page has the same URL except with a capital P in '/Presentation/', rest is the same. This used to work before but now it does not seem to work anymore. TestComplete v12.31, Chrome version - latest 60.0.81.2KViews0likes2Comments