ACM Home Page
Please provide us with feedback. Feedback
jRapture: A Capture/Replay tool for observation-based testing
Full text PdfPdf (404 KB)
Source International Symposium on Software Testing and Analysis archive
Proceedings of the 2000 ACM SIGSOFT international symposium on Software testing and analysis table of contents
Portland, Oregon, United States
Pages: 158 - 167  
Year of Publication: 2000
ISBN:1-58113-266-2
Also published in ...
Authors
John Steven  Electrical Eng. & Computer Science Dept., Case Western Reserve Univ., Cleveland, OH
Pravir Chandra  Electrical Eng. & Computer Science Dept., Case Western Reserve Univ., Cleveland, OH
Bob Fleck  Electrical Eng. & Computer Science Dept., Case Western Reserve Univ., Cleveland, OH
Andy Podgurski  Electrical Eng. & Computer Science Dept., Case Western Reserve Univ., Cleveland, OH
Sponsor
SIGSOFT: ACM Special Interest Group on Software Engineering
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 12,   Downloads (12 Months): 92,   Citation Count: 10
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues   peer to peer  

Tools and Actions: Review this Article  
Save this Article to a Binder    Display Formats: BibTex  EndNote ACM Ref   
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/347324.348993
What is a DOI?

ABSTRACT

We describe the design of jRapture: a tool for capturing and replaying Java program executions in the field. jRapture works with Java binaries (byte code) and any compliant implementation of the Java virtual machine. It employs a lightweight, transparent capture process that permits unobtrusive capture of a Java programs executions. jRapture captures interactions between a Java program and the system, including GUI, file, and console inputs, among other types, and on replay it presents each thread with exactly the same input sequence it saw during capture. In addition, jRapture has a profiling interface that permits a Java program to be instrumented for profiling ó after its executions have been captured. Using an XML-based profiling specification language a tester can specify various forms of profiling to be carried out during replay.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

1
 
2
Full Circle Software. Talkback, 2000. Available at http://www.fullcircle.com.
3
 
4
IBM alphaWorks. CFParse, 1999. Available at http://alphaworks.ibm.com/tech/cfparse.
 
5
Java 2 SDK, Standard Edition Documentation, Sun Microsystems Inc., 1995-2000.
6
 
7
 
8
 
9
10
11
12
13
 
14
Sun Microsystems, Inc. Java Project X Technology. Release 2. http://developer.java.sun.com/developer/ products/xml.

CITED BY  10
 
 
 
 

Collaborative Colleagues:
John Steven: colleagues
Pravir Chandra: colleagues
Bob Fleck: colleagues
Andy Podgurski: colleagues

Peer to Peer - Readers of this Article have also read: