Forum Discussion
There are no prizes for using the fewest words possible to ask your question. ;) The more information you give us, the easier it will be to help you.
Are you looking for setup instructions or training or have you already started a test?
What have you tried?
What happened when you did that?
What did you expect to happen instead?
We were using test complete to test our web application before .We changed our application to RWD(Responsive Web design) site.
When i tried using the same script i was getting error on Sys.Browser().Page("*") as a result i was not able to find element on the page.
That time i realize it might happened because of RWD change and may be it will need any new add in to test RWD sites.
Please advice.
Hi,
Responsive web design is just a technology that tries to determine what client requests for data (desktop or mobile client, from Windows or Android or Win Mobile or iOS platform, etc.) and return the most appropriate content. The client (browser) receives the same HTML regardless of what technology is used on the web server. As TestComplete works with the client only, no additional plug-in is required.
I would recommend a nice http://blog.falafel.com/31-days-testcomplete-mobile/ blog by Falafel, SmartBear's partner and also their 'Testing Mobile Applications In TestComplete' e-book (testing-mobile-applications-in-testComplete.pdf) that should be available on their site as well.
Thank you so much .
I was unable to locate a copy of "testing-mobile-applications-in-testComplete.pdf" on Falafel and I've searched the web. Does anyone have a copy or perhaps provide a URL to a copy?
That URL works but I got a security flag from the browser when I went there. Perhaps your firewall is blocking you?
I don't know if there is a SPECIFIC add-in/plug-in for RWD... however, if the application under test has changed, then, yes, you will need to do some rework... page titles can change, object recognition criteria will change, etc.
Technically speaking, the line of code you posted should be able to find any page open in any browser. However, it is ANY page on ANY browser so, if you have multiple pages open, multiple browsers, etc., the result could be ambiguous as to WHICH page is returned. Try being more specific with regards to the object identification to make sure that you are targetting the correct page for your tests.I am using this line of code (Sys.Browser().Page("*")) to identify the current page name followed by the element name in order to identify the element on the navigated Page but this line of code is not giving me any result .
As this is very basic function and it is regardless to any application,i am more concern about it.
Is there any specif change in code i need to do as we have RWD now??
That line of code, as you mentioned, IS very basic. So, it should work.
Could you post the code as you are using it in your test? It may be helpful to see how you are using it in context. Perhaps a sample function or subroutine that shows how you are using it and then a screenshot or text output of any error messages you are getting.For example, I tried the following in JavaScript:
function TestSomething() { var page; page = Sys.Browser().Page('*'); Log.Message(page.Name); }and it gave me the following output.
