chore(stoneintg-1092): refactor group snapshots tests

[jencull]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Issue ticket number and link

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

Checklist:

• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
• I have updated labels (if needed)

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign psturc for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[jsztuka]

Changes look fine in general, let see if the CI passes.

[jsztuka]

I think once you change the commit message from chore(stoneintg-1092) to chore(stoneintg-1092): conventional commit check will pass.

[jencull]

I think once you change the commit message from chore(stoneintg-1092) to chore(stoneintg-1092): conventional commit check will pass.

Yep, have changed it but its not showing in the title. Will come back to it.

This is a WIP, I am just testing this before i start merging additional code from the status-reporting file. Will then test those changes and, finally, update the readme. So its marked as a WIP for now as I work my way through the stages.

[jencull]

/retest

[konflux-ci-qe-bot]

@jencull: The following test has Failed, say /retest to rerun failed tests.

PipelineRun Name	Status	Rerun command	Build Log	Test Log
konflux-e2e-5zzgl	Failed	/retest	View Pipeline Log	View Test Logs

Inspecting Test Artifacts

To inspect your test artifacts, follow these steps:

1. Install ORAS (see the ORAS installation guide).
2. Download artifacts with the following commands:

mkdir -p oras-artifacts
cd oras-artifacts
oras pull quay.io/konflux-test-storage/konflux-team/e2e-tests:konflux-e2e-5zzgl

Test results analysis

🚨 Error occurred while running the E2E tests, list of failed Spec(s):

➡️ [failed] [It] [integration-service-suite Creation of group snapshots for monorepo and multiple repos] with status reporting of Integration tests in CheckRuns when creating and testing multiple components should lead to build PipelineRun finishing successfully for go-component-cremng [integration-service, group-snapshot-creation]

Click to view logs

Unexpected error:
    <*errors.StatusError | 0xc00088f540>: 
    components.appstudio.redhat.com "go-component-cremng" not found
    {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {
                SelfLink: "",
                ResourceVersion: "",
                Continue: "",
                RemainingItemCount: nil,
            },
            Status: "Failure",
            Message: "components.appstudio.redhat.com \"go-component-cremng\" not found",
            Reason: "NotFound",
            Details: {
                Name: "go-component-cremng",
                Group: "appstudio.redhat.com",
                Kind: "components",
                UID: "",
                Causes: nil,
                RetryAfterSeconds: 0,
            },
            Code: 404,
        },
    }
occurred

---