Testing class libraries for RTSJ safety

Authors:
Michael Dawson;Paul Thwaite
Affiliations:
IBM, Ottawa, Ontario, Canada;IBM, Winchester, UK
Venue:
JTRES '08 Proceedings of the 6th international workshop on Java technologies for real-time and embedded systems
Year:
2008

Citing 3
Cited 1

Design and implementation of a comprehensive real-time java virtual machine

EMSOFT '07 Proceedings of the 7th ACM & IEEE international conference on Embedded software
Challenges in Implementing the Real-Time Specification for Java (RTSJ) in a Commercial Real-Time Java Virtual Machine

ISORC '08 Proceedings of the 2008 11th IEEE Symposium on Object Oriented Real-Time Distributed Computing
Toward Libraries for Real-Time Java

ISORC '08 Proceedings of the 2008 11th IEEE Symposium on Object Oriented Real-Time Distributed Computing

Reflexes: Abstractions for integrating highly responsive tasks into Java applications

ACM Transactions on Embedded Computing Systems (TECS)

Quantified Score

Hi-index	0.00

Visualization

Abstract

The addition of new thread types and new memory areas by the Real-Time Specification for Java™ (RTSJ) [1] introduces new failure modes for existing class libraries. Existing tests for these class libraries will not cover execution with RTs, NHRTs and with the Immortal and Scoped memory areas. Writing new tests to cover these new cases can take significant time and effort. This paper introduces an approach we call AutoRTUnit that allows us to get test coverage for the new thread types and memory areas by reusing existing JUnit[2] based unit tests. In our case we applied it to expand our test coverage for a subset of the non-RTSJ APIs within our RTSJ-compliant Java virtual machine (JVM).