Detox log artifact (at test level)

[d4vidi]

Description

It can sometimes be a bit difficult to be able to trace the cause of a test failure based on the existing artifacts. At often times, on top of things such as the error message and screenshots/video, being able to review the Detox log itself can be beneficial.

While the logs are generally available (e.g. in the context of a CI build / general artifact), they are only recorded as a part of the entire testing session, and not under the context of each specific test. It make the debugging/inspection use case feel cluttered and inefficient.

Proposal: An opt-out, (trace-level?) Detox log artifact in the scope of each test.

@noomorph

[noomorph]

Dunno, we could do it maybe as a post-processing step later in the future. I would be seriously opposed to any other solution featuring splitting the logs, etc. Too many moving parts: multi-process interaction (don't forget that the logs for the same test now belong to the parent and worker processes), future-planned remote workers (other machines on the network with their logs), etc.

Only the post-processing solution can be a future-proof way to implement it. I cannot seriously consider this feature request before implementing the Allure OSS reporter.