An evaluation of software test environment architectures

Eickelmann, Nancy; Richardson, Debra J.

doi:10.1109/icse.1996.493430

Cited by 27 publications

(42 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…5 Program-point assertions: The program points considered are the places in a program in which a new literal may be added, i.e., before the first literal (if any) of a clause, between two literals, and after the last literal (if any) of a clause. Program-point assertions are literals appearing at the corresponding program point and which are of the form: check(state-formula ).…”

Section: The Ciao Assertion Languagementioning

confidence: 99%

See 1 more Smart Citation

Integrating Software Testing and Run-Time Checking in an Assertion Verification Framework

2009

View full text Add to dashboard Cite

Abstract. We present a framework that unifies unit testing and runtime verification (as well as static verification and static debugging). A key contribution of our overall approach is that we preserve the use of a unified assertion language for all of these tasks. We first describe a method for compiling run-time checks for (parts of) assertions which cannot be verified at compile-time via program transformation. This transformation allows checking preconditions and postconditions, including conditional postconditions, properties at arbitrary program points, and certain computational properties. Most importantly, we propose a minimal addition to the assertion language which allows defining unit tests to be run in order to detect possible violations of the (partial) specifications expressed by the assertions. We have implemented the framework within the Ciao/CiaoPP system and effectively applied it to the verification of ISO Prolog compliance and to the detection of different types of bugs in the Ciao system source code. Experimental results are presented that illustrate different trade-offs among program size, running time, or levels of verbosity of the messages shown to the user.

show abstract

Section: The Ciao Assertion Languagementioning

confidence: 99%

“…With respect to testing, we propose a minimal extension to the assertion language in order to be able to define unit tests [5]. The resulting language can express for example the input data for performing such unit tests, the expected output, the number of times that the unit tests should be repeated, etc.…”

Section: Introductionmentioning

confidence: 99%

Integrating Software Testing and Run-Time Checking in an Assertion Verification Framework

2009

View full text Add to dashboard Cite

show abstract

“…Thus, Proteum/AJ and other derived tools have been also made available under a license for OSS. Proteum/AJ will be available soon as OSS 14 .…”

Section: B Using Reftestmentioning

confidence: 99%

“…Considering their significant relevance, diverse application domains have proposed and used these architectures. Examples of domains with consolidated reference architectures are embedded software [7], [15], [44], software engineering tools [14], [38], [41], web browsers [27] and computer games [12]. Other examples of reference architectures are found in [2], [45].…”

Section: Introductionmentioning

confidence: 99%

Towards the Open Source Reference Architectures

Nakagawa

Maldonado

2011

2011 Fifth Brazilian Symposium on Software Components, Architectures and Reuse

View full text Add to dashboard Cite

Software architectures have received increasing attention by playing a significant role in determining the success and quality of software systems. In particular, reference architecture is a special type of architecture that captures the essence of software systems of a specific domain, achieving therefore well-recognized understanding of that domain. In spite of this, it is not observed concern in order to widely disseminate reference architectures and, as a consequence, the knowledge encompassed by these architectures. At the same time, Open Source Software (OSS) has been largely developed and used in both academy and industry. A diversity of OSS has been made available and has contributed to the software development through dissemination of knowledge that is encompassed mainly in the source code. Specifically, its success is due to OSS licences that have adequately supported its development and evolution. Thus, applying this same idea in order to disseminate reference architectures seems to be very interesting. The main contribution of this paper is to propose Open Source Reference Architecture (OSRA) that, based on principles of OSS, aims at promoting dissemination and evolution of reference architectures, intending to contribute to a more effective software development.

show abstract

“…The area of test management tools is surprisingly scarce in research papers, as vivid as it is in usage, especially during the latest decade, e.g. [10]. The common view is that test management is either a result of automating the test process [9] or a consequence of test execution automation [11].…”

Section: Related Workmentioning

confidence: 99%

Towards Fully Automated Test Management for Large Complex Systems

Eldh

Brandt

Street

et al. 2010

2010 Third International Conference on Software Testing, Verification and Validation

View full text Add to dashboard Cite

Development of large and complex software intensive systems with continuous builds typically generates large volumes of information with complex patterns and relations. Systematic and automated approaches are needed for efficient handling of such large quantities of data in a comprehensible way.In this paper we present an approach and tool enabling autonomous behavior in an automated test management tool to gain efficiency in concurrent software development and test. By capturing the required quality criteria in the test specifications and automating the test execution, test management can potentially be performed to a great extent without manual intervention.This work contributes towards a more autonomous behavior within a distributed remote test strategy based on metrics for decision making in automated testing. These metrics optimize management of fault corrections and retest, giving consideration to the impact of the identified weaknesses, such as fault-prone areas in software.

show abstract

An evaluation of software test environment architectures

Cited by 27 publications

References 12 publications

Integrating Software Testing and Run-Time Checking in an Assertion Verification Framework

Integrating Software Testing and Run-Time Checking in an Assertion Verification Framework

Towards the Open Source Reference Architectures

Towards Fully Automated Test Management for Large Complex Systems

Contact Info

Product

Resources

About