Wikipedia:Articles for deletion/End-to-end testing


 * The following discussion is an archived debate of the proposed deletion of the article below. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review).  No further edits should be made to this page.

The result was speedy deletion (G5). (non-admin closure) st170e talk 17:13, 14 December 2016 (UTC)

End-to-end testing

 * – ( View AfD View log  Stats )

Since only one book is listed, and nothing is said about notability, the real purpose of this article appears to be to publicize the book. A redirect to system testing would be in order with this information included there. Robert McClenon (talk) 02:47, 25 November 2016 (UTC)
 * Redirect to system testing: It would've been a plausible search term; or should I say "speedy redirect" to fasten it up. KGirlTrucker81huh? what I'm been doing 03:22, 25 November 2016 (UTC)
 * Note: This debate has been included in the list of Computing-related deletion discussions. Shawn in Montreal (talk) 04:31, 25 November 2016 (UTC)


 * Redirect per nom and KGT. Widely used term in the field, which should go somewhere. Patar knight - chat/contributions 14:14, 25 November 2016 (UTC)
 * Speedy Keep The nomination does not propose to delete anything. Andrew D. (talk) 14:32, 26 November 2016 (UTC)
 * While this is misfiled and should probably have been in Articles for redirect, we can decide to redirect. Since you don't have any objections to redirecting, (only deletion) please consider clarifying your position on the redirect. 208.81.212.224 (talk) 19:39, 7 December 2016 (UTC)
 * I consider the proposal to be absurd. The topic is clearly notable -- see the NASA System Engineering Handbook, for example.  What we should be doing is improving the topic, not trying to sweep it under the carpet. Andrew D. (talk) 20:37, 7 December 2016 (UTC)


 * Keep on the basis that terminology is inconsistent or "fuzzy" in this field and "end-to-end testing" is sometimes, though not always, distinguished from "system testing", as indeed in this article although none too clearly. End-to-end testing is "usually similar to system testing, but [undertaken]... to test a user's complete interaction with the system" or it's done "for multiple interrelated systems ... to verify that all interrelated systems ... are tested in an operational environment.". Another source talks about "... a full range of unit, integration, system, stress testing, and end-to-end testing...". (my emphasis) A better article could be made on this topic Noyster (talk),  12:52, 1 December 2016 (UTC)

 Relisted to generate a more thorough discussion and clearer consensus.

Please add new comments below this notice. Thanks,  Sandstein   11:27, 3 December 2016 (UTC)  Relisted to generate a more thorough discussion and clearer consensus.
 * Redirect and salvage what content is possible to salvage. It's not a common term (as is noted by Noyster) and a section in system testing would suffice to indicate what the differences are, and the redirect would be enough for the one or two links that may exist or be created. Walter Görlitz (talk) 14:29, 6 December 2016 (UTC)

Please add new comments below this notice. Thanks, st170e talk 01:25, 12 December 2016 (UTC)


 * The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.