Crowd testing

from Wikipedia, the free encyclopedia
The articles public test , beta test and crowdtesting overlap thematically. Help me to better differentiate or merge the articles (→  instructions ) . To do this, take part in the relevant redundancy discussion . Please remove this module only after the redundancy has been completely processed and do not forget to include the relevant entry on the redundancy discussion page{{ Done | 1 = ~~~~}}to mark. VÖRBY ( discussion ) 11:26, November 22, 2017 (CET)

Crowdtesting [kɹaʊd ˈtestɪŋ] refers to the beta testing of software by a mass of testers over the Internet. People who want to earn extra money online are primarily addressed as testers. During testing, the intelligence and manpower of the so-called crowd ( English for “crowd”, “ crowd ”) is used. For example, apps and Web applications prior to the launch to be tested.

advantages

The crowd is characterized by the fact that it has a large number of different test devices ( computer , smartphone , tablet PC, etc.). Since the testers use their own devices, the crowd of testers can potentially cover all end devices with all combinations of manufacturer, operating system , version, browser , provider and display size. This makes it possible to ensure compatibility with as many end devices as possible. The diversified pool of testers enables testing during the entire software life cycle , since in addition to classic functional tests for searching for errors ( bugs ), special target groups are also made accessible for usability tests . Another advantage of crowdtesting is the high flexibility of the crowd, which is ready for use at any time - even on weekends. Since the testers are not involved in the development process, they are impartial towards the product and see potential for improvement, which the actual developers may not notice due to operational blindness. Outsourcing the test processes also means considerable cost savings, as there is no need to set up an extensive range of equipment, and in-house employees do not have to be paid.

Course of a project

A commissioned test project is being worked on by the masses on the Internet. In addition to apps, online shops and browser games, for example, are tested . Each tester reports in detail about any errors found. Depending on the provider, a project manager acts as a link between tester and developer. He is responsible for the quality assurance of the results and serves as a contact for both sides. Finally, the product developers receive a detailed report. In contrast to some forms of crowdsourcing, recreational workers receive something in return for their work. The testers usually receive a performance-based remuneration depending on the number and severity of the errors found - usually in the form of money.

The communication between provider and tester is often realized via a platform in Web 2.0 . As a rule, the provider uses this platform to advertise a new test and, if necessary, addresses certain target groups. If a tester receives an invitation, he can decide whether he would like to take part in the advertised test. After the test has started, the testers receive their tasks and have a certain time frame to complete them. A typical crowd test usually lasts between one and three days. The client then has access to the results.

disadvantage

Crowdtesting does not replace end-to-end tests, nor does it replace functional and non-functional tests, it is just another additional support for testing.

The crowd testers mostly only see the behavior in the apps and web applications on their end device and cannot look behind the scenes into the backend, have no mandatory access to the database, and cannot monitor the systems to determine whether B. memory hogs or the systems are optimally configured.

Whitebox tests are also not possible because the source code is generally not available, otherwise the business model would be exposed to the competition.

history

Historically, crowdtesting is a relatively young term that has only been used more intensively for a few years. It is based on the term crowdsourcing , which was coined in 2006 by Jeff Howe and Mark Robinson ( Wired ).

Web links

Individual evidence

  1. Trends In Software Testing ( Memento of the original from December 28, 2011 in the Internet Archive ) Info: The archive link was automatically inserted and not yet checked. Please check the original and archive link according to the instructions and then remove this notice. , Tanuj Vohra, ITmagz.com, April 8, 2009.  @1@ 2Template: Webachiv / IABot / www.itmagz.com
  2. Jan Wolter: Developing Successful Applications with the Help of Crowd Testing ( Memento of the original from March 28, 2014 in the Internet Archive ) Info: The archive link was automatically inserted and not yet checked. Please check the original and archive link according to the instructions and then remove this notice. , testing experience, March 2014. @1@ 2Template: Webachiv / IABot / www.testhub.com
  3. ^ Jeff Howe: Crowdsourcing. Why the Power of the Crowd is Driving the Future of Business. Three Rivers Press, New York NY 2009, ISBN 978-0-307-39621-1 .