Create tests for each macro in order to know if it is still functioning correctly

[luzpaz]

Maybe we need to consider having tests for each and every macro that can be run to test the integrity of the macro code between version updates?

@galou thoughts ?

Related to:

• Unit tests for macros (checking compatiblity with current build) #160
• Tracking: Py3/Qt5 + Uniformity #8

[galou]

A good idea, for sure but developing the framework for this is out of my capacities right now.

[luzpaz]

@chennes maybe something for the FPA ?

[oursland]

One approach is to publish a list of public APIs and provide versioning for them. A package can declare the API versions it is requesting and when they are no longer supported they may be identified as deprecated or incompatible without the need for executing tests.

As the APIs are already defined through the custom binding generator, it may be a relatively straightforward extension to the existing descriptions.

This however does not address the functional regressions that are not associated with API changes, for which tests may be useful, but does provide a mechanism by which FreeCAD can modernize and update the APIs with breaking changes in a controlled fashion.

[luzpaz]

cc @chennes @yorikvanhavre