Compatibility testing
It is proposed that this article be deleted because of the following concern:
If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it. This message has remained in place for seven days, so the article may be deleted without further notice. Find sources: "Compatibility testing" – news · newspapers · books · scholar · JSTOR Nominator: Please consider notifying the author/project: {{subst:proposed deletion notify|Compatibility testing|concern=Unencyclopedic litany of things that can be tested for compatibility. Likely [[WP:OR|original research]]. Note that [[WP:NOTDIC|Wikipedia is not a dictionary]].}} ~~~~Timestamp: 20161230204542 20:45, 30 December 2016 (UTC) Administrators: delete |
 | This article needs additional citations for verification. (September 2016) |
Compatibility testing, part of software functional tests, is testing conducted on the application to evaluate the application's compatibility with the computing environment. Computing environment may contain some or all of the below mentioned elements:
- Computing capacity of Hardware Platform (IBM 360, HP 9000, etc.)..
- Bandwidth handling capacity of networking hardware
- Compatibility of peripherals (Printer, DVD drive, etc.)
- Operating systems (Linux, Windows, Mac etc.)
- Database (Oracle, SQL Server, MySQL, etc.)
- Other System Software (Web server, networking/ messaging tool, etc.)
- Certification testing falls within the scope of compatibility testing. Product Vendors run the complete suite of testing on the newer computing environment to get their application certified for a specific Operating Systems or Databases.
- Server Compatibility Level is specific to servers and it dictates how specific language elements of the database functions in relation to previous versions.[1] In other words, it's the "backwards compatibility" of a server to an earlier versions.
- Carrier compatibility (Verizon, Sprint, Orange, O2, AirTel, etc.)
- Backwards compatibility.
- Hardware (different phones)
- Different Compilers (compile the code correctly)
- Runs on multiple host/guest Emulators
- Browser compatibility (Chrome, Firefox, Netscape, Internet Explorer, Safari, etc.) Browser compatibility testing, can be more appropriately referred to as user experience testing. This requires that the web applications are tested on different web browsers, to ensure the following:
- Users have the same visual experience irrespective of the browsers through which they view the web application.
- In terms of functionality, the application must behave and respond the same way across different browsers.
References
- ^ "Compatibility Level vs Database Version". 2016-01-05. Retrieved 2016-09-03.
 | This computer-programming-related article is a stub. You can help Wikipedia by expanding it. |