-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
E2E konflux tooling
-
Quality / Stability / Reliability
-
False
-
-
False
-
Unset
-
In Progress
-
0% To Do, 50% In Progress, 50% Done
-
-
-
Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.
Summary and goal
This epic aims to integrate {}integration tests{} into {}Konflux pipelines{}. The primary goal is to enable *pluggable configurations* for different testing frameworks, specifically {}Cypress{}, *IQE, and, as a stretch goal, **Playwright*. This will allow teams to run their integration tests as part of the continuous integration process on Konflux, either as new tasks via a remote pipeline configuration or through dedicated Konflux integration tests.
Acceptance Criteria
These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.
- A user can configure a Konflux pipeline to run {}Cypress tests{} using a custom configuration.
- A user can configure a Konflux pipeline to run {}IQE tests{} using a custom configuration.
- The system can correctly execute the configured Cypress and IQE test tasks within the Konflux pipeline.
- (Stretch) A user can configure a Konflux pipeline to run {}Playwright tests{} using a custom configuration.
- Test results from Cypress and IQE runs are properly reported and accessible within Konflux.
Checklist
| Checklist Item | Required | Notes or Comments |
|---|---|---|
| Workstream or external team dependencies? | Y | Requires collaboration with the {}Konflux team{} for pipeline configuration and the {}DevOps team{} for infrastructure setup. |
| ADR Required? | Y | New ADR like file should be created |
| Testing plans | Y | New automation tasks need to be created for each framework (Cypress, IQE, Playwright). |
| Known dependencies? | N |
Open Questions
* What's the best approach to handle {}test environment setup{} within the Konflux pipeline for each testing framework?Capture any open questions and resolutions related to the epic goal or acceptance criteria. Add any additional details, questions or decisions that need to be made or addressed.
- How will we manage and store {}test artifacts{}, such as screenshots and videos, from the test runs?
- What's the process for gaining approval for the new Konflux tasks or remote pipeline configurations from the platform team?
- Will there be any specific security requirements for running these tests within the Konflux environment?
