Skip to content

Updates smoke to remove mariadb tests#581

Merged
dbasunag merged 1 commit intoopendatahub-io:mainfrom
dbasunag:smoke_update
Sep 4, 2025
Merged

Updates smoke to remove mariadb tests#581
dbasunag merged 1 commit intoopendatahub-io:mainfrom
dbasunag:smoke_update

Conversation

@dbasunag
Copy link
Copy Markdown
Collaborator

@dbasunag dbasunag commented Sep 3, 2025

Description

How Has This Been Tested?

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

Summary by CodeRabbit

  • Tests

    • Reclassified specific parameterized cases under smoke and sanity groups to refine targeted test execution.
    • Removed smoke/sanity markers from several creation-related tests; core logic and assertions unchanged.
    • Adjusts which tests run in focused suites without altering functionality.
  • Chores

    • No user-facing changes; impacts only CI/test selection and reporting.

@dbasunag dbasunag requested review from fege and lugi0 as code owners September 3, 2025 21:32
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Sep 3, 2025

📝 Walkthrough

Walkthrough

Test markers were adjusted in the model registry REST API tests: specific parameterized cases received new smoke/sanity marks, and six individual tests had their existing smoke/sanity markers removed. No test logic, assertions, or public APIs changed.

Changes

Cohort / File(s) Summary
Parameterized case markers updated
tests/model_registry/rest_api/test_model_registry_rest_api.py
Added pytest marks to two parameter sets: first set marked as smoke, second as sanity, altering test selection for those cases.
Markers removed from specific tests
tests/model_registry/rest_api/test_model_registry_rest_api.py
Removed smoke/sanity markers from six tests: test_validate_model_registry_resource, test_model_registry_validate_api_version, test_model_registry_validate_oauthproxy_enabled, test_create_update_model_artifact, test_updated_model_version, test_updated_registered_model.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 3, 2025

The following are automatically added/executed:

  • PR size label.
  • Run pre-commit
  • Run tox
  • Add PR author as the PR assignee
  • Build image based on the PR

Available user actions:

  • To mark a PR as WIP, add /wip in a comment. To remove it from the PR comment /wip cancel to the PR.
  • To block merging of a PR, add /hold in a comment. To un-block merging of PR comment /hold cancel.
  • To mark a PR as approved, add /lgtm in a comment. To remove, add /lgtm cancel.
    lgtm label removed on each new commit push.
  • To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
    verified label removed on each new commit push.
  • To Cherry-pick a merged PR /cherry-pick <target_branch_name> to the PR. If <target_branch_name> is valid,
    and the current PR is merged, a cherry-picked PR would be created and linked to the current PR.
  • To build and push image to quay, add /build-push-pr-image in a comment. This would create an image with tag
    pr-<pr_number> to quay repository. This image tag, however would be deleted on PR merge or close action.
Supported labels

{'/hold', '/build-push-pr-image', '/wip', '/cherry-pick', '/verified', '/lgtm'}

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
tests/model_registry/rest_api/test_model_registry_rest_api.py (1)

29-41: Add stable IDs for param sets to improve test names and selection clarity

Adding ids makes nodeids explicit in reports and CI logs; also simplifies targeted runs.

Apply:

         pytest.param(
             {},
             {},
             MODEL_REGISTER_DATA,
-            marks=(pytest.mark.smoke),
+            marks=pytest.mark.smoke,
+            id="default-db",
         ),
         pytest.param(
             {"db_name": "mariadb"},
             {"db_name": "mariadb"},
             MODEL_REGISTER_DATA,
-            marks=(pytest.mark.sanity),
+            marks=pytest.mark.sanity,
+            id="mariadb",
         ),
📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a49ee47 and 0f3751a.

📒 Files selected for processing (1)
  • tests/model_registry/rest_api/test_model_registry_rest_api.py (1 hunks)
🧰 Additional context used
🧠 Learnings (3)
📚 Learning: 2025-08-08T15:58:03.524Z
Learnt from: lugi0
PR: opendatahub-io/opendatahub-tests#487
File: tests/model_registry/async_job/constants.py:23-31
Timestamp: 2025-08-08T15:58:03.524Z
Learning: In opendatahub-io/opendatahub-tests, for tests under tests/model_registry/async_job (e.g., constants.py and related fixtures), runs start from a clean, known Model Registry state. Therefore, using static MODEL_ID, MODEL_VERSION_ID, and MODEL_ARTIFACT_ID values in MODEL_SYNC_CONFIG is intentional and acceptable; dynamic ID injection is not required for these async job tests (per guidance from user lugi0).

Applied to files:

  • tests/model_registry/rest_api/test_model_registry_rest_api.py
📚 Learning: 2025-07-04T00:17:47.799Z
Learnt from: dbasunag
PR: opendatahub-io/opendatahub-tests#401
File: tests/model_registry/rest_api/mariadb/conftest.py:89-110
Timestamp: 2025-07-04T00:17:47.799Z
Learning: In tests/model_registry/rest_api/mariadb/conftest.py, the model_registry_with_mariadb fixture should always use OAUTH_PROXY_CONFIG_DICT for the oauth_proxy parameter regardless of the is_model_registry_oauth parameter value, based on expected product behavior for MariaDB-backed ModelRegistry instances.

Applied to files:

  • tests/model_registry/rest_api/test_model_registry_rest_api.py
📚 Learning: 2025-07-30T14:15:25.605Z
Learnt from: dbasunag
PR: opendatahub-io/opendatahub-tests#429
File: tests/model_registry/rbac/test_mr_rbac_sa.py:45-45
Timestamp: 2025-07-30T14:15:25.605Z
Learning: In tests/model_registry/rbac/test_mr_rbac_sa.py, bounds checking for model_registry_instance_rest_endpoint list access is not needed because upstream fixture validation already ensures endpoints exist before the tests execute. The Model Registry setup process validates endpoint availability, making additional bounds checks redundant.

Applied to files:

  • tests/model_registry/rest_api/test_model_registry_rest_api.py
🔇 Additional comments (1)
tests/model_registry/rest_api/test_model_registry_rest_api.py (1)

29-41: Ensure CI runs smoke with -m 'smoke and not sanity' to exclude MariaDB The tests correctly mark the default-DB parameter set as smoke and MariaDB as sanity, aligning with the PR goal.

Copy link
Copy Markdown
Contributor

@fege fege left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@dbasunag dbasunag merged commit b02cc25 into opendatahub-io:main Sep 4, 2025
9 checks passed
@dbasunag dbasunag deleted the smoke_update branch September 4, 2025 12:18
@github-actions
Copy link
Copy Markdown

github-actions bot commented Sep 4, 2025

Status of building tag latest: success.
Status of pushing tag latest to image registry: success.

mwaykole pushed a commit to mwaykole/opendatahub-tests that referenced this pull request Jan 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants