Add tests for activation key with multiple content view environments

[jnagare-redhat]

Problem Statement

New MutiCV feature added for Activation key.

Solution

Add tests for activation key with multiple content view environments

test_positive_multi_lce_with_single_cv:
Validates that an activation key can have the same content view assigned to
multiple lifecycle environments. Creates a single content view, promotes it
to two different lifecycle environments, and verifies the activation key can
be configured with both CV/LCE combinations (CV1+LCE1, CV1+LCE2).

test_positive_multi_lce_with_multi_cv:
Validates that an activation key can have multiple content views assigned to
multiple lifecycle environments. Creates three different content views, each
promoted to a different lifecycle environment, and verifies the activation key
can be configured with all three unique CV/LCE combinations (CV1+LCE1, CV2+LCE2,
CV3+LCE3).

Related Issues

Airgun PR :SatelliteQE/airgun#2305
Automating https://issues.redhat.com/browse/SAT-30913

PRT test Cases example

trigger: test-robottelo
pytest: tests/foreman/ui/test_activationkey.py -k "test_positive_multi_lce_with_single_cv or test_positive_multi_lce_with_multi_cv"
airgun: 2305

Summary by Sourcery

Add UI tests validating activation keys can associate content views with multiple lifecycle environments.

Tests:

• Add coverage for activation keys using a single content view across multiple lifecycle environments.
• Add coverage for activation keys using multiple content views across multiple lifecycle environments in a single key.

[sourcery-ai]

Reviewer's Guide

Adds two UI test cases that validate activation key behavior when assigning content views across multiple lifecycle environments, covering both single-CV/multi-LCE and multi-CV/multi-LCE scenarios.

File-Level Changes

Change	Details	Files
Add test that an activation key can assign the same content view to multiple lifecycle environments	Generate random names for activation key, lifecycle environments, and content view Create first custom repository, publish a content view, and promote it to the first lifecycle environment Create a second custom repository, lifecycle environment, and update the content view to include the new repository Publish a new content view version and promote it to the second lifecycle environment Create an activation key bound to the first CV/LCE combination and then update it to add the second combination via the UI session Read activation key details and assert there are exactly two content view environment assignments matching the expected CV/LCE pairs	tests/foreman/ui/test_activationkey.py
Add test that an activation key can assign multiple content views each to different lifecycle environments	Generate random names for activation key, three lifecycle environments, and three content views Create three custom repositories and corresponding content views, each published and promoted to a distinct lifecycle environment Create an activation key with the first CV/LCE combination, then update it twice to add the second and third CV/LCE combinations via the UI session Read activation key details and assert there are exactly three content view environment assignments matching the expected CV/LCE pairs	tests/foreman/ui/test_activationkey.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• The setup for creating/publishing/promoting content views and lifecycle environments is duplicated across both tests; consider extracting a small helper to keep this logic consistent and easier to maintain.
• In both tests you index session.activationkey.search(name)[0] without checking the list length; adding an explicit assertion that a single result is returned before indexing would make the tests more robust and clearer when they fail.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The setup for creating/publishing/promoting content views and lifecycle environments is duplicated across both tests; consider extracting a small helper to keep this logic consistent and easier to maintain.
- In both tests you index `session.activationkey.search(name)[0]` without checking the list length; adding an explicit assertion that a single result is returned before indexing would make the tests more robust and clearer when they fail.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[jnagare-redhat]

trigger: test-robottelo
pytest: tests/foreman/ui/test_activationkey.py -k "test_positive_multi_lce_with_single_cv or test_positive_multi_lce_with_multi_cv"
airgun: 2305

[LadislavVasina1]

Small changes requested, otherwise looks good.

[jnagare-redhat]

trigger: test-robottelo
pytest: tests/foreman/ui/test_activationkey.py -k "test_positive_multi_lce_with_single_cv or test_positive_multi_lce_with_multi_cv"
airgun: 2305

[vijaysawant]

Suggested. cosmetic changes which will not break execution flow

[jnagare-redhat]

trigger: test-robottelo
pytest: tests/foreman/ui/test_activationkey.py -k "test_positive_multi_lce_with_single_cv or test_positive_multi_lce_with_multi_cv"
airgun: 2305

[jnagare-redhat]

Small changes requested, otherwise looks good.

Updated

[jnagare-redhat]

trigger: test-robottelo
pytest: tests/foreman/ui/test_activationkey.py -k "test_positive_multi_lce_with_single_cv or test_positive_multi_lce_with_multi_cv"
airgun: 2305

[vijaysawant]

LGTM

[jnagare-redhat]

trigger: test-robottelo
pytest: tests/foreman/ui/test_activationkey.py -k "test_positive_multi_lce_with_single_cv or test_positive_multi_lce_with_multi_cv"
airgun: 2305