Automated Fault Localization

Masri, Wes

doi:10.1016/bs.adcom.2015.05.001

Cited by 10 publications

(4 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Therefore, we expect that slightly unsafe code refactoring techniques to remove the tracking code may be promising in effectively preserving functionality while preventing tracking. Future tracking code identification techniques can greatly benefit from recent advances in automated debugging and fault localization [41,55]. For example, given filter list as a test oracle, we can adapt search-based debugging approaches to perform a systematic search on JS code and precisely isolate the tracking and functional code units [58].…”

Section: Discussionmentioning

confidence: 99%

Blocking JavaScript Without Breaking the Web: An Empirical Investigation

Amjad

Shafiq

Gulzar

2023

PoPETs

View full text Add to dashboard Cite

Modern websites heavily rely on JavaScript (JS) to implement legitimate functionality as well as privacy-invasive advertising and tracking. Browser extensions such as NoScript block any script not loaded by a trusted list of endpoints, thus hoping to block privacy-invasive scripts while avoiding breaking legitimate website functionality. In this paper, we investigate whether blocking JS on the web is feasible without breaking legitimate functionality. To this end, we conduct a large-scale measurement study of JS blocking on 100K websites. We evaluate the effectiveness of different JS blocking strategies in tracking prevention and functionality breakage. Our evaluation relies on quantitative analysis of network requests and resource loads as well as manual qualitative analysis of visual breakage. First, we show that while blocking all scripts is quite effective at reducing tracking, it significantly degrades functionality on approximately two-thirds of the tested websites. Second, we show that selective blocking of a subset of scripts based on a curated list achieves a better trade-off. However, there remain approximately 15% “mixed” scripts, which essentially merge tracking and legitimate functionality and thus cannot be blocked without causing website breakage. Finally, we show that fine-grained blocking of a subset of JS methods, instead of scripts, reduces major breakage by 3.8× while providing the same level of tracking prevention. Our work highlights the promise and open challenges in fine-grained JS blocking for tracking prevention without breaking the web.

show abstract

Section: Discussionmentioning

confidence: 99%

Blocking JavaScript Without Breaking the Web: An Empirical Investigation

Amjad

Shafiq

Gulzar

2023

PoPETs

View full text Add to dashboard Cite

show abstract

“…Causal inference FL techniques intend to improve SBFL effectiveness by considering the call and data-dependency graphs of test runs. This subset of techniques considers the causal relationship between method coverage and test results [118]. The first causal-based technique was proposed by Baah et al in [7].…”

Section: Method-level Fault Localization With Causal Inferencementioning

confidence: 99%

“…This might be the consequence of considering the correlation, not causation. Although the goal of any FL technique is "to identify the code that caused the failure and not just any code that correlated with it" [118], SBFL techniques measure the correlation between program elements and test failures to compute suspiciousness scores. Thus, they do not control potential confounding bias [138].…”

Section: Introductionmentioning

confidence: 99%

A Framework for Failure Diagnosis

Golagha

2017

2017 IEEE International Conference on Software Testing, Verification and Validation (ICST)

View full text Add to dashboard Cite

Undertaking this Ph.D. has been a truly life-changing experience for me, and it would not have been possible to do without the support and guidance that I received from many people, and I would not forget to thank them. My Supervisor: Alex, you decided to trust your instinct. Your decision changed a lot of things in my life. I worked hard to prove your instinct was right. Throughout this journey, under your supervision, I grew and became the woman I am today. Thank you for helping me understanding my strengths and weaknesses, teaching me how to accept them and how to use them. Thank you for showing me how to admit and say sorry when I am wrong, how to argue and convince when I am right, and how to confidently say "I don't know but I'll find out". I learned more than you know from you. I am more than grateful. My second supervisor: Lionel, I would like to express my sincere gratitude. Thank you for hosting me at SnT center and providing useful and actionable feedback. I was inspired by many of your previous works. My short stay with your research group and interactions with colleagues there provided me new insight.

show abstract

“…Future tracking code identification techniques can greatly benefit from recent advances in automated debugging and fault localization [42,59]. For example, given filter list as a test oracle, we can adapt search-based debugging approaches to perform a systematic search on JS code and precisely isolate the tracking and functional code units [62].…”

Section: Js Dataflow Analysismentioning

confidence: 99%

Blocking JavaScript without Breaking the Web: An Empirical Investigation

Amjad¹,

Shafiq²,

Gulzar³

2023

Preprint

View full text Add to dashboard Cite

Modern websites heavily rely on JavaScript (JS) to implement legitimate functionality as well as privacy-invasive advertising and tracking. Browser extensions such as NoScript block any script not loaded by a trusted list of endpoints, thus hoping to block privacy-invasive scripts while avoiding breaking legitimate website functionality. In this paper, we investigate whether blocking JS on the web is feasible without breaking legitimate functionality. To this end, we conduct a large-scale measurement study of JS blocking on 100K websites. We evaluate the effectiveness of different JS blocking strategies in tracking prevention and functionality breakage. Our evaluation relies on quantitative analysis of network requests, and resource loads as well as manual qualitative analysis of visual breakage. First, we show that while blocking all scripts is quite effective at reducing tracking, it significantly degrades functionality on approximately two-thirds of the tested websites. Second, we show that selective blocking of a subset of scripts based on a curated list achieves a better tradeoff. However, there remain approximately 15% "mixed" scripts, which essentially merge tracking and legitimate functionality and thus cannot be blocked without causing website breakage. Finally, we show that fine-grained blocking of a subset of JS methods, instead of scripts, reduces major breakage by 3.7× while providing the same level of tracking prevention. Our work highlights the promise and open challenges in fine-grained JS blocking for tracking prevention without breaking the web.

show abstract

Automated Fault Localization

Cited by 10 publications

References 28 publications

Blocking JavaScript Without Breaking the Web: An Empirical Investigation

Blocking JavaScript Without Breaking the Web: An Empirical Investigation

A Framework for Failure Diagnosis

Blocking JavaScript without Breaking the Web: An Empirical Investigation

Contact Info

Product

Resources

About