krainevsky
Contributor
Joined 16 years ago
User Profile
User Widgets
Contributions
Default images format for exported log
Hi I wonder why is the default format for images in exported to html log is jpeg? I tried to find the option to stop converting, but I failed. Maybe someone knows how to stop converting *.png images to *.jpg. I've attached two logs with one image. So, the resulting size of images is different and it is not in favor of jpeg. It is about 20Kb in png and 40Kb in jpeg. Thanks in advance.10KViews0likes2CommentsTC hangs on evaluating aqFileSystem.GetFolderInfo("network path")
Hi, How to avoid TestComplete hang on evaluating aqFileSystem.GetFolderInfo with network path in param? It is very strange - it looks like TC is alive(refreshes gui), but I'm unable to stop evaluation. Maybe someone from support team knows the answer. Try to evaluate the following string for example to reproduce the problem: aqFileSystem.GetFolderInfo("\\\\builder\\builds"). TC 7.52. Thanks in advance.11KViews0likes1CommentTC 7.52, Firefox. Empty properties at Inspect window.
Hi everyone! I've found a problem when inspecting firefox's script objects - i'm unable to see object's properties, fields and methods. I've allready asked support team about it, but maybe someone from this forum knows the answer/workaround. 1. Open Firefox (3.5.9), navigate to http://www.sencha.com/deploy/dev/examples/desktop/desktop.html 2. Write the script below and place breakpoint at the line with Log.Message [JScript] var mgr = Sys.Process("Firefox").Page("http://www.sencha.com/deploy/dev/examples/desktop/desktop.html").document.Script.Ext.WindowMgr; /*breakpoint here*/Log.Message(mgr.zseed); 3. Execute the script and when it stops open Evaluation window 4. At the evaluation window try to inspect the mgr variable At the Inspect window I see empty tabs "Properties", "Fields" and "Methods". This shouldn't be so, because if you continue script execution you'll get some value at the log's message. The question is how to get properties, methods, etc visible at the evaluation window? Thanks in advance.14KViews0likes4CommentsRe: Chrome, Opera support
Hi Alexei, I think I've found the cause of your misunderstanding of our problems. The point is that I'm not going to swap Chrome's render engine for IE engine to make "TC support Chrome". I'm going to do the opposite: use Chrome's render engine inside IE. I see the following disadvantages of this approach: - Using this trick cause appearing bugs that can not be reproduced at the real Chrome. - Additional resources(time, people, money...) needed to make changes inside the core of the autotests(it depends) - No guarantees that this will work, cause no one tested this But this approach is not so bad cause: - This is the only way to test Chrome with TestComplete at the moment (except coord-testing). - You can use test results from this IE-Chrome integration (only if you keep in mind that this is not real Chrome). - If you succeed at the rewriting your tests you can save resources cause you still use automated testing and cause you still use one automation tool. Please, correct me if I'm wrong or miss something. ty.2.3KViews0likes0CommentsRe: Chrome, Opera support
Hi, You are absolutely right Alexei! There are no good reasons in the list you posted above for using non-native rendering engine. But if we add to your list some new thoughts like: - We use TC for autotests - TC doesn't support some popular browsers - We need to test under the browsers which are not supported by TC we'll see definetly different picture. I hope this help you to understand reasons for using non-native rendering engine.2.3KViews0likes0CommentsRe: Chrome, Opera support
I guess this will be interesting for some TC users and developers: 1. Go here: http://code.google.com/chrome/chromeframe/ ,download and install Google Chrome Frame. 2. Modify your test pages as it said here: http://www.chromium.org/developers/how-tos/chrome-frame-getting-started. In the simpliest case you have to add <meta http-equiv = "X-UA-Compatible" content = "chrome=1" > to the test page. 3. Run test complete, open project properties at "Open Applications -> MSAA". Add two classes to the list: "Chrome_WidgetWin_0" and "Chrome_RenderWidgetHostHWND" 4. Run Internet Explorer (I used IE8) and open your modified page. Results: Now your test page is rendered with chrome engine. Now you are able to see some object's from the page through MSAA (see attach).2.3KViews0likes0Comments