A new keyword "Last REST Instance" is implemented

[TeddyTeddy]

This keyword allows the very last instance to be written to a file.
This becomes handy, when you just made a request and you want to get the instance for it.

A sample usage would be:

*** Keywords ***
Gather Instances While Creating Parameterized Resources
    [Arguments]     ${record list}         ${private token}
    FOR     ${record}    IN      @{record list}
        POST    /projects       body=${record}[json_resource]    headers=${private token}
        Last Rest Instance      file_path=${record}[on_create_instance]      sort_keys=True     # instance for the POST request
    END

[asimell]

@TeddyTeddy This functionality seems to exist already? You can give a file_path argument to Output keyword, which then writes your output into a file.

[TeddyTeddy]

@asimell , as per your comment:

@TeddyTeddy This functionality seems to exist already? You can give a file_path argument to Output keyword, which then writes your output into a file.

Hi! Yes, output keyword does write the request & response schema to a file, but it does not write the whole instance. The instance is a larger entity, which is composed of:

• request in JSON
• response in JSON
• the contract: the request schema + the response schema

If we want to have the instance as a record into a file, this utility keyword "Last REST Instance" would be helpful.

[asyrjasalo]

I think @asimell is correct. There is a way to achieve above without adding a new keyword.

[TeddyTeddy]

@asyrjasalo @asimell Sure, you can opt out my "Last REST Instance" keyword; but one change here that you might need to take into consideration is that before my changes only request & response body were outputted, but with my changes every key/value pair in the request & response are now outputted via "Last REST Instance" keyword.

Also, the end user of the library would have to write & maintain a function containing at least 10 lines of code, while
the library itself has the instance data already ready to be written into a file. Imagine that tens of users does the same. Isn't that a wasteful effort from the end users' perspective?

I have nothing further to say. Thanks anyway bringing life back to this important library.

[asimell]

only request & response body were outputted

Incorrect. If you call Output without any parameters it outputs the full request and response object. You can then redirect this output into a file with the file_path argument, e.g Output file_path=my_output.json

There's also Output Schema to output the schema only and you can give a file_path argument to that keyword as well.