Enlarge code testing coverage in GNOME Files
Project title
Enlarge code testing coverage in GNOME Files
Mentors
António Fernandes @antoniof
Project length
Can be either "Short (~175 hours)" or "Long ~350 hours". The number of tasks to pick from the roadmap is a function of project length.
Description
The file browser is expected to be a reliable application which people can use safely to manage their own data and keep open without affecting other tasks.
The GNOME Files application is one such file browser, originating from the nautilus project. It's a live project, under constant development (maintenance, modernization, enhancement, bugfixing) for over 2 decades. It's also an extenside codebase and original authors of many portions of it are no longer active participants. This creates a challenge to developers who, while fixing one thing can inadvertly break something else in unexpected ways on unpredictable components. The answer to this challenge are unit tests and integration tests.
Thanks to GNOME's adoption of GitLab, Continuous Integration has become a norm. GNOME Files has pipelines which test every merge request builds and passes a the tests. The existing tests already cover some critical components, but this coverage is far from complete.
The goal of this project is improving the coverage of code testing, by advancing through the roadmap in GNOME/nautilus#224 . This makes it a sequel to a previous GSoC project which has covered the first steps of that roadmap.
Requirements
Good knowledge of C. Basic knowledge of GObject. Basic knowledge of glib testing framework
Communication
chat (IRC/Matrix), email