
Jan 31, 2012
WALTHAM, MA, January 31, 2012 - Telerik, the developer of Sitefinity, a web content management and collaboration platform announced today they have become a contributor and member of the Organization for the Advancement of Structured Information Standards (OASIS), a not-for-profit consortium that drives the development, convergence and adoption of open standards for the global information society.
Members from the Telerik Sitefinity product team will participate on the OASIS Web Experience Management Interoperability (WEMI) committee with full voting rights. This committee works to define a simple domain model for delivering aggregated content into a total Web Experience.
"Telerik’s participation in the creation of standards for web content management content aggregation is important to provide Sitefinity and our clients with better interoperability with other systems." shared Martin Kirov, EVP of Telerik’s Sitefinity, "This is an opportunity to exchange experience with other vendors in the area of customer experience management and work together in defining a common interoperability standard to facilitate the cross-platform exchange of customer experience management data."
"We welcome Telerik to OASIS and look forward to their contributions as work on WEMI progresses," said Laurent Liscia, executive director of OASIS. "Telerik’s support of OASIS underscores the company’s commitment to open standards and to delivering meaningful interoperability to its customers."
About OASIS
OASIS (Organization for the Advancement of Structured Information Standards) is a not-for-profit consortium that drives the development, convergence and adoption of open standards for the global information society. For more information about OASIS, visit: http://www.oasis-open.org/committees/wemi/.
About Telerik
Telerik is a market-leading provider of end-to-end solutions for application development, automated testing, agile project management, reporting, and content management across all major Microsoft development platforms. Telerik's award-winning software development products enable enterprises and organizations of every size to generate tangible productivity gains, reduce time-to-market, and stay on time and under budget. With tens of thousands of users in more than 90 countries around the world, Telerik's customers include numerous Fortune 2000 companies, academic institutions, governments, and non-profit organizations.
###
Media Contacts
BJ Holtgrewe
Telerik
P: 888-365-2779 x130
E: bj.holtgrewe (a t) telerik.com
Lisa Brandli
Interprose Public Relations
P: 425-653-1246
E: lisa_brandli (a t) interprosepr.com
If you are testing your web application, it seems natural to test it with not only one, but with all of these most popular browsers (cross-browser testing).
This blog post will show you how to record your automated tests with one browser and automatically execute the recorded tests with the other ones. With Ranorex v3.2 (and higher versions) you can run your test in Internet Explorer, Mozilla Firefox, Google Chrome and Apple Safari.

Run one Ranorex Test Script in different Browser (Cross-Browser Testing)
Sample Test Suite ProjectTo demonstrate how to perform a multiple browser test, we will generate a small sample which enters data in our VIP Database Test Web Application, a small web application having the same functionality as the VIP Database you might know from our user guide.
First of all we’ll create a Test Case holding two Recordings, one for opening and one for closing the browser as setup and teardown modules.
Now we add a “OpenBrowser” action to the OpenBrowser Module with “http://www.ranorex.com/web-testing-examples/vip/” as Url and e.g. “IE” as browser.
As next step we add a recording module validating the status String on connecting and disconnecting.
The recording module simply
Make sure that the RanoreXPath of your App Folder does not include any browser specific equation like “browsername=…”.
Make also sure to have two repository items representing the connection status text, one for “Online” and one for “Offline”. This allows you to overcome issues with delaying validation steps. In our application it takes some time that the status text changes from “connecting…” to “Online”. To make the Validation work, we can simply add the actual validation into the RanoreXPath and only validate the existence of the status text in our web page. By doing so, we are using the search timeout of the repository item to wait for the status text to change.
Additionally to the TestConnection recording, we will generate a recording for adding VIP’s to the database. This recording will be added to a new Test Case as we want to data driven add VIP’s and do not want to open and close the browser and testing the connection with each iteration of adding a new VIP.
The recording might look something like this:
As we want to make our test data driven, we have to add variables which can be bound with the data from our data source.
The key sequences for first and last name contain the variables $FirstName and $LastName.
To select the category, we have to add a SetValue action and set the TagValue to the variable $Category.
The gender can be set by adding a variable to the RanoreXPath of the corresponding repository item.
Additionally, we validate the VIP count against a variable $VIP_Count.
After generating the recording, we create a data source for the Test Case Add_VIP’s and bind the data tables to the variables of the recording AddVIP.
As last step we add a Close Application action to the CloseBrowser Module with the application folder of the web application as repository item.
Now we can execute our Test Suite Project, which:
To perform these steps not only for IE but also for the other 3 browser which are supported, we first make the browser which will be started in the Recording “OpenBrowser” variable.
Therefore open the recording “OpenBrowser” and edit the browser which should be started. Now choose “As new Variable…” instead of “IE” and add a new Variable called BrowserName.
After that, add a new simple data table to the Test Case “Add_VIP_and_Validate”, holding the names of the different browsers and bind the data connector to the variable “BrowserName”.
After making the browser variable that way and binding this variable to a table holding all supported browser names, you can execute your test script for all supported browser.