Really excited to see where this goes! Some folks see testing as something that slows development down, but in reality, a good test framework will speed things up. It allows devs to be fearless if and when they want to make changes, at any time in the cycle. Getting to the “good test framework” part is pretty difficult though.
A few comments and suggestions:
The Hook modifier should be testable without user interaction. An object hooked to an empty should get a deformation going. So that can be tweaked in your spreadsheet I think.
If possible, when there’s a set of changes that are immediately useful to have in master, I think it would be ok to submit those as soon as they are ready rather than waiting until September+ for your entire gsoc branch to be merged. This is also advantageous for review meaning things will go faster later on.
Keep the spirit of patches like D7590 alive. In other words, if new tests completely replace older ones, please let’s clean up the older ones It reduces confusion and mess.
One has to enter the Object Type and Object Name and the object is created, so after the above script is run, the Blender file will have 2 objects “Cube1” and “MyCone”.
It will work on the already existing blend file if present otherwise create a new one.
Feel free to provide your insights on whether this is a good approach and any other suggestions.