testing-conventions

To run pytest and linting checks for the Nebius Physical AI repository, you must use the correct virtual environment commands specified by the testing-conventions protocol to ensure environment consistency and validate your code changes. This standardizes test execution across the project.

Live-infra integration testing in NPA workflows requires registering workflows in the submission matrix, managing environment variables, and verifying deployments against real Nebius infrastructure. This ensures changes to npa.workflow specs are properly gated and validated.

Validating infrastructure changes across diverse compute tiers in Nebius Physical AI involves executing standardized testing protocols and infrastructure validation procedures. This ensures compliance with repository-specific testing markers and deployment verification requirements.

Yes, NPA live-infra testing requires proper environment variable management to ensure compliance with repository-specific testing markers. The testing-conventions Skill defines mandatory requirements for handling these variables during live-infra integration tests.

Unit tests often fail due to configuration errors when not using the standardized virtual environment commands for pytest and ruff. The testing-conventions Skill provides unified rules to prevent these common errors and ensure consistent test coverage.

The best way to standardize testing protocols for Nebius Physical AI workflow specs is to apply unified rules for running tests, linting, and validating infrastructure changes. This prevents configuration errors and ensures proper gating across diverse compute tiers.