metaplay test integration [flags]

PREVIEW: This command is currently in preview and may change in the future. If you encounter problems or have feedback, please file an issue at https://github.com/metaplay/cli/issues/new.

Run Metaplay integration tests for your project.

The tests are run within containers. The game server and test container images are first built and then used to run the tests.

For each of the tests, the game server container is first started in the background and then the test-specific container is run against the game server.

Tests:

• bots: Run botclient tests.
• dashboard: Run dashboard Playwright tests.
• system: Run Playwright.NET system tests.

Examples

# Run the full integration test pipeline
metaplay test integration
# Run the tests without building the images. Speeds up the run if you already built the images.
metaplay test integration --skip-build
# Run only the 'bots' test.
metaplay test integration --test=bots
# Run with a custom timeout (e.g., 30 minutes)
metaplay test integration --timeout=30m

Flags

• --debug-network: [internal] Run network connectivity tests for debugging (for debugging the CLI itself)
• --output-dir <string>: Directory for test output and results (default: ./integration-test-output)
• --skip-build: Skip the docker image build step (faster if you already built the images)
• --test <string>: Run only the specified test ('bots', 'dashboard', 'system')
• --timeout <duration>: Timeout for running tests (e.g., 30m, 1h, 2h30m). Does not apply to image builds. (default: 1h0m0s)

Inherited Flags

• --color <string>: Should the output be colored (yes/no/auto)? [env: METAPLAYCLI_COLOR] (default: auto)
• --project <string>: Path to the to project directory (where metaplay-project.yaml is located)
• --skip-version-check: Skip the check for a new CLI version being available
• --verbose: Enable verbose logging, useful for troubleshooting [env: METAPLAYCLI_VERBOSE]