Software development has increasingly become an activity that is (partially) done online on open-source platforms such as GitHub, and with it, so have the tools developers typically use. One such category of tools is that of code coverage tools. These tools track and report coverage data generated during CI tests. As the adoption of these tools has grown, so does the amount of available coverage data. In this thesis we explore a large database of coverage data from Codecov, a popular coverage tool. What sets our work apart from existing research is that it spans a large number of projects which vary in size, language, and domain. Furthermore, we conduct a survey, which was disseminated among a wide variety of open-source developers, instead of at a single company or in an enterprise setting. Our research consists of three parts. Firstly, we assess whether there is a relationship between the time to merge a PR and its coverage levels. We find that such a relationship does exist in certain projects. Secondly, we look at the impact of PR comments mentioning coverage on the odds of said coverage improving. Using the odds ratio test, we conclude that there are greater odds of coverage improving when it is mentioned than when it is not. Thirdly, we conduct a survey to ask developers their reasons for ignoring a failing status check related to code coverage. Some reasons they give are the complexity of testing, the triviality of the proposed changes, or the pull request being too important to wait for proper testing. Furthermore, respondents who identify as code contributors find themselves twice more likely to find fixing coverage a waste of their time than those who identify as code maintainers, while code maintainers are more concerned with not scaring away new contributors with strict coverage guidelines.

Raccoon Serious Games hosts so called escape events. These events are similar to an escape room in which teams work together to solve puzzles, only on larger scale. Different kinds of challenges, arise when hosting these events, such as monitoring the progress of the teams and managing collection of physical puzzles. For an escape event, different kinds of staff help the teams to have the best experience possible. The teams need to be able to submit their answers to puzzles, while the staff should provide them with the right materials and monitor their progress. To facilitate these needs, Raccoon Serious Games created the Massive Online Reactive Serious Escape (M.O.R.S.E) system. However, the old system lacked in the parts of modularity and flexibility, while having the event hardcoded. To solve this problem, we created a new system to improve the lesser points of the old system while also improving the usability and maintainability. Over the course of ten weeks, we researched and created the Massive Online Reactive Serious Escape 2.0 (M.O.R.S.E 2.0) system. The first part of the project consisted of researching the previous system to find the requirements for a new system. After that, a new system was designed and implemented from the ground up. M.O.R.S.E 2.0 contains all the functionality of the old system, while also improving the structure of the administrator panel. Furthermore, the final product comes with several editors, allowing for designing the puzzles, schedule and logic in the form of rulesets for an escape event and allowing multiple events to be created managed. Furthermore the configuration editor allows the employees of Raccoon Serious Games to adjust different types of settings and cosmetics. The product was successfully tested during an escape event and will be used by Raccoon Serious Games for future events.