{'fraction_non_alphanumeric': 0.01684836471754212, 'fraction_numerical': 0.0, 'mean_word_length': 4.906432748538012, '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}}
Design of a test plan and its test cases for a translator

Conventional quality control techniques are used to develop an acceptance test plan can not be applied directly to software systems because software characteristics are different from those of the hardware product. A modified method is proposed here which consists of designing two different acceptance test plans. For the test plan design, it is assumed that all obvious errors in the translator were removed by the translator writers during the design, test, and module integration phases of development. The translator is then passed to a testing group consisting of a number of wellexperienced programmmers and headed by a senior software engineer. The test group needs to design a test plan, to write or to generate the test cases (programs), to conduct all testing processes, and to analyze the test results. this group will report acceptance, or, if the results are uncertain, will test the translator again with a different set of test cases.