Content deleted Content added
m Bilorv moved page Draft:Cross-browser testing to Cross-browser testing: Publishing accepted Articles for creation submission (AFCH 0.9.1) |
de orphaned |
||
(8 intermediate revisions by 7 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|date=2020-12-01|title=What Is Cross-Browser Testing? A Simple, Practical Guide|url=https://www.testim.io/blog/what-is-cross-browser-testing/|access-date=2021-08-02|website=AI-driven E2E automation with code-like flexibility for your most resilient tests|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>
== Cross-browser testing process ==
Cross-browser testing involves the execution of a web application to evaluate one or more properties of interest on different browsers and devices
* meets the requirements that guided its design and development,
* responds correctly to all kinds of inputs,
* 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
=== 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"
== References ==
{{reflist}}
[[Category:Software testing]]
[[Category:Web browsers]]
|