Cross-browser testing: Difference between revisions

Content deleted Content added
Changing short description from "Cross-browser testing is a type of non-functional software testing where web applications are checked for support across different browsers and devices." to "Checking web applications in various browsers" (Shortdesc helper)
clean out crap sources / stuff that doesn't actually support the article
Line 7:
 
== 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.<ref>{{Cite web|first=|title=Cross-browser Testing|url=https://blisk.io/|url-status=live|access-date=2021-08-02|website=Blisk|language=en-US}}</ref> In general, these properties indicate the extent to which the web application under test:
* meets the requirements that guided its design and development,
* responds correctly to all kinds of inputs,
* responds correctly to all kinds of inputs,<ref>{{Citation|last=Busbee|first=Kenneth Leroy|title=Software Testing|date=2018-12-15|url=https://press.rebus.community/programmingfundamentals/chapter/software-testing/|work=Programming Fundamentals|language=en|access-date=2021-08-02}}</ref>
* performs its functions within an acceptable time,
* is sufficiently usable,
* can be installed and run in its intended web browsers and devices<ref>{{Cite web|date=2018-11-12|title=What Is Cross-Browser Compatibility And Why Do We Need It?|url=https://www.softwaretestingclass.com/cross-browser-compatibility-testing/|access-date=2021-08-02|website=Software Testing Class|language=en-US}}</ref>
* 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.<ref>{{Cite web|title=11 Ways to Improve Software Testing through Planning, Work Environment, Automated Testing, and Reporting|url=https://www.altexsoft.com/blog/engineering/software-testing-qa-best-practices/|access-date=2021-08-02|website=AltexSoft|language=en-US}}</ref> 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",<ref>{{Cite web|title=What is a Full-Stack Developer? Our 2021 Guide|url=https://careerfoundry.com/en/blog/web-development/what-is-a-full-stack-web-developer/|access-date=2021-08-02|website=careerfoundry.com|language=en-US}}</ref> cross-browser tests are performed by web developers as they develop elements of the [[user interface]] and functionalities.
 
== References ==