[DSPX-3302] (4/5) xtest conftest: --scenario and --instance flags

[dmihalcik-virtru]

Summary

Fourth PR in the five-part stack. Adds two new pytest CLI options to xtest/conftest.py:

• --scenario PATH — when set, defaults --sdks-encrypt, --sdks-decrypt, and --containers from the scenario file's sdks and suite blocks. CLI-passed options always win.
• --instance NAME — propagated to OTDF_LOCAL_INSTANCE_NAME so any nested otdf-local invocation agrees on the instance.

The authoritative entry point remains otdf-local scenario run <path> (PR 3), which sets these flags for you. This PR lets pytest accept them directly when running scenario-aware sessions outside the wrapper (e.g., a developer iterating with pytest --scenario foo.yaml -k some_test).

The --scenario import of otdf_sdk_mgr.schema is guarded with a try/except so minimal pytest environments that don't have otdf-sdk-mgr installed silently no-op.

Stack

1. (base) Shared schema — chore(xtest): Shared Scenario/Instance Pydantic schema in otdf-sdk-mgr #450
2. (base) Platform installer + install scenario — feat(xtest): Lets otdf-sdk-mgr manage platform too #451
3. (base) otdf-local multi-instance refactor — feat(xtest): otdf-local multi-instance refactor #452
4. This PR — xtest conftest integration
5. Claude plugin

Test plan

• cd xtest && uv run pytest --collect-only -q → 103 tests still collect cleanly
• uv run pytest --help shows --scenario and --instance under custom options
• No regressions to existing --sdks-encrypt / --sdks-decrypt / --containers parametrization

Jira: https://virtru.atlassian.net/browse/DSPX-3302

🤖 Generated with Claude Code

Stack (a60d3302):

• chore(xtest): Shared Scenario/Instance Pydantic schema in otdf-sdk-mgr #450 DSPX-3302-01-shared-schema ← root
• feat(xtest): Lets otdf-sdk-mgr manage platform too #451 DSPX-3302-02-platform-installer ← root
• feat(xtest): otdf-local multi-instance refactor #452 DSPX-3302-03-multi-instance ← root
• [DSPX-3302] (4/5) xtest conftest: --scenario and --instance flags #453 DSPX-3302-04-xtest-conftest ↳ on feat(xtest): otdf-local multi-instance refactor #452 ← this PR
• [DSPX-3302] (5/5) Claude plugin: bug-repro skills for OpenTDF #454 DSPX-3302-05-claude-plugin ↳ on [DSPX-3302] (4/5) xtest conftest: --scenario and --instance flags #453
• [DSPX-3302] (6/6) feature-orchestrate skill + cells-of-effort spec #455 DSPX-3302-06-feature-orchestrate ↳ on [DSPX-3302] (5/5) Claude plugin: bug-repro skills for OpenTDF #454
• DSPX 3382 mlkem scenarios #463 DSPX-3382-mlkem-scenarios ↳ on [DSPX-3302] (5/5) Claude plugin: bug-repro skills for OpenTDF #454
• feat(xtest): Adds dpop verification tests #485 DSPX-3397-kc26-dpop ↳ on [DSPX-3302] (6/6) feature-orchestrate skill + cells-of-effort spec #455

Generated by wgo stack. Edit text above or below this block, not inside it.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9f1ec9d3-4410-45e7-b6ed-0e36cd08086d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch DSPX-3302-04-xtest-conftest

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request introduces new pytest CLI options, --scenario and --instance, and implements logic in pytest_configure to handle scenario-based defaults and environment variable propagation. The review feedback suggests using explicit is None checks for CLI options to ensure that user-provided empty strings are respected as overrides, rather than being ignored in favor of defaults. Additionally, a redundant import os statement was identified for removal.

[gemini-code-assist]

The import os statement is redundant as it is already imported at the top of the file (line 18). Additionally, the check if instance: should be replaced with if instance is not None: to correctly handle cases where an empty string is explicitly passed via the CLI, ensuring it is respected and not ignored in favor of scenario defaults.

