{'fraction_non_alphanumeric': 0.015736766809728183, 'fraction_numerical': 0.0, 'mean_word_length': 4.932203389830509, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 1, '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}}
Efficient Regression Tests for Database Applications

If you browse through the articles of www.junit.org, you will find only one article that contains the word database in its abstract. This observation is shocking because, of course, testing is just as important for database applications as for any other application. The sad truth is that JUnit simply does not work for database applications, and there are no alternatives on the market place. The reason is that there are some fundamental issues in automatizing regression tests for database applications. This paper addresses one particular issue that arises from the fact that you change the state of a database application while you test it.