Ongoing

Odoo is a highly-configurable web-based ERP for various management tasks (CRM, inventory management, sales, invoicing, etc.) for small and medium-sized businesses. Odoo is developed mainly in Python and Javascript. This project will involve working with Odoo developers on one of the following topics at the intersection of Continuous Integration and Software Testing.

Fuzz testing, or simply fuzzing, is an automated testing technique aiming at discovering bugs or vulnerabilities of software systems by providing random, invalid, or potential harmful input data. Fuzzing is a black-box testing technique, as typically, fuzzers, i.e. tools running fuzzing, have no access to the source code. Where structured testing will typically be manually written, i.e. developers will write test cases to ensure a system behaves as expected - verification - and fulfils the users’ expectations - validation -, fuzzing tools may employ techniques to generate a range of inputs with minimal manual intervention. However, many open-source or openly-accessible fuzzers have rudimentary user interfaces, so that developers must typically have a good understanding of what software security testing is, as well as understand how specific fuzzers need to be configured for specific software under tests. This project will explore how existing fuzzers could be made more approachable for non-experts. The scope of the project will be restricted to web systems (REST).

The goal of the thesis is to devise an approach for automated test execution for digital performances developed using creative coding.

In recent years, sustainability concerns have emerged in the software engineering community. However, little research focuses on the link between the evolution of a source code and energy consumption. Consequently, most developers don’t know the energy consumption of their software during its development. To address this problem, we want to build a theory that binds the evolution of a source code to its energy consumption profile. This relies on the measurement of the energy consumption evolution of multiple projects using repository mining approaches, the analysis of the reasons for this evolution, the design of proper data visualization to make this information available for the developers, and the evaluation of these objectives through the development of a framework for developers. This theory and the associated framework may help developers have better knowledge of the energy consumption evolution of their software and tools to reduce its consumption.