Not able to detect UI Controls on ASP.NET Application - ui-automation

I am working on a ASP.NET application. The framework which i am using for detecting UI Controls are TestStack.White and Windows Automation. Although the object is having enough properties like
Name , Controltype -> Hyperlink and Framework Id -> "Internet Explorer". But still not able to detect control with enough properties.
Do white is able to detect Controls on ASP.NET or Web Application?
Thanks in advance

Related

Possibility of implementing drag and drop out from a Chrome app

I am developing a Chrome application that currently resembles a File Manager in its UI. I would like for users to be able to drag and drop "files" both into and out of the app, for example, to and from their native file managers.
Does this seem impossible, therefore should I be looking for other user interface options?
I have looked into this question: Drag out files from browser using javascript but unfortunately it doesn't seem to work on ChromeOS, the platform I am developing for.

How do I test web pages opened in an Eclipse internal browser view.

We are developing an Eclipse plugin that opens web pages in a view using the Eclipse web browser (typically IE on Windows).
Are there any testing tools that support Eclipse (to drive the parts using Eclipse/RCP) and also able to drive the web browser views.
At a minimum I'd want to be able to get elements by ID or xpath, and to send click events to elements in the browser.
We know Quick Test Pro doesnt do this, and can't see anything that explicitly supports Eclipse web browser views.
You can check with QFS , we used this tool for SWT/JFace UI automation and this tool also supports web. You can to check if this supports your test case.

Sybase Unwired Platform Hybrid Web Container IPHONE BLACKBERRY

I am developing a application in Sybase Unwired Platform ,Hybrid Web Container. When I deploy it on Android it is working fine but when I deploy it on Iphone or blackberry I can see the menu items like back,next displayed on menubar and some on toolbar as it is in Iphone native application and the buttons on the screens are not working. I think its because of JQuery but is there any workaround to remove this menubar and toolbar and make it run properly.Thanks in advance.
I haven't tried it yet, but if you are in the last SUP version, it's supposed that you can have buttons on the screen to call SUP requests and operations without the need to add them as menuItems.
The problem with menu items is that they work different in each platform, and it's not recommended to use them anymore (even google said that), and it makes the HTML5 app less multi platform.
In my SUP apps, I hid the menuItem dynamically after the workflow initialization, and created a custom html button (using Custom.js) that calls the menuItem javascript function.

Optimise ASP.NET application IPhone and Android browsers for ASP.NET application

I have an ASP.NET (not MVC) application.
I would like to create a version that is optimised for browsers on the IPhone and on Android.
Some questions
Is it possible to detect IPhone/Android when the site is accessed
Are there any gotchas/tips for developing ASP.NET for these devices.
We're using a combination of .net webforms and jQuery mobile.
For our viewstate, it's been pretty well neutered already so only minor stuff is going down to the device.
Bear in mind that there are around 3 different mobile api's. Each of which has their own drawbacks. You might want to investigate each.
Also, we took the approach that the mobile site was a completely different website than our standard one. When the user comes in, we do some browser sniffing and push them to mobile if it matches with a link to move back to the full one if they want.
Webforms aren´t good for mobile, it generates big pages because viewstate. And you can´t control rendering (some more in .net4).
You can detect device using a db of capabilities like WURFL (I recommend 51degrees) o maybe using some like http://detectmobilebrowser.com/
I don´t know what kind of webapp but you could make a new app, maybe using MVC. Please look this resource.

iPhone web application developed using ASP.Net

We are developing an ASP.Net web application and need that application to work properly on iPhone
Are there any memory constraints for an ASP.Net web application to work properly on iPhone
are there any issues with usage of ASP.net controls like gridview/ tab view etc.
would there be any issues with 3rd party controls like Ajax RADSchduler from Telerik
any other other constraints for a web application to work on iPhone.
Thnx
Amit
If we are talking about a standard asp.net website, memory constraints aren't really the issue. Asp.net just generates (ugly) html with some javascript. Nothing really special about that. Memory in this setup is important server-side. Offcours asp.net tends to generate lots of bloat when viewstate is enabled (without it, too). And this IS an issue when it comes to bandwidth, especially for mobile applications.
When using the Asp.net Ajax Toolkit, it should work crossbrowser. Apple Safari version 2.0 or later versions are supported.
Checkout the docs for the 3rd party controls, which browsers are supported. If Safari is supported, it should work.
But i would suggest using asp.NET MVC instead of standard asp.net controls, because it allows full control over html and javascript. This will ensure minimum use of bandwith and maximum javascript performance. Or any other language/framework with full control like php/codeigniter or python/django. And maybe a javascript library like mootools, jquery or prototype.
I think having a real iPhone to test on would be most optimal.
As for integrating third-party components you should be able to ask the vendor about their support. These Telerisk and Infrastigistic components look great, but you need to ask yourself do you need that amount of power and options, if you follow the mantra of the iPhone and Apple in general you'll want to keep it as simple as possible.
One approach is to develop a different view for the iPhone, keeping the display basic and optimized to the dimensions of the screen and the touch system rather than cursor.
Since Safari is based on Webkit you can get some basic compatibility testing on your local PC.