@sajolia reported some annoyances while trying to make the Nautilus extension work under Debian stable. I would love to have some tests in the CI to avoid this kind of inconvenience, unfortunately, I have to idea on how to test a Nautilus extension :/
Any idea which direction to take on this? I never dealt with testing GUIs, but I would give it a try, as I just came across this Debian bug report, which I closed, but I would like to keep track of it as it's still valid today.
Additionally, I would like to ensure, probably via Debians autopkgtest, that the Nautilus extension is actually being available (and working) if Nautilus is started. I've no clue either, how to achieve this, but I'll do some research.
Before working on this, I would like to quickly draft what we actually want to do. I would like to enable basic testing in the first step, and probably iterate over this later on, improving and extending the test.
For a start, what about:
Prepare env to be able to run Nautilus
Copy the extension file
Set up test dir with fixtures
Start Nautilus
Call dogtail to clean the fixtures via the Nautilus extension
Check that there is no metadata anymore in place afterwards via mat2 / libmat2