A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), Monterey, June 2001. To appear.  Home/Search   Document Details and Download   Summary   Related Articles   Check

....using the simulation feature of AUTOFOCUS. 2.1 Formally deriving test sequences With the help of the AUTOFOCUS model, we can now test the resistance of an implementation of the CEPS load transaction against threats. We use the approach of specificationbased testing, as advocated in e.g. WLPS00, PLP01] For this purpose, test case specifications based on the system model have to be formulated. Test specifications would be, for example, that a certain log entry should be generated, certain data is sent on the channels, or a component should reach a success or failure state. The test ....

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), Monterey, June 2001.

....Fig. 5. STD for Issuer 3 Formally deriving test sequences With the help of the AutoFocus model, we can now test the resistance of an implementation of the CEPS load transaction against threats. We use the approach of speci cation based testing, as advocated in e.g. WLPS00, PLP01] For this purpose, test case speci cations based on the system model have to be formulated. Test speci cations would be, for example, that a certain log entry should be generated, certain data is sent on the channels, or a component should reach a success or failure state. The test speci ....

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), Monterey, June 2001. 13

....Figure 3. STD for LSAM 3. Formally deriving test sequences With the help of the AUTOFOCUS model, we can now test the resistance of an implementation of the CEPS load transaction against threats. We use the approach of specification based testing, as advocated in e.g. [13, 11]. For this purpose, test specifications are formulated, for example, that a certain log entry should be generated, certain data is sent on the channels, or a component should reach a particular state. Test sequences, i.e. concrete system behaviours satisfying the test specifications, are then ....

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), Monterey, June 2001.

No context found.

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), Monterey, June 2001. To appear.

No context found.

A. Pretschner, H. L otzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping, pages 155--160, 2001.

No context found.

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), June 2001. To appear.

No context found.

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), June 2001. To appear.

No context found.

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping, pages 155--160, 2001.

No context found.

A. Pretschner, H. L otzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping, pages 155-- 160, 2001.

....######### ##### #### ###### ######### ###### ######## #### ####### ############# ##### # # ## #### ############## Fig. 1. Model Based Testing Contribution The contribution of the paper is a proof of concept of the test case generation technology described in earlier work [16,14] and an extension of previous test generation work in the smart card field [17] The WIM had undergone extensive testing at Giesecke Devrient and is already being marketed; the goal of the work presented here is to provide evidence that the structured, automatic, and reproducible generation of ....

....Searching the state space is achieved by symbolically executing the model. To this end, the AutoFocus model is translated into a constraint logic programming (CLP) language. The translation scheme takes advantage of the simple clock synchronous semantics of AutoFocus; it is described in detail in [16,14]. In a nutshell, each transition of a bottom level component K i.e. a component equipped with a state machine is translated into a formula (## src ,##, #o, ## dst ) guard(##, ## src ) assgmt(#o, ## dst ) 1) indicating that given input ##, the component may proceed from control and ....

Pretschner, A., H. Lotzbeyer and J. Philipps, Model Based Testing in Evolutionary Software Development, in: Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping, 2001, pp. 155--160.

....establish the notion of behavioral equivalence that is at the core of refactoring. It might therefore seem worthwhile to more closely follow XP and to start with an indirect equivalence notion based on test case speci cations; current work on model based test sequence generation techniques (e.g. [26, 27]) could o er some machine assistance in this respect. 11 ....

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), 2001.

....this section, we describe our approach to model based testing on the grounds of Constraint Logic Programming. We restrict ourselves to a coarse description of the basic ideas; details of the translation may be found in [21, 22] the embedding in an incremental development process is discussed in [28]. 27] contains a detailed discussion of our approach. While for the presented smart card example 7 the exact nature of the development process is not crucial, we think our ideas on test case generation are clari ed by their embedding in the process. 4.1 Process Many modern SW development ....

....due to using statecharts in the UML, focuses on modeling rather than validation. In the sequel, when referring to models, we hence speak about behavior models. In an incremental development process, test generation techniques naturally lend themselves to their application in regression testing [28]. With suitable management tools, test cases that have been derived for an earlier increment may be used for regression testing later ones. Note that we do not give a suitable de nition of increment here that extends beyond additional functionality ; this de nition and its embedding in the ....

[Article contains additional citation context not shown here]

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), Monterey, June 2001. To appear.

....has been validated. The implementation process may introduce errors that have to be detected. One instance of conformance testing amounts to showing that the behaviors of the implementation constitute a subset of the behaviors of the speci cation. With this article, we continue a series of papers [21, 22, 26, 27, 28, 29] on model based test case generation for reactive systems speci ed with the CASE tool AutoFocus. The idea is to use the system model (a network of hierarchic components with associated behaviors) for the Supported by the DLR (project MOBASIS) and the DFG (project KONDISK IMMA; ref.no. Be ....

....Programming Modeling [3, 4] and, more geared towards reactive systems, the Cleanroom Reference model (CRM, 30] The bene t of models is particularly acknowledged in the Rational Uni ed Process [20] and the CRM. The embedding of model based testing in incremental processes is discussed in [27]. A theory of formal testing is tackled in [16, 5] They share the commonality of de ning an observational congruence ( selection hypotheses ) on systems. Similar relations are used in [32, 31] to compute whether or not a system (model) conforms to its speci cation. We di er from this approach in ....

[Article contains additional citation context not shown here]

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), June 2001. To appear.

No context found.

A. Pretschner, H. Lotzbeyer, and J. Philipps. Model Based Testing in Evolutionary Software Development. In Proc. 11th IEEE Intl. Workshop on Rapid System Prototyping (RSP'01), Monterey, June 2001.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC