Cross Browser Testing Test Case: 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.
Other Test Cases: Search Filter Test Case
Cross Browser Testing Test Case Browsers: 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 the client before you decide the scope of the test as you’d be using the only specific number of browsers.
- Does the website loads on a browser?
- Do the elements (such as buttons, forms, menu) visible?
- Do the elements clickable on a page?
- Does the content of the page visible on all devices?
- Does the webpage require a specific browser version?
- Does the webpage take a longer time to load on the browser?
Your test should include a mobile browser. Each mobile platform has a different type of browsers to test in such as Chrome, Safari, UCBrowser, Tea Shark, etc.
Cross Browser Testing Test Case Device Platform
Depending on how you wish to test, you’d be categorizing the mobile app or the performance of the website on a specific device platform. You have a platform such as Linux, Windows, Mac, Android, and a few others. Your test scope depends on the device platform that clients wish to target.
- Does this website or app open on a tablet?
- Does this website open on a smartphone?
- Does this website respond to the specific resolution?
- Does this website open on the Windows platform?
- Does this website open on Apple iOS?
- What are some of the other device platforms supported by a website?
Cross Browser Testing Test Case CSS Support
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 to validate the performance of your website. Here are some of the questions that you can have in a test scenario.
- What is CSS Version used?
- What is CSS Version supported by a browser?
- What is the CSS rendering engine under usage?
- Does CSS throw an error?
- Does CSS Minification affect rendering?
- Does CSS minification cause more errors?
- Does CSS contain code for responsive layout?
- Does CSS make calls to external image sources?
- Does CSS make calls to external font sources?
- Does the size of CSS reduce the page speed?
- Does the CSS rendering affect the loading of certain elements?
These are some of the common questions that you should create a scenario on and make tests accordingly.
- Does the JS library use affect the resolution of the device?
Cross Browser Testing Test Case Tables
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 the case of the dynamic data using AJAX or jquery, you’d find that such tables are worth testing.
- Do the tables work in a responsive layout?
- Do the tables render properly for viewing on the specific resolution?
- Does the data appear correctly in the respective tables?
- Does the HTML table respond to the responsive layout?
- Does the CSS table break in a responsive layout?
- Does the dynamic data appear
- properly in the responsive layout?
These are some common test scenarios on which you can build your test cases. In the 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.
Cross Browser Testing Test Case Network
Often ignored point while testing the websites. Most of the websites 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 load partially under a slow connection?
- Does the website render at all on a slow connection?
- Does the website miss important elements while completely rendering on a slow connection?
- Does the content delivery network (CDN) affect the rendering of the webpage?
- Does ISP speed affect the rendering of the page across the browser?
- Does the browser respond well for a 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, I hope you find the information here useful for writing the test cases. Do post your comments and suggestion below.