Talk:Web testing

Computing Stub‑class

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Stub	This article has been rated as Stub-class on Wikipedia's content assessment scale.
???	This article has not yet received a rating on the project's importance scale.
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

what is the difference between the testing of web application and desktop application other than the web based & desktop based?

A request... It'd be good if someone could outline the unique challenges of web testing (i.e. multi-tier/platforms/languages - xml, html, css, javascript, asp/php/jsp, DLL, dbms, client browser standards, etc. etc.)...Even better...How about some practical suggestions for scoping, designing, performing web application testing. —Preceding unsigned comment added by 194.201.204.112 (talk) 10:04, 22 July 2008 (UTC)[reply]

There is little difference between web testing and desktop testing. --Walter Görlitz (talk) 19:57, 3 February 2010 (UTC)[reply]

This article isn't much more than a list of tools, many of which can be used to test desktop applications. --Walter Görlitz (talk) 02:31, 23 June 2010 (UTC)[reply]

This article should be descriptive about why the word web testing is required. How it is different than software testing. This should be the main focus for this article. —Preceding unsigned comment added by 116.74.114.3 (talk) 04:39, 6 September 2010 (UTC)[reply]

This article is a glorified list advertising testing tools

This article seems to have an undue focus on the tools with which you can do some forms of web testing, rather than methodologies and processes. --Topperfalkon (talk) 15:16, 22 January 2016 (UTC)[reply]

That's always a problem with articles like this. Good content is hard, relies on the time of busy people (why write here for free when you can get £40-50 / hour writing about it elsewhere?) and spamlists are easy. As there are already two links to a "list of tools" article, let's be brutal and nuke the lot. Andy Dingley (talk) 19:04, 22 January 2016 (UTC)[reply]

But we should at least link to the lists then. Walter Görlitz (talk) 04:03, 23 January 2016 (UTC)[reply]

Some proposed changes

It is requested that an edit be made to the semi-protected article at Web testing. (edit · history · last · links · protection log)

This template must be followed by a complete and specific description of the request, that is, specify what text should be removed and a verbatim copy of the text that should replace it. "Please change X" is not acceptable and will be rejected; the request must be of the form "please change X to Y".

The edit may be made by any autoconfirmed user. Remember to change the |answered=no parameter to "yes" when the request has been accepted, rejected or on hold awaiting user input. This is so that inactive or completed requests don't needlessly fill up the edit requests category. You may also wish to use the {{ESp}} template in the response. To request that a page be protected or unprotected, make a protection request.

• Information to be added or removed: change “Robert Johnson” to “Bob Johnson” • Explanation of issue: Get my name correct. I agree this page is way out of date, however, I would like my name fixed. • References supporting change: Testing Applications on the Web Johnson-Bob (talk) 11:45, 1 January 2020 (UTC)[reply]