WaRR: A tool for high-fidelity web application record and replay

Andrica, Silviu; Candea, George

doi:10.1109/dsn.2011.5958253

Cited by 62 publications

(28 citation statements)

References 12 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Fuzzing schedules to uncover timing related bugs is a known technique in the domain of concurrent programs, for example, as done by Sen [29], Narayanasamy et al [24] for Java applications, Andrica and Candea [2], and the WAVE tool by Hong et al [12] for web applications. A central challenge for each of these tools is the identification of errors if they occur while fuzzing schedules: Sen [29] detects raised exceptions; Narayanasamy et al [24] and WAVE check if a fuzzed schedule can be executed and lead to the same final state, while Andrica and Candea [2] use manual validation only.…”

Section: Related Workmentioning

confidence: 99%

“…A central challenge for each of these tools is the identification of errors if they occur while fuzzing schedules: Sen [29] detects raised exceptions; Narayanasamy et al [24] and WAVE check if a fuzzed schedule can be executed and lead to the same final state, while Andrica and Candea [2] use manual validation only. However, as discovered by Raychev et al [27], web applications contain many races, hence manually inspecting all of these races is infeasible.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Stateless model checking of event-driven applications

Jensen

Møller

Raychev

et al. 2015

Proceedings of the 2015 ACM SIGPLAN International Conference on Object-Oriented Programming, Systems, Languages, and Applicatio

View full text Add to dashboard Cite

Modern event-driven applications, such as, web pages and mobile apps, rely on asynchrony to ensure smooth end-user experience. Unfortunately, even though these applications are executed by a single event-loop thread, they can still exhibit nondeterministic behaviors depending on the execution order of interfering asynchronous events. As in classic shared-memory concurrency, this nondeterminism makes it challenging to discover errors that manifest only in specific schedules of events.In this work we propose the first stateless model checker for event-driven applications, called R4. Our algorithm systematically explores the nondeterminism in the application and concisely exposes its overall effect, which is useful for bug discovery. The algorithm builds on a combination of three key insights: (i) a dynamic partial order reduction (DPOR) technique for reducing the search space, tailored to the domain of event-driven applications, (ii) conflict-reversal bounding based on a hypothesis that most errors occur with a small number of event reorderings, and (iii) approximate replay of event sequences, which is critical for separating harmless from harmful nondeterminism.We instantiate R4 for the domain of client-side web applications and use it to analyze event interference in a number of real-world programs. The experimental results indicate that the precision and overall exploration capabilities of our system significantly exceed that of existing techniques.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Stateless model checking of event-driven applications

Jensen

Møller

Raychev

et al. 2015

Proceedings of the 2015 ACM SIGPLAN International Conference on Object-Oriented Programming, Systems, Languages, and Applicatio

View full text Add to dashboard Cite

show abstract

“…Capture and Replay. Related to our work are 'capture and replay' techniques for web applications [5,6,16,17,21]. The goal in most of these techniques is to find a deterministic way of replaying the same set of user events for debugging purposes.…”

Section: Related Workmentioning

confidence: 99%

Understanding JavaScript event-based interactions

Alimadadi

Sequeira

Mesbah

et al. 2014

Proceedings of the 36th International Conference on Software Engineering

View full text Add to dashboard Cite

Web applications have become one of the fastest growing types of software systems today. Despite their popularity, understanding the behaviour of modern web applications is still a challenging endeavour for developers during development and maintenance tasks. The challenges mainly stem from the dynamic, event-driven, and asynchronous nature of the JavaScript language. We propose a generic technique for capturing low-level event-based interactions in a web application and mapping those to a higher-level behavioural model. This model is then transformed into an interactive visualization, representing episodes of triggered causal and temporal events, related JavaScript code executions, and their impact on the dynamic DOM state. Our approach, implemented in a tool called Clematis, allows developers to easily understand the complex dynamic behaviour of their application at three di↵erent semantic levels of granularity. The results of our industrial controlled experiment show that Clematis is capable of improving the task accuracy by 61%, while reducing the task completion time by 47%.

show abstract

“…Then, she sets a breakpoint inside the Bullet.create() method and records and visualizes when it is actually hit during the execution using the breakpoint radar feature (Figure 3-3a). Breakpoint radar automates the process of replaying the execution, pausing and resuming at each hit, and visualizing when (1). A blue cursor (2) indicates that replay execution is paused at a breakpoint, instead of between user inputs (as shown in Figure 2).…”

Section: Navigation Aid: Breakpoint Radarmentioning

confidence: 99%

“…Dolos and Timelapse are free software: our source code, study materials, and data are available on the project website 1 .…”

Section: Introductionmentioning

confidence: 99%

Interactive record/replay for web application debugging

Burg

Bailey

et al. 2013

Proceedings of the 26th Annual ACM Symposium on User Interface Software and Technology

113

View full text Add to dashboard Cite

During debugging, a developer must repeatedly and manually reproduce faulty behaviors in order to inspect different facets of the program's execution. Existing tools for reproducing such behaviors prevent the use of debugging aids such as breakpoints and logging, and are not designed for interactive, random-access exploration of recorded behavior. This paper presents Timelapse, a tool for quickly recording, reproducing, and debugging interactive behaviors in web applications. Developers can use Timelapse to browse, visualize, and seek within recorded program executions while simultaneously using familiar debugging tools such as breakpoints and logging. Testers and end-users can use Timelapse to demonstrate failures in situ and share recorded behaviors with developers, improving bug report quality by obviating the need for detailed reproduction steps. Timelapse is built on Dolos, a novel record/replay infrastructure that ensures deterministic execution by capturing and reusing program inputs both from the user and from external sources such as the network. Dolos introduces negligible overhead and does not interfere with breakpoints and logging. In a small user evaluation, participants used Timelapse to accelerate existing reproduction activities, but were not significantly faster or more successful in completing the larger tasks at hand. Together, the Dolos infrastructure and Timelapse developer tool support systematic bug reporting and debugging practices.

show abstract

WaRR: A tool for high-fidelity web application record and replay

Cited by 62 publications

References 12 publications

Stateless model checking of event-driven applications

Stateless model checking of event-driven applications

Understanding JavaScript event-based interactions

Interactive record/replay for web application debugging

Contact Info

Product

Resources

About