
- What is ReplayDIRECTOR™ ?
- How is ReplayDIRECTOR™ different from a video capture?
- How does it work?
- How will using ReplayDIRECTOR™ affect my performance?
- Do I need to change or add to my source code?
- How much data does ReplayDIRECTOR™ store when recording?
- Will ReplayDIRECTOR™ reproduce multi-user and networked bugs?
- Can I debug recordings?
- What platforms are supported?
- Do I need to recreate the environment in order to replay?
- How do I share a recorded session with my team?
- Will this replace my existing QA tools?
- Can I evaluate a Trial Version of ReplayDIRECTOR™ using my software?
1. What is ReplayDIRECTOR™?
ReplayDIRECTOR™ is a software debugging tool that gives
VCR, or DVR-like functionality to any software.
As you are running your software, ReplayDIRECTOR™ is
transparently recording every line of code that is executed.
This results in a perfect recording of your software. If you
find a bug, you can simply press play to see it again.
2. How is ReplayDIRECTOR™ different from a video or screen capture?
ReplayDIRECTOR™ is recording your program, not
the video or screen output. Every line of code that your program
executes will be recorded, and will playback exactly the same.
When you playback a recording, your software is running. This
means any bug that occurred during the recording will be
reproduced perfectly when you playback.
3. How does it work?
ReplayDIRECTOR™ is a 'binary instrumentation tool'. When
installed, it analyzes the compiled binaries of your application
and identifies everything that must be recorded in order to
create a perfect recording of your software.
Every potential source of non-determinism is captured and
recorded for later playback. Although this is an intensive
process, it takes under 10 seconds to complete.
4. How will using ReplayDIRECTOR™ affect my performance?
ReplayDIRECTOR™ is a high-performance system that has almost no
impact on performance. Replay is designed to be seamless and
transparent. This means you can be recording all the
time, even during production with software in-the-field
with customers.
With 'always-on' recording, if you, or your customer ever finds
a bug, you will never have to worry about reproducing it.
5. Do I need to change or add to my source code?
No, ReplayDIRECTOR™ does not require any changes to your application code
6. How much data does ReplayDIRECTOR™ store when recording?
The recorded session size varies by the nature of the application. A recording of an application that queries a database and receives a large dataset in response will be larger than a recording of simple web browsing.
7. Will ReplayDIRECTOR™ reproduce multi-user and networked bugs?
Yes! Recordings made of online software applications can be
Replayed at anytime, even without a network connection.
This means you can record internet applications with many users,
then playback that recording perfectly with all of the network
data, timings, asynchronous network input and all other
non-deterministic events occuring exactly as they were recorded.
8. Can I debug recordings?
Absolutely. When you playback a recording, the software will be
running. You can playback recordings from the debugger, or
attach a debugger to a playback already in progress. All
of your symbols will be valid in the debugger.
You can set breakpoints, single-step through code, and inspect
data. Your software is running just as it did when you recorded
it.
9. What platforms are supported?
ReplayDIRECTOR™ supports widely used Java application servers, including Tomcat and WebLogic.
10. Do I need to recreate the environment in which the problem was recorded in order to replay it?
No. Since ReplayDIRECTOR™ records every potential source of non-determinism in your application, it feeds the recorded data back to your application during playback in the correct sequence. The result is a perfect, line-for-line playback execution of the software you have recorded, without the need to reproduce the original environment.
11. How do I share a recorded session with my team?
Sharing of recordings between QA personnel and developers is seamless. All recorded sessions can be viewed in through the ReplayDIRECTOR™ Server. From the server’s dashboard, you can search for particular recordings, or filter just those that contain issues, and replay them.
12. Will this replace my existing QA tools?
No, ReplayDIRECTOR™ is not a substitute for load testing tools or regression testing tools, but complements them. You can have ReplayDIRECTOR™ recording while you run your functional tests, or as you stress-test your application under load, to capture the difficult to reproduce bugs that these tools uncover. Later, you can debug your application using your standard debugger or profiler, without the need to rerun the testing tools.
13. Can I evaluate a Trial Version of ReplayDIRECTOR™ using my software?
Yes, absolutely. If you would like to try ReplayDIRECTOR™ with your software, please get in touch with
us to arrange your evaluation.
Have a question that you don't see answered here? Please ask us.


