{'fraction_non_alphanumeric': 0.013852813852813853, 'fraction_numerical': 0.0, 'mean_word_length': 5.4222222222222225, '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}}
Combining UML Interaction Diagrams and State-Charts for Testing of Object Oriented Software Systems

Successful integration of classes results in correct functioning of object-oriented software. It can be possible that individual classes may function correctly but several new faults can emerge when these independent classes are integrated together. Typically, the complexity of an OO system lies in its object interactions, not within class methods which tend to be small and simple. As a result, complex behaviors are observed when related classes are integrated and several kinds of faults can arise during integration: interface faults, conflicting functions, and missing functions. Thus testing each class independently does not eliminate the need for integration testing. A large number of possible interactions between interacting classes may need to be tested to ensure the correct functionality of the system. We present a technique that enhances the integration testing of classes by accounting for all possible states of interacting classes. This is important as interactions may trigger correct behavior for certain states and not for others.