Content deleted Content added
Added references |
de orphaned |
||
| (14 intermediate revisions by 8 users not shown) | |||
Line 1:
{{Short description|Checking web applications in various browsers}}
'''Cross-browser testing''' is a type of non-functional [[software testing]] where [[
▲'''Cross-browser testing''' is a type of non-functional [[software testing]] where [[Web application|web applications]] are checked for support across different browsers and devices<ref>{{Cite web|last=Team|first=Blisk|title=Cross-browser Testing|url=https://blisk.io/|access-date=2021-07-26|website=Blisk|language=en-US}}</ref>. Cross-browser testing can also provide an objective, independent view of the status of the web application to allow the business to appreciate and understand the risks of releasing it or implementing new feature(s)<ref>{{Cite web|title=What is Cross Browser Testing and How to Perform It: A Complete Guide|url=https://www.softwaretestinghelp.com/how-is-cross-browser-testing-performed/|access-date=2021-07-26|website=www.softwaretestinghelp.com}}</ref>. 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 website 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<ref>{{Cite web|title=Introduction to cross browser testing - Learn web development {{!}} MDN|url=https://developer.mozilla.org/en-US/docs/Learn/Tools_and_testing/Cross_browser_testing/Introduction|access-date=2021-07-26|website=developer.mozilla.org|language=en-US}}</ref>.
== History ==
[[File:Device-market-share.png|thumb|Device market share (Jan 2009 - May 2021)]]
The term "cross-browser testing" originated in the early 2000s with the advent of various web browsers that rendered web pages in different ways and supported different web technologies.<ref>{{Cite web|title=Reading: Web Browser {{!}} Introduction to Computer Applications and Concepts|url=https://courses.lumenlearning.com/zeliite115/chapter/reading-web-browser/|access-date=2021-08-02|website=courses.lumenlearning.com}}</ref> As a result, this led to inconsistencies in the behavior of web applications across browsers. In the early 2010s, smartphones entered the device market, and their number began to grow significantly. According to the data from Statcounter,<ref>{{Cite web|title=Desktop vs Mobile vs Tablet Market Share Worldwide|url=https://gs.statcounter.com/platform-market-share/desktop-mobile-tablet/worldwide/|access-date=2021-07-26|website=StatCounter Global Stats|language=en}}</ref>
== Cross-browser testing process ==
Line 15 ⟶ 13:
* performs its functions within an acceptable time,
* is sufficiently usable,
* can be installed and run in its intended web browsers and devices
* achieves the general result its stakeholders desire.
=== 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,<ref>{{Cite web|title=What is Usability?|url=https://www.interaction-design.org/literature/topics/usability|access-date=2021-08-02|website=The Interaction Design Foundation|language=en}}</ref> such as features, integrations with third-party services, forms, and touch input for mobile or tablets. They also test accessibility,<ref>{{Cite web|title=Accessibility testing - W3C Wiki|url=https://www.w3.org/wiki/Accessibility_testing|access-date=2021-08-02|website=www.w3.org}}</ref> 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 "Full-stack web development", cross-browser tests are performed by web developers as they develop elements of the [[user interface]] and functionalities.
== References ==▼
{{reflist}}▼
[[Category:Software testing]]
▲== References ==
[[Category:Web browsers]]
▲{{reflist}}
| |||