BibSonomy publications for /user/ist_spl/caseWed Jul 30 15:21:39 CEST 2008Journal of Systems and Software2234-248A relation-based method combining functional and structural testing for test case generation812008case gray-box structural contracts generation test testing testdata functional SOFL specification-based oracle Wed Jul 23 14:50:44 CEST 2008London, UKECOOP '00: Proceedings of the 14th European Conference on Object-Oriented Programming472--492Automated Test Case Generation from Dynamic Models2000automated test coverage statemachine systemtest UML Use-Cases generation case We have recently shown how use cases can be systematically transformed into UML state charts considering all relevant information from a use case specification, including pre- and postconditions. The resulting state charts can have transitions with conditions and actions, as well as nested states (sub and stub states). The current paper outlines how test suites with a given coverage level can be automatically generated from these state charts. We do so by mapping state chart elements to the STRIPS planning language. The application of the state of the art planning tool graphplan yields the different test cases as solutions to a planning problem. The test cases (sequences of messages plus test data) can be used for automated or manual software testing on system level.Thu Jul 10 17:18:29 CEST 2008ProjektseminarVom Use Case zum Test Case2008testdata ScenTED Use-Cases testing requirements case UML metaheuristic based Thu Jul 10 17:05:34 CEST 2008Test case derived from requirement specification2003testing based specification requirements test Use-Cases case Wed Jun 11 10:21:56 CEST 2008The Computer JournalMR: Der Ansatz ist ein Gray-Box-Ansatz, obwohl es auf Modellen basiert, muss das Programm selbst auch ausgeführt werden um bestimmte Eingaben für das Verfahren zu liefern. Die Generierung von Testdaten ist kaum automatisiert. Für IST-SPL interessant wegen den Formalismen für Aktivitätsdiagramme. UML Activity Diagram-Based Automatic Test Case Generation For Java Programs2007Java case automated testing test software diagram generation UML activity Test case generation based on design specifications is an important part of testing processes. In this paper, Unified Modeling Language activity diagrams are used as design specifications. By setting up several test adequacy criteria with respect to activity diagrams, an automatic approach is presented to generate test cases for Java programs. Instead of directly deriving test cases from activity diagrams, this approach selects test cases from a set of randomly generated ones according to a given test adequacy criterion. In the approach, we first instrument a Java program under testing according to its activity diagram model, and randomly generate abundant test cases for the program. Then, by running the instrumented program we obtain the corresponding program execution traces. Finally, by matching these traces with the behavior of the activity diagram, a reduced set of test cases are selected according to the given test adequacy criterion. This approach can also be used to check the consistency between the program execution traces and the behavior of activity diagrams. Tue Jun 03 16:59:26 CEST 2008New York, NY, USAAST '06: Proceedings of the 2006 international workshop on Automation of software test2--8Automatic test case generation for UML activity diagrams JAVA2006generation test diagrams UML case automated activity The test case generation from design specifications is an important work in testing phase. In this paper, we use UML activity diagrams as design specifications, and present an automatic test case generation approach. The approach first randomly generates abundant test cases for a JAVA program under testing. Then, by running the program with the generated test cases, we can get the corresponding program execution traces. Last, by comparing these traces with the given activity diagram according to the specific coverage criteria, we can get a reduced test case set which meets the test adequacy criteria. The approachcan also be used to check the consistency between the program execution traces and the behavior of UML activity diagrams.Fri May 30 17:44:59 CEST 2008Proceedings of the Doctoral Symposium affiliated with the Fifth Integrated Formal Methods Conference (IFM 2005)Electronic Notes in Theoretical Computer Science#oct#MR: Stark formalisiertes und mathematisch ergründetes Werk. Basierend auf der Spezifikation des IUT (gegeben in LTS) wird der Lösungsraum durch data abstraction eingeengt (mittels µCRL). Mittels enumerativ tools (wie TGV) werden dann abstrakte Testfälle generiert. Die konkreten Daten (Ein und Ausgaben!) werden mittels constraint-solving techniques (mittels Prolog) ermittelt. Future Work soll ermöglichen UML-Spezifikationen als Eingabe zu erlauben und die Testfälle sollen in TTCN-3 generiert werden! Spätestens dann wird dieser Ansatz für IST-SPL sehr interessant.25--48Automatic Model-Based Generation of Parameterized Test Cases Using Data Abstraction1912007constraint-solving case based testing abstraction model Conformance generation data test Developing test suites is a costly and error-prone process. Model-based test generation tools facilitate this process by automatically generating test cases from system models. The applicability of these tools, however, depends on the size of the target systems. Here, we propose an approach to generate test cases by combining data abstraction, enumerative test generation and constraint-solving. Given the concrete specification of a possibly infinite system, data abstraction allows to derive an abstract system, which is finite and thus suitable for the automatic generation of abstract test cases with enumerative tools. To execute abstract test cases, we have to instantiate them with concrete data. For data selection we make use of constraint-solving techniques.Wed May 21 11:42:25 CEST 2008New York, NY, USAICSE '08: Proceedings of the 30th international conference on Software engineeringMR: nuetzlich fuer IST-SPL nur wegen der Referenzen auf eingesetzte Techniken zur ' Test Case Generation using model checkers '.161--170The effect of program and model structure on mc/dc test adequacy coverage2008generation automated model case test checking In avionics and other critical systems domains, adequacy of test suites is currently measured using the MC/DC metric on source code (or on a model in model-based development). We believe that the rigor of the MC/DC metric is highly sensitive to the structure of the implementation and can therefore be misleading as a test adequacy criterion. We investigate this hypothesis by empirically studying the effect of program structure on MC/DC coverage. To perform this investigation, we use six realistic systems from the civil avionics domain and two toy examples. For each of these systems, we use two versions of their implementation-with and without expression folding (i.e., inlining). To assess the sensitivity of MC/DC to program structure, we first generate test suites that satisfy MC/DC over a non-inlined implementation. We then run the generated test suites over the inlined implementation and measure MC/DC achieved. For our realistic examples, the test suites yield an average reduction of 29.5% in MC/DC achieved over the inlined implementations at 5% statistical significance level.