Being able to save executable test suite objects to disk would be handy, but saving them into *.robot files is not exactly trivial. Some problems that need to be addressed:

• Mapping test setup, teardown, template, tags and timeout to test specific settings like [Setup] and file related settings like Test Setup is complicated. Could obviously only use test specific settings but then there would be some duplication.
• If a suite has child suites, saving would need to create a directory structure. Possible but some work.
• A programmatically creates suite can have both tests and suites but there's no way to do that using *.robot files. One possibility to handle that would be allowing tests __init__.robot files, but that would need its own issue. Alternatively there should be an error in this case.

An alternative would be creating a new format that would allow saving the whole directory structure into a single file. That would allow pretty interesting possibilities to create tests in different formats, but designing such a format would also be a pretty big task.

Hi

I would like to create .robot file from robot.api or save py file in the current directory , In which variable can I capture the code generated by the testsuite and testcase

Regards

Being able to save executable test suite objects to disk would be handy, but saving them into *.robot files is not exactly trivial. Some problems that need to be addressed:

• Mapping test setup, teardown, template, tags and timeout to test specific settings like [Setup] and file related settings like Test Setup is complicated. Could obviously only use test specific settings but then there would be some duplication.
• If a suite has child suites, saving would need to create a directory structure. Possible but some work.
• A programmatically creates suite can have both tests and suites but there's no way to do that using *.robot files. One possibility to handle that would be allowing tests __init__.robot files, but that would need its own issue. Alternatively there should be an error in this case.

An alternative would be creating a new format that would allow saving the whole directory structure into a single file. That would allow pretty interesting possibilities to create tests in different formats, but designing such a format would also be a pretty big task.

Hi @pekkaklarck, this feature has been implemented?

No concrete plans for implementing this. It's more likely that we add support for saving executable suites into JSON. For more details see #3902.