Changes between Version 3 and Version 4 of path:tutorial:backintime


Ignore:
Timestamp:
01/08/2014 02:35:46 PM (9 years ago)
Author:
michael.perscheid
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • path:tutorial:backintime

    v3 v4  
    55'''Keywords:''' Debugging, Testing,  Back-in-time, Program Comprehension, Dynamic Analysis
    66
     7In contrast to symbolic debuggers, back-in-time debuggers help to understand complete infection chains and to follow failure causes back to their defects.
     8As the reasons for observable failures happened in the past, these debuggers record all run-time information before the failure occurs and then present it afterwards.
     9Developers start with the observable failure, step backward, and search for infections at each point in the program’s execution history.
     10By asking questions about a program’s run-time such as: “Where did the value of a variable change?”, they can develop a deeper understanding of infection chains step by step until it is clear how failures come to be.
     11
     12For the purpose of localizing failure causes, our back-in-time debugger called [wiki:path:pathFinder PathFinder] offers developers access to the entire execution history of a failing test case.
     13Starting with a test case as a reproducible entry point, we record its behavior, present the run-time data in form of an explorable call tree, and so allow developers to follow the infection chain back to its root cause.
     14In doing so, we provide arbitrary navigation through method call trees and their state spaces in both forward and backward direction.
     15We restrict dynamic analysis to partial traces and, primarily, to the granularity level of methods.
     16Apart from common back-in-time features, such as a query engine for getting a deeper understanding of what happened, our approach possesses two distinguishing characteristics.
     17First, our step-wise run-time analysis (see ''more information'' below) allows for immediate access to run-time information of reproducible and deterministic test cases.
     18Second, the integration of anomalies classifies suspicious trace data and so facilitates navigation in large traces (see also [wiki:path:tutorial:tdfn test-driven fault navigation]).
     19
    720== Demonstration ==
    821