Exposing bugs in JavaScript engines through test transplantation and differential testing

Lima, Igor; Silva, Jefferson Lins da; Miranda, Breno; Pinto, Gustavo; d’Amorim, Marcelo

doi:10.1007/s11219-020-09537-8

Cited by 6 publications

(2 citation statements)

References 26 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…JavaScript has been the most commonly used programming language for several years 1 . It is also popular in various application domains, including web (server-side and client-side), mobile, and the Internet of Things (IoT) [19], [20]. In addition, given the nature of the language (handling HTTP requests, running on browsers), JavaScript is known to be one of the languages that uses asynchronous APIs extensively, with an execution model susceptible to races.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

An Empirical Study of Flaky Tests in JavaScript

Hashemi

Tahir

Rasheed

2022

View full text Add to dashboard Cite

Flaky tests (tests with non-deterministic outcomes) can be problematic for testing efficiency and software reliability. Flaky tests in test suites can also significantly delay software releases. There have been several studies that attempt to quantify the impact of test flakiness in different programming languages (e.g., Java and Python) and application domains (e.g., mobile and GUI-based). In this paper, we conduct an empirical study of the state of flaky tests in JavaScript. We investigate two aspects of flaky tests in JavaScript projects: the main causes of flaky tests in these projects and common fixing strategies. By analysing 452 commits from large, top-scoring JavaScript projects from GitHub, we found that flakiness caused by concurrency-related issues (e.g., async wait, race conditions or deadlocks) is the most dominant reason for test flakiness. The other top causes of flaky tests are operating system-specific (e.g., features that work on specific OS or OS versions) and network stability (e.g., internet availability or bad socket management). In terms of how flaky tests are dealt with, the majority of those flaky tests (>80%) are fixed to eliminate flaky behaviour and developers sometimes skip, quarantine or remove flaky tests.

show abstract

Section: Introductionmentioning

confidence: 99%

“…There are 10 commits from the resource leak category. The following example20 from Node.js shows a flaky test due to EMFILE, which means that a process is trying to open too many files.…”

mentioning

confidence: 99%