{'fraction_non_alphanumeric': 0.012411347517730497, 'fraction_numerical': 0.0, 'mean_word_length': 5.647058823529412, '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}}
Allegations as aids to static program testing

In static program analysis, a program is examined without execution in an attempt to anticipate possible sources of error. Possible errors detected in this way can rarely be considered certain to occur because of the impossibility of infallibly determining the executability of a given program path. Current heuristic systems for making this determination are costly and uncertain. Hence the use of allegations—user supplied unverifiable statements designed to provide answers to executability questions—is suggested.