Suggested change

	import os
	instance = config.getoption("--instance")
	if instance:
	os.environ["OTDF_LOCAL_INSTANCE_NAME"] = instance
	instance = config.getoption("--instance")
	if instance is not None:
	os.environ["OTDF_LOCAL_INSTANCE_NAME"] = instance

References

1. Redundant imports should be removed to maintain code cleanliness and avoid confusion.
2. When implementing configuration overrides, ensure that explicit user input (even if empty) is prioritized over default values.

[gemini-code-assist]

Use is None checks for CLI options to ensure that explicit overrides (including empty strings) are respected and not overwritten by scenario defaults. This maintains the 'CLI wins' principle described in the function's docstring.

Suggested change

	if not config.getoption("--sdks-encrypt") and scenario.sdks.encrypt:
	config.option.sdks_encrypt = " ".join(scenario.sdks.encrypt.keys())
	if not config.getoption("--sdks-decrypt") and scenario.sdks.decrypt:
	config.option.sdks_decrypt = " ".join(scenario.sdks.decrypt.keys())
	if not config.getoption("--containers") and scenario.suite.containers:
	config.option.containers = scenario.suite.containers
	if not instance and scenario.instance.metadata.name:
	os.environ["OTDF_LOCAL_INSTANCE_NAME"] = scenario.instance.metadata.name
	if config.getoption("--sdks-encrypt") is None and scenario.sdks.encrypt:
	config.option.sdks_encrypt = " ".join(scenario.sdks.encrypt.keys())
	if config.getoption("--sdks-decrypt") is None and scenario.sdks.decrypt:
	config.option.sdks_decrypt = " ".join(scenario.sdks.decrypt.keys())
	if config.getoption("--containers") is None and scenario.suite.containers:
	config.option.containers = scenario.suite.containers
	if instance is None and scenario.instance.metadata.name:
	os.environ["OTDF_LOCAL_INSTANCE_NAME"] = scenario.instance.metadata.name

References

1. When implementing configuration overrides, ensure that explicit user input (even if empty) is prioritized over default values.

[gemini-code-assist]

Code Review

This pull request introduces new CLI options, --scenario and --instance, to the pytest configuration and implements a pytest_configure hook to manage scenario-based defaults and environment variable propagation. The review feedback highlights that using falsiness checks for CLI options prevents users from overriding scenario defaults with empty values; it is recommended to use is None checks instead to ensure CLI-passed options always take precedence. Additionally, a redundant local import of the os module was identified.

[gemini-code-assist]

The current implementation uses falsiness checks (if not ...) to determine if CLI options were provided. This prevents users from explicitly overriding scenario defaults with empty values (e.g., --sdks-encrypt "" to run no encryption SDKs), as an empty string is falsy and will be replaced by the scenario's default. Using is None checks ensures that only unprovided options are populated from the scenario file, adhering to the principle that CLI-passed options always win.

Additionally, the local import os is redundant as it is already imported at the top of the file (line 18).

    instance = config.getoption("--instance")
    if instance is not None:
        os.environ["OTDF_LOCAL_INSTANCE_NAME"] = instance

    scenario_path = config.getoption("--scenario")
    if not scenario_path:
        return
    try:
        from otdf_sdk_mgr.schema import load_scenario
    except ImportError:
        # otdf-sdk-mgr may not be installed in a minimal pytest env.
        return
    scenario = load_scenario(scenario_path)
    if config.getoption("--sdks-encrypt") is None and scenario.sdks.encrypt:
        config.option.sdks_encrypt = " ".join(scenario.sdks.encrypt.keys())
    if config.getoption("--sdks-decrypt") is None and scenario.sdks.decrypt:
        config.option.sdks_decrypt = " ".join(scenario.sdks.decrypt.keys())
    if config.getoption("--containers") is None and scenario.suite.containers:
        config.option.containers = scenario.suite.containers
    if instance is None and scenario.instance.metadata.name:
        os.environ["OTDF_LOCAL_INSTANCE_NAME"] = scenario.instance.metadata.name

