FIX: unit test configuration handles deferred var @{x} from surefire/failsafe

[treilhes]

Fixes #1824
Fixes #1832

[github-actions]

Test Results

  321 files  ±0    321 suites  ±0   52m 42s ⏱️ + 1m 25s
  680 tests +2    659 ✅ ±0  20 💤 +2  0 ❌ ±0  1 🔥 ±0 
2 040 runs  +6  1 979 ✅ ±0  60 💤 +6  0 ❌ ±0  1 🔥 ±0 

For more details on these errors, see this check.

Results for commit 1e30cab. ± Comparison against base commit 3af1fc5.

♻️ This comment has been updated with latest results.

[HannesWell]

Thanks a lot for these fixes @treilhes and sorry for the late reply.

I made a few small adjustments in UnitTestSupport.resolveDeferredVariables() to be more precise in case of multiple occurrences of equal placeholders (although the result should be the same) and to handle a null value or empty properties.

I plan to submit this change this evening. Please let me know if you are not fine with any adjustments.

[HannesWell]

Thanks again.

Btw. I noticed that the tests you added are skipped in the CI. Locally they passed, but it would be good to have them running.
Could you please look into that?

[treilhes]

Hello @HannesWell

I don't have anything against your adjustments

About the unit tests not runninig, from my limited knowledge it seems neither junit or testng features are installed in the eclipse test environment which lead to disabled test.
If you can give me some pointers about where to look at for seting the features deployed in the test instance i will gladly give it a try