Talk:Concurrent testing

This article is rated Start-class on Wikipedia's content assessment scale. It is of interest to the following WikiProjects:

Computing 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 ??? This article has not yet received a rating on the project's importance scale.

I am thinking of aligning the text to the references (and add some other references) - specifically, to align the descriptions to the ideas of testing for concurrency (shared memory & data) rather than "multiple users using a system simultaneously". For this, I think load testing and software performance testing should be able to cover this. Comments? — Preceding unsigned comment added by Yorkyabroad (talk • contribs) 16:59, 11 February 2018 (UTC)Reply

It does seem that what this page is describing is the same as load testing or reliability testing. But for concurrency, does that need to be on a differently named page, or better, on an existing page covering testing methods? Faught (talk) 04:29, 12 February 2018 (UTC)Reply

Yeah, I could think testing for concurrency can be a section in another page rather than an article on it's own. Maybe it's worth inserting that update in the load and/or performance test pages, then nominating this page afterwards for removal/deletion. Yorkyabroad (talk) 20:32, 12 February 2018 (UTC)Reply

Please go ahead and use templates to propose a merge or move or just do it if it is not controversial. I think your idea about the main topic is correct. When you do, will you please address the question in the following section about parallel testing? Will you also address the link given in the article Software_testing#Concurrent_testing?Stephen Charles Thompson (talk) 21:25, 19 October 2018 (UTC)Reply

Some additional specific references added and text added to align to the referenced literature. The comparison to stress testing is, I think, a confusion - it is not mentioned in any of the references (even the original general references) so I have flagged this as a non-sequitur for later removal. Yorkyabroad (talk) 16:28, 1 May 2019 (UTC)Reply

Binder's book mentions testing for concurrency as a pre-requisite to stress testing. I will re-work the section to list historical approaches to testing for concurrency and then probably remove the "concurrent vs stress" part.Yorkyabroad (talk) 11:18, 5 May 2019 (UTC)Reply

What is the relationship to the term Parallel testing, which I see defined on various websites as:

• Testing of multiple applications or subcomponents of one application concurrently to reduce the test time.[1][2]
• Testing multiple applications or subcomponents of one application concurrently to reduce the test time. Parallel tests consist of two or more parts (projects or project suites) that check different parts or functional characteristics of an application.[3]

If parallel testing is a separate topic, you please create a stub for Parallel testing? Stephen Charles Thompson (talk) 21:21, 19 October 2018 (UTC)Reply

It could be that "parallel testing" is a form of "concurrent computing" applied to test suites/programs. Not sure (yet) if parallel testing should be a new/separate page. It might be better to include those as approaches to test suite execution/scheduling under test suite. Yorkyabroad (talk) 11:25, 5 May 2019 (UTC)Reply