Refactoring Legacy JavaScript Code to Use Classes: The Good, The Bad and The Ugly

Silva, Leonardo Humberto; Valente, M.; Bergel, Alexandre

doi:10.1007/978-3-319-56856-0_11

Cited by 7 publications

(7 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In particular, until ECMAScript 2015, JavaScript did not include syntactical support for classes. Classes were emulated using functions as constructors, and methods/fields are added to their prototype [46,47,48]. In addition, object literals could represent imaginary classes: comma-separated list of name-value pairs enclosed in curly braces, where the name-value pairs declare the class fields/methods.…”

Section: B Patterns In Bugs and Fixesmentioning

confidence: 99%

BugsJS: a Benchmark of JavaScript Bugs

Gyimesi

Vancsics

Stocco

et al. 2019

2019 12th IEEE Conference on Software Testing, Validation and Verification (ICST)

View full text Add to dashboard Cite

JavaScript is a popular programming language that is also error-prone due to its asynchronous, dynamic, and loosely-typed nature. In recent years, numerous techniques have been proposed for analyzing and testing JavaScript applications. However, our survey of the literature in this area revealed that the proposed techniques are often evaluated on different datasets of programs and bugs. The lack of a commonly used benchmark limits the ability to perform fair and unbiased comparisons for assessing the efficacy of new techniques. To fill this gap, we propose BUGSJS, a benchmark of 453 real, manually validated JavaScript bugs from 10 popular JavaScript server-side programs, comprising 444k LOC in total. Each bug is accompanied by its bug report, the test cases that detect it, as well as the patch that fixes it. BUGSJS features a rich interface for accessing the faulty and fixed versions of the programs and executing the corresponding test cases, which facilitates conducting highly-reproducible empirical studies and comparisons of JavaScript analysis and testing tools.

show abstract

Section: B Patterns In Bugs and Fixesmentioning

confidence: 99%

BugsJS: a Benchmark of JavaScript Bugs

Gyimesi

Vancsics

Stocco

et al. 2019

2019 12th IEEE Conference on Software Testing, Validation and Verification (ICST)

View full text Add to dashboard Cite

show abstract

“…The identification of classes and their dependencies in legacy JavaScript is studied in [34,35]. Extensions of these works provide migration rules for their refactoring towards using ES6 classes [36,37]. Paltoglou et al [38] propose a static analysis technique for refactoring nonmodular ES5 web applications towards ES6 modules.…”

Section: Related Workmentioning

confidence: 99%

“…Our work handles concerns related to code migration to a newer language version, as well as to the improvement of its internal quality attributes. As compared to earlier work on refactoring legacy ES5 code to the ES6 class syntax [36,37], our work is complementary and a basic requirement for its application. The reason is that migration to ES6 modularity is a prerequisite for further application of migrations that incorporate modern language features to a code-base.…”

Section: Related Workmentioning

confidence: 99%

Automated Refactoring of Legacy JavaScript Code to ES6 Modules

Paltoglou,

Zafeiris,

Diamantidis

et al. 2021

Preprint

View full text Add to dashboard Cite

The JavaScript language did not specify, until ECMAScript 6 (ES6), native features for streamlining encapsulation and modularity. Developer community filled the gap with a proliferation of design patterns and module formats, with impact on code reusability, portability and complexity of build configurations. This work studies the automated refactoring of legacy ES5 code to ES6 modules with fine-grained reuse of module contents through the named import/export language constructs. The focus is on reducing the coupling of refactored modules through destructuring exported module objects to fine-grained module features and enhancing module dependencies by leveraging the ES6 syntax. We employ static analysis to construct a model of a JavaScript project, the Module Dependence Graph (MDG), that represents modules and their dependencies. On the basis of MDG we specify the refactoring procedure for module migration to ES6. A prototype implementation has been empirically evaluated on 19 open source projects. Results highlight the relevance of the refactoring with a developer intent for fine-grained reuse. The analysis of refactored code shows an increase in the number of reusable elements per project and reduction in the coupling of refactored modules. The soundness of the refactoring is empirically validated through code inspection and execution of projects' test suites.

show abstract

“…In particular, until ECMAScript 2015, JS did not include syntactical support for classes. Classes were emulated using functions as constructors, and methods/fields are added to their prototype [51][52][53]. In addition, object literals could represent imaginary classes: comma-separated list of name-value pairs enclosed in curly braces, where the name-value pairs declare the class fields/methods.…”

Section: Of 38 Bugsjs: a Bencmark And Taxamony Of Javascript Bugsmentioning

confidence: 99%

BUGSJS: a benchmark and taxonomy of JavaScript bugs

Gyimesi

Vancsics

Stocco

et al. 2020

Software Testing Verif & Rel

View full text Add to dashboard Cite

JavaScript is a popular programming language that is also error-prone due to its asynchronous, dynamic, and loosely typed nature. In recent years, numerous techniques have been proposed for analyzing and testing JavaScript applications. However, our survey of the literature in this area revealed that the proposed techniques are often evaluated on different datasets of programs and bugs. The lack of a commonly used benchmark limits the ability to perform fair and unbiased comparisons for assessing the efficacy of new techniques. To fill this gap, we propose BUGSJS, a benchmark of 453 real, manually validated JavaScript bugs from 10 popular JavaScript server-side programs, comprising 444k lines of code (LOC) in total. Each bug is accompanied by its bug report, the test cases that expose it, as well as the patch that fixes it. We extended BUGSJS with a rich web interface for visualizing and dissecting the bugs' information, as well as a programmable API to access the faulty and fixed versions of the programs and to execute the corresponding test cases, which facilitates conducting highly reproducible empirical studies and comparisons of JavaScript analysis and testing tools. Moreover, following a rigorous procedure, we performed a classification of the bugs according to their nature. Our internal validation shows that our taxonomy is adequate for characterizing the bugs in BUGSJS. We discuss several ways in which the resulting taxonomy and the benchmark can help direct researchers interested in automated testing of JavaScript applications.

show abstract

Refactoring Legacy JavaScript Code to Use Classes: The Good, The Bad and The Ugly

Cited by 7 publications

References 18 publications

BugsJS: a Benchmark of JavaScript Bugs

BugsJS: a Benchmark of JavaScript Bugs

Automated Refactoring of Legacy JavaScript Code to ES6 Modules

BUGSJS: a benchmark and taxonomy of JavaScript bugs

Contact Info

Product

Resources

About