Wire up the local disk and remote persisters

[ankur22]

What?

Wire up the local disk persister (#1156) and remote persister (#1159) so that when the environment is setup correctly the remote persister is used otherwise the local persister is used.

Why?

When the configuration for the remote persister is present (the env var that was introduced in #1159), that implies that the screenshots are to be sent to a remote location. When that is not the case, then they need to be saved local to the disk.

How?

When the test run starts, if the env var (from #1159) is present and the remote persister is created, that is to be passed to the screenshotter. When this is not the case a local persister should be created and passed to the screenshotter.

1. Read and parse K6_BROWSER_SCREENSHOTS_OUTPUT which should contain all the configuration required to upload the screenshot. Take a look at how it's done in k6 for traces.
2. Create a new interface that works with both LocalPersister and RemotePersister which may require amendments to one of both of the concrete types.

Tasks

Tasks

Beta Give feedback

1. PR: Wire up the local and remote persisters #1203
2. Add screenshot upload release notes k6#3600
   +0

Related PR(s)/Issue(s)

Prerequisite issues: #1156 & #1159.