New HP UFT Best Practices Document: "Cross-Browser Functional Testing Best Practices"

A new HP Unified Functional Testing best practices document has just been published, called "Cross-Browser Functional Testing Best Practices"  (you'll need an HP Passport to access it).  It provides concepts and guidelines for designing and executing functional tests that involve different browsers, and some best practices for developing portable cross-browser tests using HP Unified Functional Testing.  For convenience, I've attached a copy of the document to this post.

 

Let me know what you think about it in the comments box below, as well as additional tips and best practices you'd like to share.  

 

To whet your appetite, here's the introduction to the document:

 

 

Introduction to Cross-Browser Functional Testing

The term cross-browser testing usually means some variation of testing of a web-based application on different browsers. We might have a requirement that our application must run on Internet Explorer, Firefox, Chrome and Safari. Conversely, we might have to support all versions of Internet Explorer from version 8 and later. And what do we mean by ‘must run’? Is it enough that the functionality is identical on different browsers? What about the way the page looks – is it acceptable if two buttons appear on the same line in one browser, but appear one above the other in a different browser? This document will examine some common types of cross-browser functional testing and will present some best practices  that you can adopt in order to achieve your cross-browser testing goals.

 

You can also download Unified Functional Testing here.

Comments
fingold | ‎07-29-2013 05:52 AM

Nice article, yet I would add that when testing for cross-browser you should also check for different OS versions.

Same i.e version behave differently on different  OS (winXP,Win7, Win8…) and same for Firefox (with other OS available as well).

 

Also of course I will add different locals to this. since language effect fonts, page margins, size of elements etc… but this is less important than the OS. Different OS sometimes mean different DOM and JavaScript engines, so issues may appear.

 

| ‎07-29-2013 05:54 AM

Hi fingold,

 

These are excellent points.  Thanks for sharing!

Aarush | ‎08-23-2013 02:47 AM

Thanks, for sharing this article.

Very well written and of great help to increase knowledge in Cross Browser functionality.

My question is that don't we check the Functinality behavior in this.

| ‎08-25-2013 12:41 AM

Thanks Aarush.  The actual check for the functionality depends on the web application, and needs to be written accordingly.  It's not really possible to provide a generic check for functionality.  The document provides tips for writing generic, portable tests that account for differences between browsers, which you can then apply to writing tests for your specific use cases and user stories.

Naveen_KumarN | ‎02-13-2014 03:06 AM

Thanks! So, we can write only code to test across all the browsers in UFT. Correct me, if I am wrong. 

 

Thanks!

NaveenKumar N

Leave a Comment

We encourage you to share your comments on this post. Comments are moderated and will be reviewed
and posted as promptly as possible during regular business hours

To ensure your comment is published, be sure to follow the Community Guidelines.

Be sure to enter a unique name. You can't reuse a name that's already in use.
Be sure to enter a unique email address. You can't reuse an email address that's already in use.
Type the characters you see in the picture above.Type the words you hear.
Search
About the Author
Malcolm is a functional architect, focusing on best practices and methodologies across the software development lifecycle.


Follow Us
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation