Pekka Klärck

This is the most important RF 6.1 issue because there are so many interesting usages for it in the ecosystem. Basic functionality is ready and will be part of the...

Remaining tasks to get this done: - [ ] Handling resource files. - [x] Support serializing resource files to JSON and using them with "normal" `.robot` tests. This requires deciding...

You can manipulate `TestSuite.resource.variables`, but it's not too convenient. That API could be enhanced, but I believe you typically want to pass variables like this to `TestSuite.run` and that works...

The above commit added support for JSON resource files and enhanced error handling if a parsed JSON file is invalid. With resource files it is possible to use either `*.json`...

There are currently the following limitations: 1. The source path is stored in absolute format. This causes problems if data is moved to another machine with a different directory layout....

In the previous comment I mentioned that absolute suite source is problematic. The commit above added `TestSuite.adjust_source` that can be used to make absolute source relative and to add a...

Commits listed above have added a JSON schema as well as documentation in the User Guide. Creating JSON resource files was made more convenient by #4793. We can finally consider...

No updates in over two years. Closing.

Yes, this is effectively a duplicate of #4807.

This will be done in RF 7.0. For forward compatibility, it would be good to add propertys containing start, end and elapsed times as `datetime` and `timedelta` objects already in...