• Configuration file. Create currents.config.ts|js to define Currents configuration (in addition to CLI flags, reporter configuration or environment variables). Currents evaluates the contents - i.e. you can use custom code and logic within the file.

• Lifecycle functions. Use the configuration file to define custom lifecycle function. For example, orchestration.onFinish runs after run completion, the function accepts the latest known status of a distributed orchestrated run (reported by the server from all CI machines). You can invoke custom logic based on the reported run progress status - e.g. send an API call or finalize Visual Testing tools run (ArgosCI, Applitools) after all results were reported.

Improvements

• Inline Test Record Links. Console output includes inline links to individual test recordings for more convenient navigation.

Misc

• Report the original run details when rerunning previously failed tests.

• Better support for uploading generic and arbitrary artifacts - that unlocks support for Playwright Coverage and Lighthouse reports.

• Retry failed network requests. We’ve worked with AWS support to reduce the impact of requests failing because of internal AWS issues (the current failure rate is at 0.002%, which is below AWS formal SLA).

• Security patches and minor bug fixes.