Pekka Klärck

This seems to be a variation of #1595. Can you check that?

Closing as a duplicate. Good news is that #1595 will be included in RF 5.1!

I propose we add `to_json` method to `TestSuite`. It should by default return JSON string but it should also accept a path or an open file object where to save...

Serializing a big suite into JSON is problematic because reading it back requires deserializing the big JSON string first. To avoid problems with that, I propose we support splitting suites...

I propose we use new `.rbt` extension when saving this format into a file. We cannot really use `.json` if we support also JSON Lines and having a custom extension...

Saved suite objects in `.rbt` files should also contain imports, variables and keywords same way as normal `.robot` files can have.

External resource files could possibly be saved into a `.rbt` file as well. The best approach would be including all imported resources in it automatically but this probably should be...

This issue is highly related to the proposal to add JSON based output format (#3423). Executable suite structure and result suite structure are similar, they even have common base, and...

The biggest reason to split JSON into multiple objects is to avoid the need to read the whole file into memory and parse the whole JSON in one go. This...

Too big task for RF 4.1. Hopefully can be included in RF 5.0.