Establish a regression SVG file collection
I forget when exactly we discussed this, but the idea was to have a place to easily collect random SVG files from bug reports or community members that exhibit odd behaviors or provide stressful workloads for performance testing.
The best way to structure this, I'm not sure. Probably keep them separate from the main codebase, maybe with laxer commit permissions?
Currently it's in the main codebase so that it can be run with "make test" at each commit/MR. It can be easily moved to a separate repo when we will use git submodule
Marc Jeanmougin, you've been doing a lot of good work lately on setting up testing, including some render check testing in the main codebase. Would you be willing to take ownership of this task?
Sure ! I even recently discovered we used to have such a suite (in 2014) : https://bazaar.launchpad.net/~inkscape.dev/inkscape-rendertest/trunk/files
Another related thing I started a while ago and will finish One Day(tm) (probably when there will be an easily compilable gui-less inkscape with no gtk) will be to integrate Inkscape into a fuzzing engine to automatically find files that would crash Inkscape on launch.