{'fraction_non_alphanumeric': 0.016722408026755852, 'fraction_numerical': 0.0, 'mean_word_length': 4.99, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Augmenting data flow criteria for class testing

A class is widely considered the basic unit of testing in object-oriented software. Although there has been much recent research on class testing, little attention has been paid to code-based class testing criteria. In this paper, we extend the traditional data flow testing techniques and propose three new code-based class testing criteria. These new criteria help overcome the problems associated with existing data flow techniques. We also show that each of the new criteria is stricter than its traditional counterpart in the subsume hierarchy.