ENH: Add script to update ITK testing macros names

[jhlegarreta]

Add script to update ITK testing macros names.

Motivated by PR #999.

This script should ease the task to update the testing macros names in
remote modules when used together with the ApplyScriptToRemotes.sh script.

PR Checklist

• 🚫 Makes breaking changes
• 🚫 Makes design changes
• 🚫 Adds the License notice to new files.
• 🚫 Adds Python wrapping.
• 🚫 Adds tests and baseline comparison (quantitative).
• 🚫 Adds test data.
• 🚫 Adds Examples to ITKExamples
• 🚫 Adds Documentation.

Refer to the ITK Software Guide for
further development details if necessary.

[jhlegarreta]

Tested as a stand-alone script. Working to apply it to remotes.

Related to this, I was wondering whether we should make the ApplyScriptToRemotes.sh script accept a varying number of additional input parameters in the event that the script that is applied to the remotes (i.e. its <script_filename> argument) requires input parameters. I guess this is doable, although it may not be easy.

I thought about it because to apply the above patch, I had to look at #999, see the changes in itkTestingMacros.h and manually code the changes to be applied by the script. I thought that an improvement over this would be to:

1. Identify the commit and the file(s) that we are interested in to draw the changes from (e.g. using git diff and generating a file with those changes).
2. Get the "changes to be applied" (e.g. change TEST_GET_SET_VALUE to ITK_TEST_SET_GET_VALUE) as an array of arguments that would be passed on to the script.

However, identifying the "changes to be applied" from the diff file to be applied to other files does not seem straightforward, to say the least.

So if we do not foresee the latter as doable, I do not see the necessity of making the ApplyScriptToRemotes.sh script accept a varying number of additional input parameters right now.

I am not willing to tackle this now (both modifying ApplyScriptToRemotes.sh to accept a varying number of additional input parameters, and a script to identify "changes to be applied" from a diff), just wondering whether you think it is doable/useful, in which case I'd open an issue.

[dzenanz]

I did not try this.

[dzenanz]

Adding variable number of arguments to ApplyScriptToRemotes.sh is probably not hard. Extracting meaningful changes from a diff to be distilled into a change-script is almost certainly impossible.