[gemini-code-assist]

Code Review

This pull request introduces new --scenario and --instance CLI options to the pytest configuration, along with a new pytest_configure function to handle scenario-based defaults and environment variable propagation. The review identifies a potential issue where the current logic for applying scenario defaults to SDK flags ignores the general --sdks CLI flag, and provides a code suggestion to ensure that CLI-provided options correctly take precedence.

[gemini-code-assist]

The current logic for applying scenario defaults to --sdks-encrypt and --sdks-decrypt does not account for the general --sdks CLI flag. Since pytest_generate_tests (lines 199-203 and 214-218) uses --sdks as a fallback when the specific flags are missing, programmatically setting config.option.sdks_encrypt or config.option.sdks_decrypt from the scenario file will cause any CLI-provided --sdks value to be ignored. To ensure that "CLI-passed options always win" as stated in the PR description, these defaults should only be applied if neither the specific flag nor the general --sdks flag was provided on the command line.

Suggested change

	if not config.getoption("--sdks-encrypt") and scenario.sdks.encrypt:
	config.option.sdks_encrypt = " ".join(scenario.sdks.encrypt.keys())
	if not config.getoption("--sdks-decrypt") and scenario.sdks.decrypt:
	config.option.sdks_decrypt = " ".join(scenario.sdks.decrypt.keys())
	if not config.getoption("--sdks-encrypt") and not config.getoption("--sdks") and scenario.sdks.encrypt:
	config.option.sdks_encrypt = " ".join(scenario.sdks.encrypt.keys())
	if not config.getoption("--sdks-decrypt") and not config.getoption("--sdks") and scenario.sdks.decrypt:
	config.option.sdks_decrypt = " ".join(scenario.sdks.decrypt.keys())

[gemini-code-assist]

Code Review

This pull request enhances the pytest configuration by adding --scenario and --instance CLI options. A new pytest_configure hook is implemented to propagate the instance name via environment variables and to load default values for SDK and container settings from a scenario file when provided. The review feedback points out a redundant local import of the os module that should be removed to maintain code cleanliness and follow PEP 8 standards.

[gemini-code-assist]

The os module is already imported at the top of the file (line 18). This local import is redundant and can be removed to improve code clarity and adhere to Python's best practices (PEP 8), which recommend placing all imports at the top of the module.

[github-actions]

X-Test Results

✅ go-v0.15.0
✅ js-main
✅ js-v0.15.0
✅ java-main
✅ go-main
✅ java-v0.15.0

[github-actions]

X-Test Results

✅ java@main-v0.15.0
✅ java@main-main
✅ js@main-v0.15.0
✅ js@main-main
✅ go@v0.30.0-main
✅ go@main-main
✅ go@main-v0.15.0
✅ go@v0.30.0-v0.15.0
✅ js@v0.4.0-main
✅ js@v0.4.0-v0.15.0

[github-actions]

X-Test Results

✅ java@main-v0.15.0
✅ java@main-main
✅ js@main-main
✅ js@main-v0.15.0
✅ go@v0.30.0-main
✅ go@main-v0.15.0
✅ go@main-main
✅ js@v0.4.0-main
✅ go@v0.30.0-v0.15.0
✅ js@v0.4.0-v0.15.0

[github-actions]

X-Test Failure Report

[github-actions]

X-Test Failure Report

✅ java@main-main
✅ js@main-main
✅ js@v0.4.0-main

[github-actions]

X-Test Failure Report

[github-actions]

X-Test Failure Report

[github-actions]

X-Test Failure Report

[github-actions]

X-Test Failure Report

✅ java@v0.15.0-main
✅ java@main-main
✅ java@main-v0.16.0
✅ go@v0.32.0-main
✅ js@main-main
✅ js@main-v0.16.0
✅ go@main-main
✅ go@main-v0.16.0
✅ js@v0.4.0-main
✅ java@v0.15.0-v0.16.0
✅ go@v0.32.0-v0.16.0

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud