Skip to content

Programatic procedure to retrieve the output path of a test #478

@umarcor

Description

@umarcor

Ref #467.

@umarcor:
Is it possible to read test_name_to_path_mapping.txt directly as some Python type (dict or list)?

@kraigher:
The file was intended for human use. The format is folder_name SPACE test_name.
I do not recommend that you use it. It is better we add this to --export-json instead.

@kraigher:
Currently the commands are logged if you use --log-level=DEBUG for human use. If an external tool needs this information we need to add it to --export-json.

@umarcor:
IMHO, there should be a simple and realiable programatic procedure to retrieve the output/log of a test. It don't really mind if I need to set some stdout in the python script, or get it as a return field from vu.main(), or parse some output file. I am trying to process test_name_to_path_mapping.txt just because I didn't find a better way to 'see' the content in output.txt.

About adding it to --export-json, although useful, I'd rather avoid it for this specific use case. Using JSON is a better approach when it is to be used from Python, Go, etc. But, with Bash or C I find it easier not to require a JSON parsing library. The current format, as you described it, is straighforward, as one only needs to search for the first space.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions