@article{LeGall:1996:FST, title = {Formal Specifications and Test: Correctness and Oracle}, author = {P. {Le Gall} and A. Arnould}, journal = {Lecture Notes in Computer Science}, pages = {342--??}, volume = 1130, year = 1996, bibdate = {Tue Oct 29 14:12:39 MST 1996}, issn = {0302-9743}, acknowledgement = {Nelson H. F. Beebe, Center for Scientific Computing, University of Utah, Department of Mathematics, 110 LCB, 155 S 1400 E RM 233, Salt Lake City, UT 84112-0090, USA, Tel: +1 801 581 5254, FAX: +1 801 581 4148, e-mail: \path|beebe@math.utah.edu|, \path|beebe@acm.org|, \path|beebe@computer.org|, \path|beebe@ieee.org| (Internet), URL: \path|http://www.math.utah.edu/~beebe/|}, coden = {LNCSD9}, description = {Computer Science Bibliography Collection}, biburl = {http://www.bibsonomy.org/bibtex/291f73a0b6315aee831988a133974e83d/ist_spl}, keywords = {correctness oracle singlesystem} } @inproceedings{conf/iri/TanSL04, title = {Specification-based Testing with Linear Temporal Logic}, author = {Li Tan and Oleg Sokolsky and Insup Lee}, booktitle = {IRI}, editor = {Du Zhang and {\'E}ric Gr{\'e}goire and Doug DeGroot}, note = {ST: Anforderungen werden in LTL spezifiziert.Es wird eine Metrik definiert, die eine Aussage ueber die Abdeckung der spezifizierten Eingenschaften durch eine Testsuite macht. Durch ein Abdeckungskriterium wird eine Testsuite mit endlichen Testfaellen definiert, die die spezifizierten Eigenschaften testet. }, pages = {493--498}, publisher = {IEEE Systems, Man, and Cybernetics Society}, year = 2004, bibsource = {DBLP, http://dblp.uni-trier.de/db/conf/iri/iri2004.html#TanSL04}, bibdate = {2004-12-02}, isbn = {0-7803-8819-4}, description = {Computer Science Bibliography Collection}, biburl = {http://www.bibsonomy.org/bibtex/2489f963043db59b7bf4d78128112420e/ist_spl}, keywords = {LTL automated generation singlesystem specification-based test} } @inproceedings{1032732, title = {Generating Test Cases from UML Activity Diagram based on Gray-Box Method}, address = {Washington, DC, USA}, author = {Wang Linzhang and Yuan Jiesong and Yu Xiaofeng and Hu Jun and Li Xuandong and Zheng Guoliang}, booktitle = {APSEC '04: Proceedings of the 11th Asia-Pacific Software Engineering Conference}, note = {ST:Testfaelle mit Testdaten werden automatisch auf Basis eines UML-Aktivitaetsdiagramms abgeleitet. Abdeckungskriterium: Kanten werden hoechstens einmal abgedeckt, Schleifen werden hoechstens einmal durchlaufen. Aktivitaetsdiagramm muss sehr feingranular sein und Methodenaufrufe in den Aktivitaeten anzeigen. }, pages = {284--291}, publisher = {IEEE Computer Society}, year = 2004, url = {http://portal.acm.org/citation.cfm?id=1032732#}, isbn = {0-7695-2245-9}, doi = {http://dx.doi.org/10.1109/APSEC.2004.55}, description = {Generating Test Cases from UML Activity Diagram based on Gray-Box Method}, abstract = {Test case generation is the most important part of the testing efforts, the automation of specification based test case generation needs formal or semi-formal specifications. As a semi-formal modelling language, UML is widely used to describe analysis and design specifications by both academia and industry, thus UML models become the sources of test generation naturally. Test cases are usually generated from the requirement or the code while the design is seldom concerned, this paper proposes an approach to generate test cases directly from UML activity diagram using gray-box method, where the design is reused to avoid the cost of test model creation. In this approach, test scenarios are directly derived from the activity diagram modelling an operation. Then all the information for test case generation, i.e. input/output sequence and parameters, the constraint conditions and expected object method sequence, is extracted from each test scenario. At last, the possible values of all the input/output parameters could be generated by applying category-partition method, and test suite could be systematically generated to find the inconsistency between the implementation and the design. A prototype tool named UMLTGF has been developed to support the above process.}, biburl = {http://www.bibsonomy.org/bibtex/21b3b853c356f30b69b0e73bae873f883/ist_spl}, keywords = {UML activity automated blackbox diagram singlesystem whitebox} } @article{PetPar98, title = {Using Test Oracles Generated from Program Documentation}, author = {D. Peters and D. Parnas}, journal = {IEEE Transactions on Software Engineering}, note = {ST: Spezifikation einer SW-Einheit (im Paper Methoden) wird formal beschrieben. Tool leitet automatisch Orakel ab. Grenzen werden bei dynamische Datenstrukturen erreicht da sie schwer beschreibbar sind. Die formale Spezifikation erscheint in den Beispielen sehr aufwendig.}, number = 3, pages = {161--173}, volume = 24, year = 1998, keyword = {program testing, finite state machine, tabular expression}, description = {Computer Science Bibliography Collection}, biburl = {http://www.bibsonomy.org/bibtex/23724f0ee7961e2e7a2f826e484f88ee4/ist_spl}, keywords = {finite formal machine oracle program singlesystem specification state test testing} } @article{10.1109/ICSE.1996.493403, title = {Assertion-oriented automated test data generation}, address = {Los Alamitos, CA, USA}, author = {B. Korel and A.M. Al-Yami}, journal = {icse}, note = {ST: Testdaten werden mit Hilfe der Assertions automatisch abgeleitet. Das Ziel ist es Testdaten abzuleiten die die Assertion verletzen. Mit dieser Vorgehensweise werden mehr Fehler gefunden als mit herkömmlichen Methoden.}, pages = 71, publisher = {IEEE Computer Society}, volume = 00, year = 1996, issn = {0270-5257}, doi = {http://doi.ieeecomputersociety.org/10.1109/ICSE.1996.493403}, description = {Assertion-oriented automated test data generation}, biburl = {http://www.bibsonomy.org/bibtex/210ecb63b6d1d3302d7e4ebfdfc984f6f/ist_spl}, keywords = {assertions automated data generation single system test} } @inproceedings{conf/sigsoft/BertolinoG03, title = {Use case-based testing of product lines}, author = {Antonia Bertolino and Stefania Gnesi}, booktitle = {ESEC / SIGSOFT FSE}, note = {ST: Testfaelle und Testdaten werden auf Basis von Use Cases abgeleitet, indem in den Use Cases beinhaltete Szenarien abgedeckt werden. Fazit: Keine Automatisierung von Testdatenableitung, keine Trennung von Domain- und Application Engineering zur Wiederverwendung von Testdaten. }, pages = {355--358}, year = 2003, url = {http://doi.acm.org/10.1145/940071.940120}, bibsource = {DBLP, http://dblp.uni-trier.de/db/conf/sigsoft/fse2003.html#BertolinoG03}, bibdate = {2006-02-15}, description = {Computer Science Bibliography Collection}, biburl = {http://www.bibsonomy.org/bibtex/24a37cf834f5567a673368fb54eb9d34a/ist_spl}, keywords = {Use-Cases category line manually method partion procuct systemtest} } @inproceedings{conf/sigsoft/UzuncaovaGKB07, title = {A specification-based approach to testing software product lines}, author = {Engin Uzuncaova and Daniel Garcia and Sarfraz Khurshid and Don S. Batory}, booktitle = {ESEC/SIGSOFT FSE}, editor = {Ivica Crnkovic and Antonia Bertolino}, note = {ST: Die Spezifikation der Produktlinie liegt in einer formalen Beschreibung vor (LTL) Es wird ein Modelchecking-Verfahren durchgefuehrt um zu beweisen, dass die Spezifikation gilt. Fazit: Keine explizite Ableitung von Testdaten, die Spezifikation muss formal vorliegen. }, pages = {525--528}, publisher = {ACM}, year = 2007, url = {http://doi.acm.org/10.1145/1287624.1287701}, bibdate = {2007-10-23}, bibsource = {DBLP, http://dblp.uni-trier.de/db/conf/sigsoft/fse2007.html#UzuncaovaGKB07}, isbn = {978-1-59593-811-4}, description = {Computer Science Bibliography Collection}, biburl = {http://www.bibsonomy.org/bibtex/233f9d7285e59ffa1460ea88d3bfac3cf/ist_spl}, keywords = {AHEAD Alloy GenVoca data generation lines product specification-based test testing} } @inproceedings{Kishi:2004:DTPL, title = {Design Testing for Product Line Development based on Test Scenarios}, address = {Boston, MA}, author = {Tomoji Kishi and Natsuko Noda}, booktitle = {Proceedings of the International Workshop on Software Product Line Testing ({SPL}i{T} 2004)}, editor = {Birgit Geppert and Charles Krueger and Jenny Li}, month = {August}, note = {ST: Das zu testende System und die mit dem System in Interaktion stehende Umgebung werden als Zustandsautomat modelliert. Testdaten ergeben sich aus den Transitionen. Es werden Modelchecking Techniken angewendet um Invarianten zu prüfen. }, pages = {19--26}, year = 2004, category = {Testing}, available = {1}, newinversion = {3.5}, description = {Computer Science Bibliography Collection}, abstract = {In product line development, we develop each product by analyzing features of the product, examining what variants should be bound to variation points in core assets and designing product specific parts that are not supported by the core assets. In order to test the design of each product efficiently, it is desirable to develop test scenarios systematically from selected features and developed design model. In this paper, we propose a design testing method based on test scenarios utilizing model checking techniques. We discuss how we define variation points in test scenarios to make test scenarios reusable, and how we define traceability among feature model, design model and test scenarios to develop test scenarios efficiently for each product.}, biburl = {http://www.bibsonomy.org/bibtex/2d9cd68668830d12b86180df66f98d4b6/ist_spl}, keywords = {checking model scenarios statecharts techniques test} } @inproceedings{Hartmann:2004:VPL, title = {A {UML}-based Approach for Validating Product Lines}, address = {Boston, MA}, author = {Jean Hartmann and Marlon Vieira and Axel Ruder}, booktitle = {Proceedings of the International Workshop on Software Product Line Testing ({SPL}i{T} 2004)}, editor = {Birgit Geppert and Charles Krueger and Jenny Li}, month = {August}, note = {ST:Basiert auf UML-Aktivitätsdiagrammen Entwicklung eines Tools auf Basis von Rational-Rose. Für die Testdatengewinnung wird eine Ä-Klassenanalyse durchgeführt. Wichtig sind daher die Bedingungen an der Verzweigungspunkten im Aktivitätsdiagramm, da die Auswahl des Testfalls von diesen abhängt. Nutzer wählt Produkt aus und das Tool generiert für ein produkt Testfälle Fazit: Es werden zwar Testfälle mit Testdaten für die Produkte einer Produktlinie automatisch generiert, aber es findet keine Trennung zwischen Domain- und Application Engineering statt. Es ist kein Wiederverwendungsansatz erkennbar. Außerdem arbeitet das Tool auf Basis anderer kommerzieller Tools (Rose). }, pages = {58--65}, year = 2004, category = {Testing}, available = {1}, newinversion = {3.5}, description = {Computer Science Bibliography Collection}, abstract = {The Unified Modeling Language (UML) is gaining wide acceptance in industry as the new de facto visual modeling language and as such it is being used within Siemens to model large, complex new product lines. As a result, we are extending our existing UML-based approaches to component and system validation to address the needs of product line validation. In this paper, we will focus on describing the extensions made to our system testing approach in which Activity Diagrams that form the basis for the test specification are annotated with variation points and conformance tests are then automatically generated to validate each product variant. We are also implementing these extensions as part of our Test Development Environment for UML (TDE/UML) automated test generation technology, which is currently integrated with the IBM/Rational Rose UML modeling tool and coupled with test execution tools, such as a graphical capture/replay tool. This paper provides an outline of our existing UML-based approach to system validation, but focuses on how we supplement the existing UML diagrams with information concerning the variation points for product-line validation.}, biburl = {http://www.bibsonomy.org/bibtex/242adeda1515608dae46ba044035d5904/ist_spl}, keywords = {UML activity diagrams line product validation} } @inproceedings{Stephenson:2004:TDG, title = {Test Data Generation for Product Lines - {A} Mutation Testing Approach}, address = {Boston, MA}, author = {Zoë Stephenson and Yuan Zhan and John Clark and John McDermid}, booktitle = {Proceedings of the International Workshop on Software Product Line Testing ({SPL}i{T} 2004)}, editor = {Birgit Geppert and Charles Krueger and Jenny Li}, month = {August}, note = {ST:Fokus liegt auf Test der Variablen Artefakte, es soll gezeigt werden dass das richtige Produkt abgeleitet wurde. Test der Korrekten Bindung. Testdaten-Generierung um zu zeigen, dass der Output sich für zwei unterschiedliche Varianten unterscheidet. Output wird dann gegen die Anforderungen der verschiedenen Varianten getestet, so kann festgestellt werden, ob die richtige Variante gebunden wurde. Technik erfordert lauffähiges Produkt. Entwicklung eines Tools, welches für zwei Sourceocde-Artefakte, die sich durch Variabilität unterscheiden, Testdaten generiert. Fazit: eher für die Überprüfung geeignet ob Varianten korrekt gebunden wurden. Kein Wiederverwendungsansatz für Testdaten, keine explizite Trennung der Testdatenermittlung für Domain / Application Engineering. }, pages = {13--18}, year = 2004, category = {Testing}, available = {1}, newinversion = {3.5}, description = {Computer Science Bibliography Collection}, abstract = {Modern product lines typically generate large and complex software products. There is an associated cost increase from the need to test such products, especially for a safety-critical embedded system. We propose a method by which characteristics of the product line can be used as a way of reducing the test data search space and providing effective test data for relevant testing problems. We illustrate this with a solution to the problem of checking that a generated instance is a correct reflection of the required behavior.}, biburl = {http://www.bibsonomy.org/bibtex/28439146ef6fcdee2f3481b1468064316/ist_spl}, keywords = {binding generation line product testdata variant} }