{'fraction_non_alphanumeric': 0.01903367496339678, 'fraction_numerical': 0.0, 'mean_word_length': 5.075555555555556, '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}}
Continuous integration processes for modern client-side web applications

Continuous Integration (CI) is very useful for applications that involve many files and multiple developers. Unfortunately, not all types of applications can easily apply this approach. Apparently, CI does not gain a lot of attention with Modern Client-Side Web Application (MCSWA) because it requires complicated testing, i.e. the running environments are browsers. There is no compiler or error warning when a developer writes bad code and the build behavior in the usual CI practice is different from the build process in MCSWA. If the integration process is done manually by an integration expert, unexpected errors are found not only while integrating but also when performing manual tests to verify it. Moreover, it is problematic and elaborate if a developer needs to test the features by clicking around with repeated user-interaction in different browsers; especially, he might create human errors or miss some steps. This indicates that manual processes consume a lot of time and they are stressful. Therefore, the intent of this paper is to demonstrate a new approach for a CI process which specifically applies to MCSWA. It also provides a precise cycle for web development teams on how these repeated processes are important to run automatically with effective expected outcomes.