No more “No Repro’s”

Pinpoint Root Cause Analysis.

Because Replay Recordings re-execute the original binaries to create a live debugging session, all the techniques that developers use to locate a problem are available: breakpoints, memory status, exceptions, etc. Because the code is re-executing it is also possible to increase the logging level beyond the originally generated logs for finer grained, more detailed debug information. The ability to recreate a defect with 100% precision means that non-reproducible bugs are a thing of the past.

Typical Use Case:

A major Independent Software Vendor utilizes Eclipse as their standard IDE. Developers will pull up a recording in Eclipse using the Replay Plug-in designed for that purpose and execute the code while seeing the corresponding source code statements, variable values, threads, stack traces, etc. necessary to diagnose a problem. Because Replay can generate “markers” during recording to pinpoint where issues occur, the developer can use them to directly navigate to the part of the code that exhibited a problem.

“The ping-pong between QA and Dev over tough to reproduce bugs used to eat up days of valuable test and coding resources. With ReplayDIRECTOR, we don’t hear “It works on my machine” and we no longer accept shipping production code with non-reproducible bugs.”
Quotes:
“Play back the recording in the regular Eclipse Java debugger as often as you like to figure out the problem.” - Stephen Smith - VP R&D - Sage Software
“Play back the recording in the regular Eclipse Java debugger as often as you like to figure out the problem.” - Stephen Smith - VP R&D - Sage Software
“The problem was un-reproducible. Without Replay, we wouldn’t have had a chance at fixing it.” - John W. - Sr. Software Engineer
“The problem was un-reproducible. Without Replay, we wouldn’t have had a chance at fixing it.” - John W. - Sr. Software Engineer
Take the ReplayDIRECTOR 3 Minute Tour:
Solutions:
ReplayDIRECTOR Developer Edition
ReplayDIRECTOR Developer Edition