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

Many software engineering techniques, such as fault localization, operatebased on relevance relationships between tests and code. These relationshipsare often inferred through the use of dynamic test execution information (testexecution traces) that approximate the link between relevant code units andasserted, by the tests, program behaviour. Unfortunately, in practice dynamicinformation is not always available due to the overheads introduced by theinstrumentation or the nature of the production environments. To deal with thisissue, we propose CEMENT, a static technique that automatically infers suchtest and code relationships given the projects' evolution. The key idea is thatdevelopers make relevant changes on test and code units at the same period oftime, i.e., co-evolution of tests and code units reflects a probable linkbetween them. We evaluate CEMENT on 15 open source projects and show that itindeed captures relevant links. Additionally, we perform a fault localizationcase study where we compare CEMENT with an existing Information Retrieval-basedFault Localization (IRFL) technique and show that it achieves comparableperformance. A further analysis of our results reveals a small overlap betweenthe faults successfully localized by the two approaches suggestingcomplementarity. In particular, out of the 39 successfully localized faults,two are common while CEMENT and IRFL localize 16 and 21. These resultsdemonstrate that test and code evolutionary coupling can effectively supporttest and debugging activities.

Using Evolutionary Coupling to Establish Relevance Links Between Tests and Code Units. A case study on fault localization