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 goal of regression testing is to ensure that the behavior of existingcode is not altered by new program changes. The primary focus of regressiontesting should be on code associated with: a) earlier bug fixes; and b)particular application scenarios considered to be important by the tester.Existing coverage criteria do not enable such focus, e.g., 100% branch coveragedoes not guarantee that a given bug fix is exercised or a given applicationscenario is tested. Therefore, there is a need for a complementary coveragecriterion in which the user can define a test requirement characterizing agiven behavior to be covered as opposed to choosing from a pool of pre-definedand generic program elements. We propose UCov, a user-defined coveragecriterion wherein a test requirement is an execution pattern of programelements and predicates. Our proposed criterion is not meant to replaceexisting criteria, but to complement them as it focuses the testing onimportant code patterns that could go untested otherwise. UCov supports testcase intent verification. For example, following a bug fix, the testing teammay augment the regression suite with the test case that revealed the bug.However, this test case might become obsolete due to code modifications notrelated to the bug. But if an execution pattern characterizing the bug wasdefined by the user, UCov would determine that test case intent verificationfailed. We implemented our methodology for the Java platform and applied itonto two real life case studies. Our implementation comprises the following: 1)an Eclipse plugin allowing the user to easily specify non-trivial testrequirements; 2) the ability of cross referencing test requirements acrosssubsequent versions of a given program; and 3) the ability of checking whetheruser-defined test requirements were satisfied, i.e., test case intentverification.

UCov: a User-Defined Coverage Criterion for Test Case Intent Verification