JSON

[CScharer]

This is not an issue, but rather a question/request. Why not have it write out a json file with a list of the json rather than a log file with bunch of lines of dictionaries?

[nicoddemus]

Hi @CScharer,

As stated in the README:

Each line of the report log contains a self contained JSON object corresponding to a testing event, such as a collection or a test result report. The file is guaranteed to be flushed after writing each line, so systems can read and process events in real-time.

One of the use cases is being able to read the reports in real time, which would not be possible if we formatted it as a list, because the list would only be fully formed (the ending ]) at the end of the session. Having one JSON object per line allows each line to be processed as they are written.

Closing this for now, feel free to follow up with more questions.

[xsamueljr]

This plugin can't include an option to convert JSON Lines in JSON once the tests have finished? That would be very helpful to make documents in an automated way, for example, a summary with the results in MarkDown format. Or is it not very different to process both formats? Sorry, I don't have much experience

(I apologize for my lack of ability regarding the lexicon of the English language)

[The-Compiler]

It's not very different indeed. All you would do is something like:

with open("pytest.jsonl") as f:
    for line in f:
        rep = json.load(line)
        # do something with the data in 'rep'