-
[show abstract]
[hide abstract]
ABSTRACT: One of the important tasks during software testing is the generation of test cases. Various approaches have been proposed to automate this task. The approaches available, however, often have problems limiting their use. A problem of dynamic test case generation approaches, for instance, is that a large number of iterations can be necessary to obtain test cases. This article proposes a novel algorithm for path-oriented test case generation based on binary search and describes a possible implementation.
07/2004;
-
[show abstract]
[hide abstract]
ABSTRACT: One of the important tasks during software testing is the generation of appropriate test data. Various techniques have been proposed to automate this task. The techniques available, however, often have problems limiting their use. In the case of dynamic test data generation techniques, a frequent problem is that a large number of iterations might be necessary to obtain test data. This article proposes a novel technique for automated test data generation based on binary search. Binary search conducts searching tasks in logarithmic time, as long as its assumptions are fulfilled. This article shows that these assumptions can also be fulfilled in the case of path-oriented test data generation and presents a technique which can be used to generate test data covering certain paths in class methods.
07/2004;
-
[show abstract]
[hide abstract]
ABSTRACT: The use of components in development of complex software systems can surely have various benefits. Their testing, however, is still one of the open issues in software engineering. Both the developer of a component and the developer of a system using components often face the problem that information vital for certain development tasks is not available. Such a lack of information has various consequences to both. One of the important consequences is that it might not only obligate the developer of a system to test the components used, it might also complicate these tests. This article gives an overview of component testing approaches that explicitly respect a lack of information in development.
07/2004;
-
[show abstract]
[hide abstract]
ABSTRACT: Development of a software system from existing components can surely have various benefits, but can also entail a series of problems. One type of problems is caused by a limited exchange of information between the developer and user of a component. A limited exchange and thereby a lack of information can have various consequences, among them the requirement to test a component prior to its integration into a software system. A lack of information cannot only make test prior to integration necessary, it can also complicate this tasks.
07/2004;
-
[show abstract]
[hide abstract]
ABSTRACT: One of the important tasks during software testing is the generation of test cases. Unfortunately, existing approaches to test case generation often have problems limiting their use. A problem of dynamic test case generation approaches, for instance, is that a large number of iterations can be necessary to obtain test cases. This article introduces a formal framework for the application of the well-known search strategy of binary search in path-oriented test case generation and explains the binary search-based test case generation (BINTEST) algorithm.
07/2004;
-
Proceedings of the Sixteenth International Conference on Software Engineering & Knowledge Engineering (SEKE'2004), Banff, Alberta, Canada, June 20-24, 2004; 01/2004
-
Software Process: Improvement and Practice. 01/2004; 9:229-238.
-
Computer and Information Sciences - ISCIS 2003, 18th International Symposium, Antalya, Turkey, November 3-5, 2003, Proceedings; 01/2003
-
[show abstract]
[hide abstract]
ABSTRACT: Although both black- and white-box testing have the same objective, namely detecting faults in a program, they are often conducted separately. In our opinion, the reason is the lack of techniques and tools integrating both strategies, although an integration can substantially decrease testing costs. Specifically, an integrated technique can generate a reduced test suite, as single test cases can cover both specification and implementation at the same time. This paper proposes a new graphical representation of classes, which can be used for integrated class-level blackand white-box testing. Its distinguishing feature from existing representations is that each method of a class is shown from two perspectives, namely the specification and implementation view. Both the specification of a method and its implementation are represented as control flow graphs, which allows black- and white-box testing by structural techniques. Moreover, a test suite reduction technique has been developed for adjusting white-box test cases to blackbox testing. 1
08/2001;
-
[show abstract]
[hide abstract]
ABSTRACT: In recent years, several techniques have been proposed for class-level regression testing. Most of these techniques focus either on white- or black-box testing, although an integrated approach can have several benefits. As similar tasks have to be carried out for both white- and black-box testing, an integrated approach can improve efficiency and cost effectiveness. This article explains a new approach for class-level regression testing, integrating existing techniques. Particularly, those of Rothermel et al. and Hong et al. for whitebox regression testing and black-box testing, respectively, have been integrated into a single technique. The benefits of the resulting technique are shown by example. 1
07/2001;
-
[show abstract]
[hide abstract]
ABSTRACT: Evolution is one of the integral parts in the lifecycle of a process. Similar to software, a process often has to be modified in order to fulfill changed process requirements, or to correct problems that occurred during its enactment. Although currently changes are often implemented ad-hoc without any consideration of side-effects and risks, it is obvious that such side-effects and especially the risk inherent to a change have to be analyzed before actually changing a process. Additionally, it is often impossible to stop, change and restart a process. In these cases, techniques are required which are capable of analyzing and changing currently enacted processes.
06/2001;
-
[show abstract]
[hide abstract]
ABSTRACT: The main idea of component-based development is to use existing components for building software. The resulting software often has features which complicate testing, such a feature is, for example, the absence of component source code.
06/2001;
-
[show abstract]
[hide abstract]
ABSTRACT: Evolution is one of the integral parts in the lifecycle of a process. Similar to software, a process often has to be modified in order to fulfil changed process requirements, or to correct problems that occurred during its enactment. Although currently changes are often implemented ad-hoc without any consideration of side-e#ects and risks, it is obvious that such side-e#ects and especially the risk inherent to a change have to be analyzed before actually changing a process. Additionally, often it is impossible to stop, change and restart a process. In these cases, techniques are required which are capable of analyzing and changing currently enacted processes. This article describes the approach for risk and decision analysis elaborated in the ESPRIT project Process Instance Evolution (PIE). The main concept of the approach used in PIE consists of determining the probability distribution of important process parameters and calculating risk measures for decision making. This article describes the overall approach and explains the algorithm used for determining probability distributions. 1
03/2001;
-
[show abstract]
[hide abstract]
ABSTRACT: Process support environments (PSEs) are widely used for modelling, enacting and analyzing human intensive processes. The benefits of a PSE become apparent when processes to be supported are long lived and distributed and contain heterogeneous components. Generally, such processes are subject to dynamic evolution, i.e. they have to be changed during their execution.
03/2001;
-
[show abstract]
[hide abstract]
ABSTRACT: An important activity in software development is the testing of developed software using the appropriate techniques. Obviously, these techniques have to take into account the type of the software process and the type of the developed software. This article proposes a technique for testing classes developed during a special type of software process, namely object-oriented prototyping. Furthermore, the technique developed is suited for application domains requiring a high degree of quality of the deployed software.
10/2000;
-
Software Process Technology, 7th European Workshop, EWSPT 2000, Kaprun, Austria, February 21-25, 2000, Proceedings; 01/2000
-
[show abstract]
[hide abstract]
ABSTRACT: Development of a software system from existing compo-nents can surely have various benefits, but can also entail a series of problems. One type of problems is caused by a limited exchange of information between the developer and user of a component. A limited exchange and thereby a lack of information can have various consequences, among them the requirement to test a component prior to its in-tegration into a software system. A lack of information cannot only make test prior to integration necessary, it can also complicate this tasks. However, difficulties in testing can be avoided if certain provisions to increase testability are taken beforehand. This article describes a new form of improving testability of, particularly commercial, compo-nents, the self-testing COTS components (STECC) strategy.
-
Yalda Ariana, Sami Beydeda,
Oliver Effner,
Marcel Gleis,
Volker Gruhn,
Martin Krzysiak,
Jens Lauert,
Thomas Louis,
Carsten Röttgers,
Kai Schwaighofer,
Martin Testrot,
Uwe Ulrich,
Yingguang Yuan
