English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

The use of asserts in code has received increasing attention in the softwareengineering community in the past few years, even though it has been arecognized programming construct for many decades. A previous empirical studyby Casalnuovo showed that methods containing asserts had fewer defects thanthose that did not. In this paper, we analyze the test classes of twoindustrial telecom Java systems to lend support to, or refute that finding. Wealso analyze the physical position of asserts in methods to determine if thereis a relationship between assert placement and method defect-proneness.Finally, we explore the role of test method size and the relationship it haswith asserts. In terms of the previous study by Casalnuovo, we found onlylimited evidence to support the earlier results. We did however find thatdefective methods with one assert tended to be located at significantly lowerlevels of the class position-wise than non-defective methods. Finally, methodsize seemed to correlate strongly with asserts, but surprisingly less so whenwe excluded methods with just one assert. The work described highlights theneed for more studies into this aspect of code, one which has strong links withcode comprehension.

Assert Use and Defectiveness in Industrial Code