In this article we discuss sample test cases for cross browser testing. We cover some of the common compatibility scenarios under which you can test your website for cross browser tests. So let’s take a look at those scenarios.
Here are some of the scenarios that you can check and build up your test cases.
You have to decide how many mainstream browsers your app or website supports. Some of the common browsers include – Chrome, Firefox, Opera, Safari, Edge and UCBrowser. Your client should know how many browsers they wish to support. In case if the support for some specific app is not included, what are the alternatives. You have to check with client before you decide the scope of the test as you’d be using only specific number of browsers.
- Does the website loads on browser?
- Does the elements (such as buttons, forms, menu) visible?
- Does the elements clickable on page?
- Does the content of the page visible on all devices?
- Does the webpage require specific browser version?
- Does the webpage takes longer time to load on browser?
Your test should include mobile browser. Each mobile platform has different type of browsers to test in such as Chrome, Safari, UCBrowser, Tea Shark etc.
Depending on how you wish to test, you’d be categorizing the mobile app or the websites performance on specific device platform. You have platform such as Linux, Windows, Mac, Android and few others. Your test scope depends on the device platform that clients wishes to target.
- Does this website or app opens on tablet?
- Does this website opens on smartphone?
- Does this website responds to the specific resolution?
- Does this website opens on Windows platform?
- Does this website opens on Apple iOS?
- What are some of the other device platform that supported by website?
A large part of the cross browser testing revolves around CSS. This is what makes and breaks the app or website in any device. So most of the things that you’re going to test would be around this element. You have plenty of tests to be done in order to validate the performance of your website. Here are some of the questions that you can have in test scenario.
- What CSS Version is used?
- What CSS Version is supported by browser?
- What CSS rendering engine is under usage?
- Does CSS throws error?
- Does CSS Minification affects rendering?
- Does CSS minification causes more errors?
- Does CSS contains code for responsive layout?
- Does CSS makes calls to external image sources?
- Does CSS makes calls to external font sources?
- Does the size of CSS reducing the page speed?
- Does the CSS rendering affecting loading of certain elements?
These are some of the common questions that you should create scenario on and make tests accordingly.
- Does the JS library used affects the resolution of the device?
Almost every website these days makes use of tables of some sort that contains the data. The tables on the pages could be – CSS Table or HTML Table. In case of the dynamic data using AJAX or jquery, you’d find that such tables are worth testing.
- Does the tables work in responsive layout?
- Does the tables render properly for viewing on specific resolution?
- Does the data appears correctly in the respective tables?
- Does the HTML table respond to the responsive layout?
- Does the CSS table breaks in responsive layout?
- Does the dynamic data appears properly in the responsive layout?
These are some common test scenarios on which you can build your test cases. In case of tables or any grid layout on the page you have to make the test cases depending on how the project is designed. You have to adjust your test scenarios based on the tabular content on the page.
Often ignored point while testing the websites. Most of the website render differently if the connection speed is low. They render the items with small size first before rendering bigger sized elements. And you can write test cases of those conditions for your network tests.
- Does the website loads partially under slow connection?
- Does the website render at all on slow connection?
- Does the website misses important elements while completely rendering on slow connection?
- Does the content delivery network (CDN) affects rendering of webpage?
- Does ISP speed affects rendering of page across browser?
- Does the browser responds well for slow connection?
Most of the time above scenarios are more than enough to validate the performance of the website across multiple platforms. There are some of the other tests you can perform under OS, network and few other variables. However those tests will be too deep and may often give similar results under certain browser sets. That being said, hope you find the information here usful for writing the test cases. Do post your comments and suggestion below.