TL;DR

  • Resolved an issue preventing maestro test from running in cloud environments.
  • Improved stability for users configuring Maestro Cloud via environment variables.
  • Ensures consistent test execution when MAESTRO_CLOUD_API_KEY is present without MAESTRO_CLOUD_WORKSPACE_ID.

Key Changes

The Maestro CLI 2.6.1 update focuses on a single, yet important, bug fix:

  • Fixes: Addressed an issue where the maestro test command would fail if the MAESTRO_CLOUD_API_KEY environment variable was set, but MAESTRO_CLOUD_WORKSPACE_ID was not. This fix prevents unexpected test failures and streamlines cloud test setup.

For full details, refer to the official Maestro changelog.

Impact for QA Teams

This update directly benefits QA teams utilizing Maestro Cloud for mobile and API testing. It removes a potential blocker for test execution, ensuring smoother integration and more reliable results when configuring cloud tests using environment variables. Teams can now configure MAESTRO_CLOUD_API_KEY without concern for immediate failure if MAESTRO_CLOUD_WORKSPACE_ID is not simultaneously defined.

FAQ