Thanks for the PR. In order to get RF 7.2 out still this year, we decided to move this functionality to RF 7.3 that we start developing right after the new year. Because I need to concentrate on 7.2, I won't have time to properly review this until it is in the release candidate phase. I took a quick look at the changes, though, and here are quick comments based on that:

• In general changes look good.
• The functionality to specify allowed metadata/setting names is missing. It is probably a good idea to implement it separately after the basic functionality is done, but it needs to be taken into account. It would be good to design it soon, but that can be discussion in the issue or on Slack.
• Existing tests are broken and need to be fixed.
• Plenty of new tests are needed. Parser changes can be tested using unit tests, but otherwise this is easiest to test on the acceptance tests level.
• metadata should be after tags in TestCase.__init__ to avoid breaking usages where tags are passed as a positional argument. It needed to be at the end of the argument list to be even safer, but then the position would be too inconsistent.
• XML and JSON schemas need to be updated.
• Documentation is needed. We are going to recreate the User Guide as part of RF 7.3, so perhaps this should wait until that's done.

Hello @DanielSeim is there a way i can help you out with this functionality ? Do you need a hand on anything regarding ?

FYI i will change the loading of the custom settings to cli options to get rid of the toml dependency as clarified at robocon.

The PR has merge conflicts that must be resolved before further evaluation.