@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{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} } @incollection{Nebut2006, title = {System Testing of Product Lines: From Requirements to Test Cases}, author = {Clementine Nebut and Yves Traon and Jean-Marc ER Jezequel}, booktitle = {Software Product Lines - Research Issues in Engineering and Management}, editor = {Timo Kakola and Juan Carlos Duenas}, note = {MR: Bei dem beschriebenen Ansatz ist es notwendig die Testdaten manuell einzufügen für die Testgenerierung und Simulation. Im Artikel wird trotzdem von der Generierung der konkreten Testfälle gesprochen, die konkreten Daten werden aber ausgeblendet! Ansatz baut auf Use Cases als Anforderungen auf, die mit UML-Sequenzdiagrammen (als Systemscenarios) erweitert sind und als Eingabe gedacht sind. Aus diesen werden automatisch Testszenarien abgeleitet. Nützliche Ideen: - OCL zur Beschreibung von Pre- und Postbedingungen für die Testszenarios. - Test Synthesis zur Effizienzsteigerung bei der Ableitung der Testfälle. - Verwandschaft zu ScenTED wurde skizziert. Usefulness for IST-SPL (-/0/+/++/+++): ++ (Verwandschaft zu ScenTED) }, pages = {447--477}, publisher = {Springer-Verlag}, year = 2006, url = {http://dx.doi.org/10.1007/978-3-540-33253-4_12}, biburl = {http://www.bibsonomy.org/bibtex/2a20ee1265fe5c6f075c5b2d05ee032bb/ist_spl}, keywords = {cases line ocl product requirements system testing uml use} } @book{Reuys2006, title = {Anforderungsbasierte Ableitung von Systemtestfall-Szenarien in der Software-Produktlinien-Entwicklung}, author = {Andreas Reuys}, publisher = {Logos Berlin}, year = 2006, url = {http://www.amazon.de/gp/redirect.html%3FASIN=383251435X%26tag=ws%26lcode=xm2%26cID=2025%26ccmID=165953%26location=/o/ASIN/383251435X%253FSubscriptionId=13CT5CVB80YFWJEPWS02}, ean = {9783832514358}, asin = {383251435X}, isbn = {383251435X}, biburl = {http://www.bibsonomy.org/bibtex/2b16f35af29812ed0f63b2ebd8bccc966/ist_spl}, keywords = {based line product requirements scenario software testing} } @inproceedings{Cohen2006, title = {Coverage and adequacy in software product line testing}, address = {New York, NY, USA}, author = {Myra B. Cohen and Matthew B. Dwyer and Jiangfan Shi}, booktitle = {ROSATEA '06: Proceedings of the ISSTA 2006 workshop on Role of software architecture for testing and analysis}, pages = {53--63}, publisher = {ACM}, year = 2006, url = {http://portal.acm.org/citation.cfm?id=1147249.1147257&coll=Portal&dl=GUIDE&CFID=65839091&CFTOKEN=21681387}, location = {Portland, Maine}, isbn = {1-59593-459-6}, doi = {http://doi.acm.org/10.1145/1147249.1147257}, abstract = {Software product line modeling has received a great deal of attention for its potential in fostering reuse of software artifacts across development phases. Research on the testing phase, has focused on identifying the potential for reuse of test cases across product line instances. While this offers potential reductions in test development effort for a given product line instance, it does not focus on and leverage the fundamental abstraction that is inherent in software product lines - variability.In this paper, we illustrate how rich software product line modeling notations can be mapped onto an underlying relational model that captures variability in the feasible product line instances. This relational model serves as the semantic basis for defining a family of coverage criteria for testing of a product line. These criteria make it possible to accumulate test coverage information for the product line itself over the course of multiple product line instance development efforts. Cumulative coverage, in turn, enables targeted testing efforts for new product line instances. We describe how combinatorial interaction testing methods can be applied to define test configurations that achieve a desired level of coverage and identify challenges to scaling such methods to large, complex software product lines. }, biburl = {http://www.bibsonomy.org/bibtex/24e49dee20bb58ab0b5160a54950cbf88/ist_spl}, keywords = {line product software testing} }