{'fraction_non_alphanumeric': 0.028353326063249727, 'fraction_numerical': 0.0, 'mean_word_length': 5.079470198675497, '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}}
Test-Goal-Specific Termination Criteria for Evolutionary White-Box Testing by Means of Software Measures

White-box testing is an important test procedure for the early detection of errors during software development. It defines, depending on the coverage criteria selected, test goals, such as, for example, requirements, branches or conditions, which need to be achieved for a complete white-box test. Here, test data generation plays a crucial role, because it defines error-prone test data. A successful approach to automated test data generation is evolutionary white-box testing. It is, however, difficult to define a suitable termination criterion for evolutionary white-box testing. This is because it is not known whether the program structure itself is not executable or whether the search for test data was not thorough enough if one of the program structures required by the sub-criterion is not achieved.