JSNOSE: Detecting JavaScript Code Smells

Fard, Amin Milani; Mesbah, Ali

doi:10.1109/scam.2013.6648192

Cited by 99 publications

(64 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Some of them even focused on web technologies, such as bad practices in CSS (Mesbah and Mirshokraie 2012), Javascript (Silva et al 2015;Fard and Mesbah 2013), and HTML (Nederlof et al 2014). However, to the best of our knowledge, no research has focused on code smells for server-side MVC Web applications.…”

Section: Related Workmentioning

confidence: 99%

Code smells for Model-View-Controller architectures

et al. 2017

View full text Add to dashboard Cite

Previous studies have shown the negative effects that low-quality code can have on maintainability proxies, such as code change-and defect-proneness. One of the symptoms of low-quality code are code smells, defined as sub-optimal implementation choices. While this definition is quite general and seems to suggest a wide spectrum of smells that can affect software systems, the research literature mostly focuses on the set of smells defined in the catalog by Fowler and Beck, reporting design issues that can potentially affect any kind of system, regardless of their architecture (e.g., Complex Class). However, systems adopting a specific architecture (e.g., the Model-View-Controller pattern) can be affected by other types of poor practices that only manifest themselves in the chosen architecture. We present a catalog of six smells tailored to MVC applications and defined by surveying/interviewing 53 MVC developers. We validate our catalog from different perspectives. First, we assess the relationship between the defined smells and the code change-and defect-proneness. Second, we investigate when these smells are introduced and how long they survive. Third, we survey 21 developers to verify their perception of the defined smells. Fourth, since our catalog has been mainly defined together with developers adopting a specific Java framework in their MVC applications (e.g., Spring), we interview four expert developers working with different technologies for the implementation of their MVC applications to check the generalizability of our catalog. The achieved results show that the defined Web MVC smells (i) more often than not, have more chances of being subject to changes and defects, (ii) are mostly introduced when the affected file (i.e., the file containing the smell) is committed for the first time in the repository and survive for long time in the system, (iii) are perceived by developers as severe problems, and (iv) generalize to other languages/frameworks.

show abstract

Section: Related Workmentioning

confidence: 99%

Code smells for Model-View-Controller architectures

et al. 2017

View full text Add to dashboard Cite

show abstract

“…Fard and Mesbah [20] proposed a set of 13 JavaScript code smells, including generic smells (e.g., long functions and dead code) and smells specific to JavaScript (e.g., creating closures in loops and accessing this in closures). They also describe a tool, called JSNode, for detecting code smells based on a combination of static and dynamic analysis.…”

Section: Related Workmentioning

confidence: 99%

Does JavaScript software embrace classes?

Silva¹,

Ramos

Valente

et al. 2015

2015 IEEE 22nd International Conference on Software Analysis, Evolution, and Reengineering (SANER)

View full text Add to dashboard Cite

International audienceJavaScript is the de facto programming language for the Web. It is used to implement mail clients, office applications, or IDEs, that can weight hundreds of thousands of lines of code. The language itself is prototype based, but to master the complexity of their application, practitioners commonly rely on some informal class abstractions. This practice has never been the target of empirical investigations in JavaScript. Yet, understanding it would be key to adequately tune programming environments and structure libraries such as they are accessible to programmers. In this paper we report a large and in-depth study to understand how class emulation is employed in JavaScript applications. We propose a strategy to statically detect class-based abstractions in the source code of JavaScript systems. We used this strategy in a dataset of 50 popular JavaScript applications available from GitHub. We found systems structured around hundreds of classes, suggesting that JavaScript developers are standing on traditional class-based abstractions to tackle the growing complexity of their systems

show abstract

“…This has been used to identify JavaScript-specific code smells, and their occurrence [19]. The results indicate that lazy object, long method/function, closure smells, coupling between JavaScript, HTML, and CSS, and excessive global variables are the most prevalent code smells.…”

Section: Software Evolutionmentioning

confidence: 99%

Crawl-based analysis of web applications: Prospects and challenges

Deursen

Mesbah

Nederlof

2015

Science of Computer Programming

Self Cite

View full text Add to dashboard Cite

In this paper we review five years of research in the field of automated crawling and testing of web applications.We describe the open source Crawljax tool, and the various extensions that have been proposed in order to address such issues as cross-browser compatibility testing, web application regression testing, and style sheet usage analysis.Based on that we identify the main challenges and future directions of crawl-based testing of web applications. In particular, we explore ways to reduce the exponential growth of the state space, as well as ways to involve the human tester in the loop, thus reconciling manual exploratory testing and automated test input generation. Finally, we sketch the future of crawl-based testing in the light of upcoming developments, such as the pervasive use of touch devices and mobile computing, and the increasing importance of cyber-security.

show abstract

JSNOSE: Detecting JavaScript Code Smells

Cited by 99 publications

References 10 publications

Code smells for Model-View-Controller architectures

Code smells for Model-View-Controller architectures

Does JavaScript software embrace classes?

Crawl-based analysis of web applications: Prospects and challenges

Contact Info

Product

Resources

About