Cross-browser testing: Difference between revisions

Revision as of 09:30, 22 July 2021

Revision as of 10:39, 22 July 2021

Line 3:

'''Cross-browser testing''' is a type of non-functional [[software testing]] in which [[Web application|web applications]] are checked for support across different browsers and devices. Cross-browser testing can also provide an objective, independent view of the web application to allow the business to appreciate and understand the risks of releasing it or implementing new feature(s). Test techniques include the process of executing a web application with the intent of finding failures in different browsers and devices and verifying that the software productwebsite is fit for use in all of them. In other words, Cross-browser testing is verification that web application behaves in various [[Web browser|web browsers]] identically.

== History ==

Line 18:

=== QA engineers ===

Cross-browser testing is usually performed by QA engineers. After the development team builds a web application or site, QA engineers evaluate the completed project. The QA engineer tests the consistency of the content and layout, such as how fonts and images display, and whether the [[responsive web design]] works, if applicable. Next, they check the web application or site's usability, such as features, integrations with third-party services, forms, and touch input for mobile or tablets. They also test accessibility, such as the presence of alt text for images or closed captioning for video.

=== Web developers ===

Cross-browser testing can be conducted even if the web application is partially complete. With such an approach, also called as full"Full-stack web development", cross-browser tests are performed by web developers as they develop elements of the [[user interface]] and functionalities.