| Author | Title | Year | Journal/Proceedings | Reftype | DOI/URL |
|---|---|---|---|---|---|
| Bertolino, A. & Gnesi, S. | PLUTO: A Test Methodology for Product Families | 2003 | PFE | inproceedings | URL |
| Abstract: The testing stage for a product belonging to a family is a crucial and expensive part of development. Yet the derivation of test cases for product families has so far received little attention. We focus here on test planning, that is the most critical part of testing. We outline a simple methodology we are developing for this purpose, called PLUTO, relying on the early requirements specification expressed as Use Cases. We also overview the related literature. | |||||
BibTeX:
@inproceedings{Bertolino2003a,
author = {Antonia Bertolino and Stefania Gnesi},
title = {PLUTO: A Test Methodology for Product Families},
booktitle = {PFE},
year = {2003},
pages = {181-197},
note = {MR: Beschäftigt sich mit dem Systemtest. Variabilität der PL auch in Testartefakten berücksichtigt, aber keine systematische Wiederverwendung von Testeingaben und erwarteten Ergebnissen. Testableitung teilweise manuell. Nicht modellbasiert.},
url = {http://www.springerlink.com/content/9hl2jpcf3ge8hk89}
}
|
|||||
| Edwards, S. H. | Black-box testing using flowgraphs: an experimental assessment of effectiveness and automation potential | 2001 | Software Testing, Verification and Reliability | article | DOIURL |
| Abstract: A black-box testing strategy based on Zweben et al.'s specification-based test data adequacy criteria is explored. The approach focuses on generating a flowgraph from a component's specification and applying analogues of white-box strategies to it. An experimental assessment of the fault-detecting ability of test sets generated using this approach was performed for three of Zweben et al.'s criteria using mutation analysis. By using precondition, postcondition and invariant checking wrappers around the component under test, fault detection ratios competitive with white-box techniques were achieved. Experience with a prototype test set generator used in the experiment suggests that practical automation may be feasible. | |||||
BibTeX:
@article{Edwards2000,
author = {Stephen H. Edwards},
title = {Black-box testing using flowgraphs: an experimental assessment of effectiveness and automation potential},
journal = {Software Testing, Verification and Reliability},
year = {2001},
volume = {10},
number = {4},
pages = {249--262},
note = {MR: Aus dem Text: Testing 'to contract' is at the heart of specification based testing. Es wird gezeigt wie ein Anzatz von [Zweben1992] (der leider nicht auffindbar ist) sich praktisch umsetzen lässt. Dabei spielen die Contracts für die Generierung der Test(ein/aus)gabedaten grundlegende Rolle. Die getesteten Komponenten werden als Flowgraphs dargestellt, womit sie große Analogie zu Aktivitätsdiagrammen besitzen. Obwohl noch Probleme bei der Auswahl der Testdaten (infeasable paths) existieren, wurde gezeigt, dass dieser Ansatz großen Potential besitzt. Für das Experiment wurde Fehlerinjektionsmethoden angewendet (Mutation).},
url = {http://dx.doi.org/10.1002/1099-1689(200012)10:4\%3C249::AID-STVR215\%3E3.0.CO;2-C},
doi = {http://dx.doi.org/10.1002/1099-1689(200012)10:4<249::AID-STVR215>3.0.CO;2-C}
}
|
|||||
| Liggesmeyer, P. | Software-Qualität: Testen, Analysieren und Verifizieren von Software [BibTeX] |
2002 | book | URL | |
BibTeX:
@book{Liggesmeyer2002,
author = {Peter Liggesmeyer},
title = {Software-Qualität: Testen, Analysieren und Verifizieren von Software},
publisher = {Spektrum Akademischer Verlag},
year = {2002},
note = {MR: Wertvoll ist die Klassifikation und Beschreibung der SW-Prüftechniken unterteilt u.a. in funktionsorientierte (spezifikationsbasierte) und strukturierte (codebasierte).},
url = {http://www.amazon.de/gp/redirect.html%3FASIN=3827411181%26tag=ws%26lcode=xm2%26cID=2025%26ccmID=165953%26location=/o/ASIN/3827411181%253FSubscriptionId=13CT5CVB80YFWJEPWS02}
}
|
|||||
| Peled, D. A. | Software Reliability Methods [BibTeX] |
2001 | book | URL | |
BibTeX:
@book{Peled2001,
author = {Doron A. Peled},
title = {Software Reliability Methods},
publisher = {Springer},
year = {2001},
edition = {1},
url = {http://www.amazon.com/Software-Reliability-Methods-Computer-Science/dp/0387951067%3FSubscriptionId%3D13CT5CVB80YFWJEPWS02%26tag%3Dws%26linkCode%3Dxm2%26camp%3D2025%26creative%3D165953%26creativeASIN%3D0387951067}
}
|
|||||
| Pohl, K. & Metzger, A. | Software product line testing | 2006 | Commun. ACM | article | DOIURL |
| Abstract: Exploring principles and potential solutions. | |||||
BibTeX:
@article{Pohl2006,
author = {Klaus Pohl and Andreas Metzger},
title = {Software product line testing},
journal = {Commun. ACM},
publisher = {ACM},
year = {2006},
volume = {49},
number = {12},
pages = {78--81},
url = {http://portal.acm.org/citation.cfm?id=1183236.1183271&coll=Portal&dl=GUIDE&CFID=1470361&CFTOKEN=75766762},
doi = {http://doi.acm.org/10.1145/1183236.1183271}
}
|
|||||
| Reis, S., Metzger, A. & Pohl, K. | Integration Testing in Software Product Line Engineering: A Model-Based Technique | 2007 | FASE | inproceedings | |
| Abstract: The development process in software product line engineering is divided into domain engineering and application engineering. As a consequence of this division, tests should be performed in both processes. However, existing testing techniques for single systems cannot be applied during domain engineering, because of the variability in the domain artifacts. Existing software product line test techniques only cover unit and system tests. Our contribution is a model-based, automated integration test technique that can be applied during domain engineering. For generating integration test case scenarios, the technique abstracts from variability and assumes that placeholders are created for variability. The generated scenarios cover all interactions between the integrated components, which are specified in a test model. Additionally, the technique reduces the effort for creating placeholders by minimizing the number of placeholders within the integration test case scenarios. We have experimentally measured the performance of the technique and the potential reduction of placeholders. | |||||
BibTeX:
@inproceedings{Reis2007,
author = {Sacha Reis and Andreas Metzger and Klaus Pohl},
title = {Integration Testing in Software Product Line Engineering: A Model-Based Technique},
booktitle = {FASE},
year = {2007},
pages = {321-335}
}
|
|||||
| Reuys, A., Kamsties, E., Pohl, K. & Reis, S. | Model-Based System Testing of Software Product Families [BibTeX] |
2005 | CAiSE | inproceedings | |
BibTeX:
@inproceedings{Reuys2005,
author = {Andreas Reuys and Erik Kamsties and Klaus Pohl and Sacha Reis},
title = {Model-Based System Testing of Software Product Families},
booktitle = {CAiSE},
year = {2005},
pages = {519-534}
}
|
|||||
| Spillner, A. | Zuerst die Anforderungen testen! Wie soll das gehen? [BibTeX] |
2005 | Tagungsband Requirements Days 2005 | inproceedings | |
BibTeX:
@inproceedings{Spillner2005,
author = {Andreas Spillner},
title = {Zuerst die Anforderungen testen! Wie soll das gehen?},
booktitle = {Tagungsband Requirements Days 2005},
year = {2005}
}
|
|||||
| Stricker, V. | Datenflussbasierte Identifikation erneut auszuführender Applikationstestfälle in der Produktlinienentwicklung [BibTeX] |
2006 | School: Universität Duisburg-Essen | mastersthesis | |
BibTeX:
@mastersthesis{Stricker2006,
author = {Vanessa Stricker},
title = {Datenflussbasierte Identifikation erneut auszuf{\"u}hrender Applikationstestf{\"a}lle in der Produktlinienentwicklung },
school = {Universit{\"a}t Duisburg-Essen},
year = {2006}
}
|
|||||
| Vieira, M., Leduc, J., Hasling, B., Subramanyan, R. & Kazmeier, J. | Automation of GUI testing using a model-driven approach | 2006 | AST '06: Proceedings of the 2006 international workshop on Automation of software test | inproceedings | DOIURL |
| Abstract: This paper describes an ongoing research on test case generation based on Unified Modeling Language (UML). The described approach builds on and combines existing techniques for data and graph coverage. It first uses the Category-Partition method to introduce data into the UML model. UML Use Cases and Activity diagrams are used to respectively describe which functionalities should be tested and how to test them. This combination has the potential to create a very large number of test cases. This approach offers two ways to manage the number of tests. First, custom annotations and guards use the Category-Partition data which allows the designer tight control over possible, or impossible, paths. Second, automation allows different configurations for both the data and the graph coverage. The process of modeling UML activity diagrams, annotating them with test data requirements, and generating test scripts from the models is described. The goal of this paper is to illustrate the benefits of our model-based approach for improving automation on software testing. The approach is demonstrated and evaluated based on use cases developed for testing a graphical user interface (GUI). | |||||
BibTeX:
@inproceedings{Vieira2006,
author = {Marlon Vieira and Johanne Leduc and Bill Hasling and Rajesh Subramanyan and Juergen Kazmeier},
title = {Automation of GUI testing using a model-driven approach},
booktitle = {AST '06: Proceedings of the 2006 international workshop on Automation of software test},
publisher = {ACM},
year = {2006},
pages = {9--14},
url = {http://portal.acm.org/citation.cfm?id=1138932},
doi = {http://doi.acm.org/10.1145/1138929.1138932}
}
|
|||||
Created by JabRef export filters on 08/09/2008 by the social publication management platform BibSonomy