Skip to content

README.md

Latest commit

 

History

History
74 lines (50 loc) · 1.85 KB

README.md

File metadata and controls

74 lines (50 loc) · 1.85 KB

Running ITK Tests Locally

This directory contains scripts to run Integration Test Kit (ITK) tests locally using Podman.

Prerequisites

1. Install Podman

Run the following commands to install Podman and its components:

sudo apt update && sudo apt install -y podman podman-docker podman-compose

2. Configure SubUIDs/SubGIDs

For rootless Podman to function correctly, you need to ensure subuids and subgids are configured for your user.

If they are not already configured, you can add them using (replace $USER with your username if needed):

sudo usermod --add-subuids 100000-165535 --add-subgids 100000-165535 $USER

After adding subuids or if you encounter permission issues, run:

podman system migrate

Running Tests

1. Set Environment Variable

You must set the A2A_SAMPLES_REVISION environment variable to specify which revision of the a2a-samples repository to use for testing. This can be a branch name, tag, or commit hash.

Example:

export A2A_SAMPLES_REVISION=itk-v.015-alpha

2. Execute Tests

Run the test script from this directory:

./run_itk.sh

The script will:

  • Clone a2a-samples (if not already present).
  • Checkout the specified revision.
  • Build the ITK service Docker image.
  • Run the tests and output results.

Debugging

To enable debug logging and persist logs for inspection:

  1. Set the ITK_LOG_LEVEL environment variable to DEBUG:

    export ITK_LOG_LEVEL=DEBUG

  2. Run the test script:

    ./run_itk.sh

When run in DEBUG mode:

  • The logs/ directory will be created in this directory (if it doesn't exist).
  • The logs/ directory will be mounted to the container.
  • The test execution will produce detailed logs in logs/ (e.g., agent_current.log).
  • The logs/ directory will not be removed during cleanup.