Record your Flow

Record a Flow as an MP4 with Maestro CLI and share runs for debugging or demos.

Maestro allows you to generate high-quality screen recordings of your tests without needing third-party software. The record command programmatically stitches the app screen and Flow output into a professional MP4, making it easy to debug failures or showcase features.

Why record your Flows?

• Debugging: Visually identify race conditions or rendering issues by seeing exactly where a test fails.

• Collaboration: Share a clear video of a bug or user journey with developers and stakeholders.

• Documentation: Maintain a visual record of your application's critical paths for compliance or training.

How to record

To ensure the best performance and privacy, it is recommended to use Local Rendering. This processes the video directly on your machine.

maestro record --local YourFlow.yaml

After rendering, the video will be available in the same directory as the reports and artifacts:

• macOS and Linux: ~/.maestro/tests

• Windows: %userprofile%\.maestro\tests

It's important to notice that recordings are limited to a maximum of two minutes. If your Flow runs longer, the recording will stop automatically.

Deprecation notice

The standard maestro record (remote) command is being deprecated. In future releases, local rendering will become the default behavior. We recommend switching to the --local flag now to prepare for this change.

Legacy (Remote rendering)

If you run maestro record without the --local flag, Maestro currently sends the raw screen capture and Flow output to mobile.dev servers to be processed.

Privacy and security

• Signed URLs: Remote recordings generate a signed URL valid for 60 minutes.

• Auto-Deletion: All videos sent to our servers are automatically deleted after 24 hours.

Related content

You can also record your tests using startRecording or take screenshots for specific steps using takeScreenshot.