Too Darned Big to Test: Testing large systems is a daunting task, but there are steps we can take to ease the pain

The increasing size and complexity of software, coupled with concurrency and distributed systems, has made apparent the ineffectiveness of using only handcrafted tests. The misuse of code coverage and avoidance of random testing has exacerbated the problem. We must start again, beginning with good d...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:ACM queue 2005-02, Vol.3 (1), p.30-37
1. Verfasser: Stobie, Keith
Format: Magazinearticle
Sprache:eng
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
container_end_page 37
container_issue 1
container_start_page 30
container_title ACM queue
container_volume 3
creator Stobie, Keith
description The increasing size and complexity of software, coupled with concurrency and distributed systems, has made apparent the ineffectiveness of using only handcrafted tests. The misuse of code coverage and avoidance of random testing has exacerbated the problem. We must start again, beginning with good design (including dependency analysis), good static checking (including model property checking), and good unit testing (including good input selection). Code coverage can help select and prioritize tests to make you more efficient, as can the all-pairs technique for controlling the number of configurations. Finally, testers can use models to generate test coverage and good stochastic tests, and to act as test oracles.
doi_str_mv 10.1145/1046931.1046944
format Magazinearticle
fullrecord <record><control><sourceid>crossref</sourceid><recordid>TN_cdi_crossref_primary_10_1145_1046931_1046944</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>10_1145_1046931_1046944</sourcerecordid><originalsourceid>FETCH-crossref_primary_10_1145_1046931_10469443</originalsourceid><addsrcrecordid>eNpjYBA3NNAzNDQx1Tc0MDGzNDbUA9MmJkwMnIamJka65uYmlixwtrEBBwNXcXGWgYGRiaWpCSeDWEh-voJLYlFeaoqCU2a6Qkm-QkhqcQkPA2taYk5xKi-U5mbQd3MNcfbQTS7KLy4uSk2LLyjKzE0sqow3NIgHWR8PtT4ear0x6ToA3DYzpA</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>magazinearticle</recordtype></control><display><type>magazinearticle</type><title>Too Darned Big to Test: Testing large systems is a daunting task, but there are steps we can take to ease the pain</title><source>Alma/SFX Local Collection</source><creator>Stobie, Keith</creator><creatorcontrib>Stobie, Keith</creatorcontrib><description>The increasing size and complexity of software, coupled with concurrency and distributed systems, has made apparent the ineffectiveness of using only handcrafted tests. The misuse of code coverage and avoidance of random testing has exacerbated the problem. We must start again, beginning with good design (including dependency analysis), good static checking (including model property checking), and good unit testing (including good input selection). Code coverage can help select and prioritize tests to make you more efficient, as can the all-pairs technique for controlling the number of configurations. Finally, testers can use models to generate test coverage and good stochastic tests, and to act as test oracles.</description><identifier>ISSN: 1542-7730</identifier><identifier>EISSN: 1542-7749</identifier><identifier>DOI: 10.1145/1046931.1046944</identifier><language>eng</language><ispartof>ACM queue, 2005-02, Vol.3 (1), p.30-37</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed><cites>FETCH-crossref_primary_10_1145_1046931_10469443</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><link.rule.ids>780,784,27924</link.rule.ids></links><search><creatorcontrib>Stobie, Keith</creatorcontrib><title>Too Darned Big to Test: Testing large systems is a daunting task, but there are steps we can take to ease the pain</title><title>ACM queue</title><description>The increasing size and complexity of software, coupled with concurrency and distributed systems, has made apparent the ineffectiveness of using only handcrafted tests. The misuse of code coverage and avoidance of random testing has exacerbated the problem. We must start again, beginning with good design (including dependency analysis), good static checking (including model property checking), and good unit testing (including good input selection). Code coverage can help select and prioritize tests to make you more efficient, as can the all-pairs technique for controlling the number of configurations. Finally, testers can use models to generate test coverage and good stochastic tests, and to act as test oracles.</description><issn>1542-7730</issn><issn>1542-7749</issn><fulltext>true</fulltext><rsrctype>magazinearticle</rsrctype><creationdate>2005</creationdate><recordtype>magazinearticle</recordtype><recordid>eNpjYBA3NNAzNDQx1Tc0MDGzNDbUA9MmJkwMnIamJka65uYmlixwtrEBBwNXcXGWgYGRiaWpCSeDWEh-voJLYlFeaoqCU2a6Qkm-QkhqcQkPA2taYk5xKi-U5mbQd3MNcfbQTS7KLy4uSk2LLyjKzE0sqow3NIgHWR8PtT4ear0x6ToA3DYzpA</recordid><startdate>200502</startdate><enddate>200502</enddate><creator>Stobie, Keith</creator><scope>AAYXX</scope><scope>CITATION</scope></search><sort><creationdate>200502</creationdate><title>Too Darned Big to Test</title><author>Stobie, Keith</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-crossref_primary_10_1145_1046931_10469443</frbrgroupid><rsrctype>magazinearticle</rsrctype><prefilter>magazinearticle</prefilter><language>eng</language><creationdate>2005</creationdate><toplevel>online_resources</toplevel><creatorcontrib>Stobie, Keith</creatorcontrib><collection>CrossRef</collection><jtitle>ACM queue</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>Stobie, Keith</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Too Darned Big to Test: Testing large systems is a daunting task, but there are steps we can take to ease the pain</atitle><jtitle>ACM queue</jtitle><date>2005-02</date><risdate>2005</risdate><volume>3</volume><issue>1</issue><spage>30</spage><epage>37</epage><pages>30-37</pages><issn>1542-7730</issn><eissn>1542-7749</eissn><abstract>The increasing size and complexity of software, coupled with concurrency and distributed systems, has made apparent the ineffectiveness of using only handcrafted tests. The misuse of code coverage and avoidance of random testing has exacerbated the problem. We must start again, beginning with good design (including dependency analysis), good static checking (including model property checking), and good unit testing (including good input selection). Code coverage can help select and prioritize tests to make you more efficient, as can the all-pairs technique for controlling the number of configurations. Finally, testers can use models to generate test coverage and good stochastic tests, and to act as test oracles.</abstract><doi>10.1145/1046931.1046944</doi></addata></record>
fulltext fulltext
identifier ISSN: 1542-7730
ispartof ACM queue, 2005-02, Vol.3 (1), p.30-37
issn 1542-7730
1542-7749
language eng
recordid cdi_crossref_primary_10_1145_1046931_1046944
source Alma/SFX Local Collection
title Too Darned Big to Test: Testing large systems is a daunting task, but there are steps we can take to ease the pain
url https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-08T12%3A37%3A08IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-crossref&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Too%20Darned%20Big%20to%20Test:%20Testing%20large%20systems%20is%20a%20daunting%20task,%20but%20there%20are%20steps%20we%20can%20take%20to%20ease%20the%20pain&rft.jtitle=ACM%20queue&rft.au=Stobie,%20Keith&rft.date=2005-02&rft.volume=3&rft.issue=1&rft.spage=30&rft.epage=37&rft.pages=30-37&rft.issn=1542-7730&rft.eissn=1542-7749&rft_id=info:doi/10.1145/1046931.1046944&rft_dat=%3Ccrossref%3E10_1145_1046931_1046944%3C/crossref%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true