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 Tools annual

Global: Zendy Free Plan

Global: Zendy Tools monthly

Global: Zendy Plus monthly

Regression testing activities greatly reduce the risk of faulty softwarerelease. However, the size of the test suites grows throughout the developmentprocess, resulting in time-consuming execution of the test suite and delayedfeedback to the software development team. This has urged the need forapproaches such as test case prioritization (TCP) and test-suite reduction toreach better results in case of limited resources. In this regard, proposingapproaches that use auxiliary sources of data such as bug history can beinteresting. We aim to propose an approach for TCP that takes into account testcase coverage data, bug history, and test case diversification. To evaluatethis approach we study its performance on real-world open-source projects. Thebug history is used to estimate the fault-proneness of source code areas. Thediversification of test cases is preserved by incorporating fault-proneness ona clustering-based approach scheme. The proposed methods are evaluated ondatasets collected from the development history of five real-world projectsincluding 357 versions in total. The experiments show that the proposed methodsare superior to coverage-based TCP methods. The proposed approach shows thatimprovement of coverage-based and fault-proneness-based methods is possible byusing a combination of diversification and fault-proneness incorporation.

Test case prioritization using test case diversification and fault-proneness estimations