Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10037

QE End-to-End test migration from RHDH Lightspeed with road-core to RHDH Lightspeed with lighstpeed-core

    • Icon: Story Story
    • Resolution: Done
    • Icon: Major Major
    • 1.8.0
    • None
    • AI, lightspeed, Quality
    • None

      Story (Required)

      End-to-end QE validation for the backend migration. It involves creating a test plan, setting up a stable test environment, and executing a comprehensive suite of tests.

      Background (Required)

      <Describes the context or background related to this story>

      The goal is to confirm that the user experience, functionality, and performance are preserved after migrating from ROAD-Core to Lightspeed-Core. The scope includes functional parity, configuration validation and error handling, etc.

       

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Dependencies

      <Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

      Acceptance Criteria (Required)

      <Describe edge cases to consider when implementing the story and defining tests>

      <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

      documentation updates (design docs, release notes etc)
      demo needed
      SOP required
      education module update (Filled by RHDHPAI team only)
      R&D label required (Filled by RHDHPAI team only)

      Done Checklist

      Code is completed, reviewed, documented and checked in
      Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      Continuous Delivery pipeline(s) is able to proceed with new code included
      Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
      Acceptance criteria are met
      If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well

              jrichter@redhat.com Jan Richter
              yangcao Stephanie Cao
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: