• Open
• Click and Wait
• Open Window
• Refresh
• Refresh and Wait
• Submit
• Submit and Wait
• Go Back
• Go Back and Wait

The new commands do exactly the same as the above Selenium commands, but don’t do an automatic screenshot. They are

• Open – No Screenshot
• Click and Wait – No Screenshot
• Open Window – No Screenshot
• Refresh – No Screenshot
• Refresh and Wait – No Screenshot
• Submit – No Screenshot
• Submit and Wait – No Screenshot
• Go Back – No Screenshot
• Go Back and Wait – No Screenshot

The new commands were added into the 1.9.0 release of the agent software. More details of the commands can be found in the support area of the customer portal – http://portal.cloudtesting.com/.

For more details of the Functional and Cross Browser testing service, please see our website at http://www.cloudtesting.com/.

You can also view it at selenium.cloudtesting.com/ and of course it available from seleniumhq.org

Once you have clicked on the ‘Test’ button, the following dialog appears:

If you are happy with the default browser for this project – in this case Internet Explorer 7, all you have to do is click ‘Run Test’.

If you would like to choose the browser to use, you can choose from the drop down list:

If you are running a Private Cloud Testing Agent (which allows you to test websites and applications inside your firewall), you will be presented with the browsers available on that, otherwise you will have access to all those supported by Cloud Testing:

Internet Explorer ( 6, 7 & 8 )

Firefox ( 2, 3 & 3.5)

Safari (3.2 & 4.0)

Opera (9.6 & 10.0)

Google Chrome (2.0 & 3.0)

]]> http://www.cloudtesting.com/blog/2009/12/01/selecting-which-browser-to-use-for-selenium-test-in-cloud-testing/feed/ 0 http://www.cloudtesting.com/blog/2009/10/31/firefox-3-6-beta-1-is-now-available-for-download/ http://www.cloudtesting.com/blog/2009/10/31/firefox-3-6-beta-1-is-now-available-for-download/#comments Sat, 31 Oct 2009 20:41:50 +0000 cloudtesting http://blog.cloudtesting.com/?p=874

