github.com/redhat-appstudio/e2e-tests@v0.0.0-20240520140907-9709f6f59323/tests/release/pipelines/README.md (about)

     1  # Release pipelines e2e tests suite
     2  
     3  This suite contains e2e-tests for testing release pipelines from repository [release-service-catalog](https://github.com/konflux-ci/release-service-catalog/tree/development).
     4  All tests must have the label `release-pipelines`.
     5  
     6  ## Branch alignment
     7   * Below are the branches in [release-service-catalog](https://github.com/konflux-ci/release-service-catalog/tree/development). All these branches will be tested per requirement.  
     8     - production	: this branch will be used for RHTAP production environment
     9     - stage	: this branch will be used for RHTAP stage environment
    10     - development: this branch is the default branch for development
    11  
    12  ## Test cases 
    13  ### The happy path with pushing to Pyxis stage (rh_push_to_external_registry.go)
    14  
    15  This test is designed to run the release pipeline `rh-push-to-external-registry` and validates that the artifacts are successfully pushed to Pyxis.
    16  
    17  Checkpoints:
    18    - Two build PipelineRuns are created in the dev namespace.
    19    - The build PipelineRuns pass.
    20    - The release PipelineRuns are successfully created in the managed namespace.
    21    - The release PipelineRuns are expected to pass.
    22    - The Releases pass.
    23    - Validate that the SBOM for both components were uploaded to Pyxis stage.
    24  
    25  ### The happy path with pushing to external registry (push_to_external_registry.go)
    26  
    27  This test is designed to run the release pipeline `push-to-external-registry`. 
    28  
    29  Checkpoints:
    30    - A build PipelineRun is created in the dev namespace.
    31    - The build PipelineRun passes.
    32    - The release PipelineRun is successfully created in the managed namespace.
    33    - The release PipelineRun is expected to pass.
    34    - Test if the image from the snapshot is pushed to Quay
    35    - The Release passes.
    36  
    37  ### The happy path of FBC related tests (fbc_release.go)
    38  
    39  This test is designed to run the release pipeline `fbc_release` related test and validates that the artifacts are successfully pushed. There are two test cases currently in this file. One of them is the happy path of releasing FBC related fragments and the other is for testing FBC hotfix releasing.
    40  
    41  Prerequisites: 
    42     - Export the following environment variables:
    43         - TOOLCHAIN_API_URL_ENV	: Offline token used for getting Keycloak token in order to authenticate against stage/prod cluster
    44         - KEYLOAK_URL_ENV	: Keycloak URL used for authentication against stage/prod cluster
    45         - OFFLINE_TOKEN_ENV 	: Toolchain API URL used for authentication against stage/prod cluster
    46     - The tests will run on two dedicated namespaces, so a user not part of them need to request access to the following namespaces:
    47         - dev-release-team-tenant
    48         - managed-release-team-tenant
    49  
    50  Checkpoints:
    51    - A build PipelineRun is created in the dev namespace.
    52    - The build PipelineRun passes.
    53    - The Release CR is created.
    54    - The release PipelineRun is successfully created in the managed namespace.
    55    - The release PipelineRun is expected to pass.
    56    - The Release passes.