I am working on a application which includes a developer express Datagrid version 12.2.7 . i have checked the supported list of controls from here :
visit http://support.smartbear.com/viewarticle/55638/
according to which the version which i have is technically not supported ? does that mean i cannot use testcomplete for that grid ? or do i have to upgrade the version base in my application too?
I think that this means that SmartBear did not test this functionality with this specific version of the controls. Most probably, TestComplete should work without any problems with it.
Related
I'm using sap gui in macbook os x. Whenever I execute the web dynpro programs, the browser will be opened and is keep on loading and it never ends. How can I fix this issue?
Though your Safari version seems actual, I assume your MacOS version is not supported by SAP, as PAM lists only versions from 10.11.
SAP issues PAM (Product Availability Matrix) sheets where you can match your Browser, Platform and Product versions and check for inconsistencies. Netweaver 7.4 PAM can be found here.
Probably, your MacOS version is too old for SAP and you should try to update. However, personally I feel that problem lies elsewhere and you should ask for help of experienced BASIS. Maybe your WDA uses certain feature that is not supported by Safari or WDA in general.
Additionally you can check:
Note 1634749 concerning Safari support for Web Dynpro ABAP (version for non-S-users).
Note 1098009 for general Web Dynpro ABAP browser limitations
Browser supporting page from SAP.
Please suggest if there is any way to automate the testing of Javafx application using UFT 12.02 as UFT is unable to identify the objects in JavaFx application.
Thanks in advance.
After a quick Google search, you would find out that UFT has no direct support for JavaFX applications.
This link talks about it:
https://community.hpe.com/t5/Unified-Functional-Testing/QTP-not-recognizing-JavaFX-controls/td-p/5793877
A brief summary on the answers:
QTP does not have any separate add-in specifically for those controls,
QTP has only the standard Java add-in that would work if the mentioned
controls are Java standard controls and if they belongs to the
standard Java Swing classes or Java AWT clases, only standard no any
kind of customized nor third party control. Otherwise, the recognition
will be basic because QTP will not support the controls.
You can find more information about the technologies that support the
Java add-in in the next link at page 4:
HP QuickTest Professional 11.00 Product Availability Matrix
http://support.openview.hp.com/selfsolve/document/KM1210389
Actually we have an Enhancement Request to evaluate the prosiblitiy to
bring support to JavaFX objects:
Support for JavaFX 2.0.2.
https://support.openview.hp.com/selfsolve/document/FID/DOCUMENTUM_QCCR1J26625
For the moment as a workaround we recomend work with these kind of
controls as third-party controls.
How to work with unsupported or third-party controls
http://support.openview.hp.com/selfsolve/document/KM186906
I don't have further knowledge about it as I've never worked with JavaFX before, but I belive here you will find enough content to help you out
Please check out UFT 14.01, it is supported natively now.
UFT now supports testing applications built with JavaFX, natively using the Java Add-in.
Prior to 14.01, JavaFX was supported by Microsoft UI Automation for
purely JavaFX widgets.
You can find the documentation here: https://admhelp.microfocus.com/uft/en/latest/UFT_Help/Content/Landing_Pages/Whats_New_Landing_Page.htm#hp-minitoc-item-2
I am using a C sharp .NET application and Testcomplete is not recognising the combo boxes using the object Spy. and since I cannot map it , the object spy doesn't not give me any methods related to combo boxes like e.g.. ClickItem function.
please give an workable solution or an alternative to access the items in the combo boxes .
It looks like TestComplete doesn't recognize your app correctly.
Check the version of TestComplete and the version of .NET Framework installed on your computer (and the one used to build your app). TestComplete may not support the .NET Framework version you use. For example, if you are using TestComplete 9.31, it works with .NET Framework 4.5 and earlier. If .NET Framework 4.5.1 is used in your app, you need to use TestComplete 10.
Microsoft's AntiXSS library has been broken for 6 months and it looks abandoned (that may or may not officially be the case). Due to a security issue with previous versions, it is not safe to rollback to an earlier release. Are there any good actively developed alternatives for AntiXSS and web security in general when working with the Microsoft (specifically MVC) stack?
There's a new xss sanitizer shipping with the June 2012 release of the ajax control toolkit. The toolkit was originally using the microsoft anti xss library as well, so they experienced the same problems. The new sanitizer is based off the HtmlAgilityPack
See http://stephenwalther.com/archive/2012/06/25/announcing-the-june-2012-release-of-the-ajax-control-toolkit.aspx
I have the same issue and I've been looking high and low for a solution but haven't found anything else out there.
Basically, I think the only option moving forward is to use some flavour of WMD (like they do here on Stackoverflow)... send it back to the server as WMD markup then save it in the database as HTML and then convert it html when spitting it out on the page on the server.
This could be a good start: http://code.google.com/p/pagedown/
There is a unofficial port of WPL called AntiXSS.NetStandard that support AntiXSS in .NET Standard 2.0 (.NET Core 2.0+, .NET Framework 4.6.1).
I wanted to know what i shouldn't do in code that will prevent my C# app from running on mac.
In general you shouldn't use anything from the Microsoft.* namespaces, no PInvoke (DllImport in C#) and UI might be problematic as well.
Further information on Mono compatibility is contained in the Mono Guide Porting Winforms Applications. Existing applications can be checked for compatibility using the Migration Analyzer tool.
UPDATE: PInvoke actually works in Mono, but if you want to have it working cross-platform you must provide a native shared library with the same interface for each platform (i.e. Win API most likely will not work).
Mono's Application Portability guide is a good reference.
In addition to divo's recommendations, I would recommend the Mono Migration Analyzer (MoMA) tool: "The Mono Migration Analyzer (MoMA) tool helps you identify issues you may have when porting your .Net application to Mono"
Also, I would keep an eye on Miguel de Icaza's blog, and the Mono Project website.
In his presentation for the Boston.NET Users Group this month, he showed a preview of a Visual Studio plugin that launches your app on Mono using a VM! This lets you test compatibility during the development process.
I believe their goal was to release it at TechEd 2009, so look for an update over the next month or so.
You will, at the very least, want to try and avoid using Windows Forms, since that is just a paper-thin layer on top of the Windows native UI.
Mono emulates it somewhat with help from WINE, but I wouldn't trust that.
Mono did this a while ago but the effort was abandoned. See WinForms on Mono for more information. Thanks jpobst.
Try using GTK# or Qt# (although I'm not too sure the latter one actually exists) for cross platform support. You might also consider using Java with SWT or even Swing instead of C#, but that will probably not be an option you're willing to consider.
Using anything related to P/Invoke is probably also a bad idea, since that invokes native code which will probably not be portable (unless you write it yourself, then you can choose to make it portable).
I'm not sure if it is possible with mono, but WIN32 API calls will definitly not work ;)