File Download
  Links for fulltext
     (May Require Subscription)
Supplementary

Article: CHOC'LATE: A framework for specification-based testing

TitleCHOC'LATE: A framework for specification-based testing
Authors
Issue Date2010
PublisherAssociation for Computing Machinery, Inc. The Journal's web site is located at http://www.acm.org/cacm/
Citation
Communications Of The Acm, 2010, v. 53 n. 4, p. 113-118 How to Cite?
AbstractIn spite of its importance in software reliability, testing is labor intensive and expensive. It has been found that software testing without a good strategy may not be more effective than testing the system with random data. Obviously, the effectiveness of testing relies heavily on how well the test suite-the set of test cases actually used-is generated. This is because the comprehensiveness of the test suite will affect the scope of testing and, hence, the chance of revealing software faults. There are two main approaches to generating test suites: specification-based and code-based. The former generates a test suite from information derived from the specification, without requiring the knowledge of the internal structure of the program. The latter approach, on the other hand, generates a test suite based on the source code of the program. Neither of these approaches is sufficient; they are complementary to one another. In software development, the requirements have to be established before implementation, and the specification should exist prior to coding. In this respect, the specification-based approach to test suite generation is particularly useful because test cases can be generated before coding has been completed. This facilitates software development phases to be performed in parallel, thus allowing time for preparing more thorough test plans and yet shortening the length of the whole process. © 2010 ACM.
Persistent Identifierhttp://hdl.handle.net/10722/55460
ISSN
2015 Impact Factor: 3.301
2015 SCImago Journal Rankings: 1.910
ISI Accession Number ID
Funding AgencyGrant Number
Research Grants Council of Hong Kong517704
717308
Hong Kong Polytechnic University1-ZV2H
Australian Research CouncilDP0771733
Funding Information:

This research is supported in part by a grant of the General Research Fund of the Research Grants Council of Hong Kong (Project nos 517704 and 717308), the Department General Research Fund of The Hong Kong Polytechnic University (project no. 1-ZV2H), and a Discovery Grant of the Australian Research Council (project no. DP0771733).

References

 

DC FieldValueLanguage
dc.contributor.authorPoon, PLen_HK
dc.contributor.authorTang, SFen_HK
dc.contributor.authorTse, THen_HK
dc.contributor.authorChen, TYen_HK
dc.date.accessioned2009-08-10T03:43:07Z-
dc.date.available2009-08-10T03:43:07Z-
dc.date.issued2010en_HK
dc.identifier.citationCommunications Of The Acm, 2010, v. 53 n. 4, p. 113-118en_HK
dc.identifier.issn0001-0782en_HK
dc.identifier.urihttp://hdl.handle.net/10722/55460-
dc.description.abstractIn spite of its importance in software reliability, testing is labor intensive and expensive. It has been found that software testing without a good strategy may not be more effective than testing the system with random data. Obviously, the effectiveness of testing relies heavily on how well the test suite-the set of test cases actually used-is generated. This is because the comprehensiveness of the test suite will affect the scope of testing and, hence, the chance of revealing software faults. There are two main approaches to generating test suites: specification-based and code-based. The former generates a test suite from information derived from the specification, without requiring the knowledge of the internal structure of the program. The latter approach, on the other hand, generates a test suite based on the source code of the program. Neither of these approaches is sufficient; they are complementary to one another. In software development, the requirements have to be established before implementation, and the specification should exist prior to coding. In this respect, the specification-based approach to test suite generation is particularly useful because test cases can be generated before coding has been completed. This facilitates software development phases to be performed in parallel, thus allowing time for preparing more thorough test plans and yet shortening the length of the whole process. © 2010 ACM.en_HK
dc.languageeng-
dc.publisherAssociation for Computing Machinery, Inc. The Journal's web site is located at http://www.acm.org/cacm/en_HK
dc.relation.ispartofCommunications of the ACMen_HK
dc.rightsCommunications of the ACM. Copyright © Association for Computing Machinery, Inc..-
dc.rightsCreative Commons: Attribution 3.0 Hong Kong License-
dc.rights©ACM, 2010. This is the author's version of the work. It is posted here by permission of ACM for your personal use. Not for redistribution. The definitive version was published in PUBLICATION, {VOL 53, ISS 4, (APRIL 2010)} http://doi.acm.org/10.1145/nnnnnn.nnnnnn-
dc.titleCHOC'LATE: A framework for specification-based testingen_HK
dc.typeArticleen_HK
dc.identifier.openurlhttp://library.hku.hk:4550/resserv?sid=HKU:IR&issn=0001-0782&volume=53&issue=4&spage=113&epage=118&date=2010&atitle=CHOC%27LATE:+a+framework+for+specification-based+testing-
dc.identifier.emailTse, TH: thtse@cs.hku.hken_HK
dc.identifier.authorityTse, TH=rp00546en_HK
dc.description.naturepostprinten_HK
dc.identifier.doi10.1145/1721654.1721687en_HK
dc.identifier.scopuseid_2-s2.0-77950363280en_HK
dc.identifier.hkuros168425-
dc.relation.referenceshttp://www.scopus.com/mlt/select.url?eid=2-s2.0-77950363280&selection=ref&src=s&origin=recordpageen_HK
dc.identifier.volume53en_HK
dc.identifier.issue4en_HK
dc.identifier.spage113en_HK
dc.identifier.epage118en_HK
dc.identifier.eissn1557-7317-
dc.identifier.isiWOS:000276841200034-
dc.publisher.placeUnited Statesen_HK
dc.identifier.scopusauthoridPoon, PL=7101925990en_HK
dc.identifier.scopusauthoridTang, SF=7403437100en_HK
dc.identifier.scopusauthoridTse, TH=7005496974en_HK
dc.identifier.scopusauthoridChen, TY=13104290200en_HK

Export via OAI-PMH Interface in XML Formats


OR


Export to Other Non-XML Formats