The following posting on the Mozilla developer news (https://developer.mozilla.org/devnews/index.php/2009/10/30/firefox-3-6-beta-1-is-now-available-for-download/) announces 3.6 beta 1 of Firefox:

The Mozilla community is proud to release Firefox 3.6 Beta 1 for download. This beta version of the next version of Firefox is built on the Gecko 1.9.2 web rendering engine, containing many improvements for web developers, Add-on developers, and users. The Mozilla community appreciates your feedback and assistance in testing this preview of the next version of Firefox. Your beta software will update itself periodically, and eventually will be updated to the final release itself.

This first revision of the Beta of Firefox 3.6 / Gecko 1.9.2 introduces several new features:

• Users can now change their browser’s appearance with a single click, with built in support for Personas.
• Firefox 3.6 will alert users about out of date plugins to keep them safe.
• Open, native video can now be displayed full screen, and supports poster frames.
• Support for the WOFF font format.
• Improved JavaScript performance, overall browser responsiveness and startup time.
• Support for new CSS, DOM and HTML5 web technologies.

Web developers and Add-on developers should read more detail about the many new features in Firefox 3.6 for developers on the Mozilla Developer Center. For the full list of changes since the alpha release, see this list (it’s big).

Please use the following links to download Firefox 3.6 Beta, or visit the beta download page:

• Windows: Firefox 3.6 Beta 1 Setup.exe
• Mac OS X: Firefox 3.6 Beta 1.dmg
• Linux: firefox-3.6b1.tar.bz2

At this time most Add-ons have not yet been upgraded by their authors to be compatible with Firefox 3.6 Beta. If you wish to help test your Add-ons, please also download and install the Add-on Compatibility Reporter – your favorite Add-on author will appreciate it!

The release can be downloaded from http://www.mozilla.com/en-US/firefox/all-beta.html

Cloud Testing has added support for 3.6 Beta to it’s Functional and Cross Browser testing service, which allows users to upload and run their Selenium IDE scripts, capturing screen-shots, HTML, components and timings. Tests can be initiated via an API or via the web portal.

See the Cloud Testing website at http://www.cloudtesting.com/ for more details.

Subscribers can access the service at http://portal.cloudtesting.com/

Cloud Testing has released a updated version of it’s Portal (http://portal.cloudtesting.com/) which now gives customers access to an API (Application Programming Interface). This will give users the ability to initiate tests on the Cloud Testing agents, as well as view the status of projects, scripts and results of individual tests in and XML format.

Cloud Testing allows users to run scripts captured with Selenium IDE in a selection of browsers, with full screen-shots and diagnostics recorded and stored for analysis. For full details of all the features, see http://www.cloudtesting.com/serviceFeaturesFunctional.php

You can choose which view of the results to use by selecting from the links at the top right of the page.

The views are:

Overview View

This allows you to see a quick overview of all the steps in the script.

Clicking on the [+] next to a step expands the view so you can see the screenshot that was captured.

You can also click on the icons to view the full size screen-shot, HTML or full components list.

Thumbnails View

This view allows you to see all screen-shots from the script on a single page.

Details View

This is the classic view, and allows you to see all details on one page.

You can also click on the icons to view the full size screen-shot, HTML or full components list.

Running Selenium Scripts

The Cloud Testing service allows you to upload and run scripts recorded in Selenium IDE, in a number of browsers, for either Functional or Cross Browser Testing. For full details see the website at www.cloudtesting.com

The syntax is:

highlight(locator)

Arguments:

• locator – an element locator

Briefly changes the backgroundColor of the specified element yellow. Useful for debugging.

To use this feature within Cloud Testing, just choose the Highlight command, and enter the element or link name e.g. ‘link=Click Me’ for the first argument.

To enable you to view the highlighted area, you will need to add a Capture Screenshot command as the next step in the script, as the highlighting is reset and removed on any page refreshes or reloads.

The area corresponding to the element is highlighted in yellow as can be seen in the following view:

The following shows how you would highlight a text box on the screen.

and a larger view of the highlighted element:

For more information on the Cloud Testing service and features, please visit the Cloud Testing website at www.cloudtesting.com

Create Cookie

You can add cookies by using the ‘Create Cookie’ command.

The first argument is the name=value, e.g.

PHPSessionID=1213121

The second argument contain options for the cookie. Currenly ‘path’ and ‘max_age’ are supported.

The format is:

“path=/directory/, max_age=3600″

Create Cookie example

For example:

Delete Cookie

Cookies can also be deleted using the ‘Delete Cookie’ command. This take the cookie name as the first argument and the path as the second.

Delete Cookie example.

Full Example

In the following example, we visit a page, from which we get some cookies set by the server, we then add two cookies of our own, before deleting one of them.

Script with cookie create / delete

When we run the test, we get the following results:

Results of a test run

You are always able to view the cookies on any step that has interaction with the web server. After we have visited the page at step 1, we have the following cookies set:

Original cookies - set by server

After we set our own cookies at step 3 and 4 (CT and CT2), the next server interaction results in us having the following cookies set:

After manually added cookies

Note that the original cookies are still set, any new ones are just added.

In step 7 we delete one of the cookies we added (CT), we are left with the original ones from the server plus CT2:

After deleting the manual cookie CT

For full details of the services and features available from Cloud testing see www.cloudtesting.com

When you access the server manually you get one of the pop-up dialogs, depending on which browser you are using.

HTTP Authentication pop-up in Chrome

HTTP Authentication pop-up in Safari

HTTP Authentication pop-up in Opera

HTTP Authentication pop-up in Internet Explorer

HTTP Authentication pop-up in Firefox

If you fail to get the username and password correct after a number of retries (usually three), you will get a 401 Unauthorised HTTP result code from the server.

HTTP result code 401 - Unauthorized

So how do we get round this in Selenium? As we have mentioned in our articles, Selenium does not start processing until the onLoad() event has fired. Since no content has yet been delivered by the web server to the browser, this hasn’t yet happened, so we’re stuck.

Fortunately, there is a workaround. In RFC 1738, which covers URLs (Uniform Resource Locators), we are able to use a username and password in the URL. The following quote from the RFC explains how a URL is constructed:

; URL schemeparts for ip based protocols:

ip-schemepart  = "//" login [ "/" urlpath ]

login          = [ user [ ":" password ] "@" ] hostport
hostport       = host [ ":" port ]
host           = hostname | hostnumber
hostname       = *[ domainlabel "." ] toplabel
domainlabel    = alphadigit | alphadigit *[ alphadigit | "-" ] alphadigit
toplabel       = alpha | alpha *[ alphadigit | "-" ] alphadigit
alphadigit     = alpha | digit
hostnumber     = digits "." digits "." digits "." digits
port           = digits
user           = *[ uchar | ";" | "?" | "&" | "=" ]
password       = *[ uchar | ";" | "?" | "&" | "=" ]
urlpath        = *xchar    ; depends on protocol see section 3.1

; HTTP

httpurl        = "http://" hostport [ "/" hpath [ "?" search ]]
hpath          = hsegment *[ "/" hsegment ]
hsegment       = *[ uchar | ";" | ":" | "@" | "&" | "=" ]
search         = *[ uchar | ";" | ":" | "@" | "&" | "=" ]

Or as a simplified version, your URL needs to look like:

http://username:password@www.mydomain.com/secretarea/

Note that this won’t work on Internet Explorer, since Microsoft has disabled usernames/passwords in URLs as a security measure. If you want to get round this on an installation you have access to, you can add that functionality back in by modifying your registry, as described in the Microsoft Knowledge Base article http://support.microsoft.com/kb/834489.

How to disable the new default behavior for handling user information in HTTP or HTTPS URLs

// To disable the new default behavior in Windows Explorer and Internet Explorer, create iexplore.exe and explorer.exe DWORD values in one of the following registry keys and set their value data to 0.

• For all users of the program, set the value in the following registry key:
  HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE
• For the current user of the program only, set the value in the following registry key:
  HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_HTTP_USERNAME_PASSWORD_DISABLE

If you use Selenium RC (Remote Control), this is done automatically, as of version 0.9.2. As Cloud Testing is built upon Selenium RC, this is taken care of for you already.

For full details of the services and features available from Cloud testing see www.cloudtesting.com

Thanks to everyone for their positive feedback on our HowTo articles so far http://blog.cloudtesting.com/howtos/. We have a number of ideas of future articles we’re going to cover, but would be interested in finding out what you want to read about.

Articles we have in the pipeline will cover:

• Working with pop-up windows using Selenium and Cloud Testing – advanced
• Checking dynamic text or content using Selenium and Cloud Testing
• Data Driven Testing using Selenium and Cloud Testing
• Checking for XSS (Cross Site Scripting) using Selenium and Cloud Testing
• Cross Browser Testing – strategies using Selenium and Cloud Testing
• Detecting differences by comparing screenshot images using Selenium and Cloud Testing
• Capturing component information and headers using Selenium and Cloud Testing
• Analysing your page content and speed using Selenium and Cloud Testing

If you have any other suggestions, please leave a reply, or contact us.