Automated UI E2E Testing: Test Case Development #1228
Description
Overview
- Relates to Automated UI E2E Testing: Environment Setup #990
- This proposal outlines the development of fundamental Cypress tests for critical modules
- And their integration into the CI/CD pipeline for automatic execution in the development environment and potential future deployment.
Explain the topic in 2 sentences
- The Cypress setup for E2E testing is already integrated, and we will provide test scenarios for the automated validation of essential workflows across the application's core modules.
- This enhances release reliability and accelerates issue detection during development.
What's the benefit?
This implementation improves quality assurance by providing efficient, reliable testing automation. The streamlined CI/CD integration enables faster releases with a reduced risk of errors reaching production.
What are the Risks/Dependencies ?
It requires collaboration and review of the CI/CD pipeline to ensure seamless integration.
Detailed explanation
- Initial test coverage will focus on primary modules such as apps, services, and user management (which are defined in UI Automation Test Plan and Roadmap portal-frontend#1375).
- Cypress tests will then be integrated into the CI/CD pipeline during development, enabling automated execution upon the creation of new features and ensuring consistent verification of workflows.
Current implementation
- Manual testing is currently used to validate workflows, which is both time-consuming and susceptible to human error, impacting the overall release process.
Proposed improvements
- Introducing Cypress as an automated E2E solution will replace much of the manual testing, allowing for continuous validation, early detection of bugs, and improved reliability in deployment processes.
Feature Team
Contributor
Committer
User Stories
Acceptance Criteria
- Develop essential Cypress tests to cover modules such as apps, services, user management, etc.
- Integrate Cypress tests into our CI/CD pipeline for development, enabling seamless automated execution upon deployment (possibly in the future)
Test Cases
Test Case 1
Steps
- Do something
- Click something
- Add something
Expected Result
- Expectation
- Expectation
- Expectation
Architectural Relevance
The following items are ensured (answer: yes) after this issue is implemented.
In the context of the standards 126 and 127, typically only one is applicable, depending on the specific use case. Please cross out one of the two standards that does not apply.
- This feature aligns with our current architectural guidelines
- Data Sovereignty: All data sharing activities across company boundaries follow the Catena-X Regulatory Framework, in particular the Data Exchange Governance, and the Dataspace Protocol via a compliant Connector (like the tractusx-edc or similar, see Connector KIT)
- Interoperability: Digital Twins are used (compliant to the Digital Twin KIT and the Industry Core KIT)
- Data Format:
- The data model is based on a published Semantic Model
- The impact on the overall system architecture has been assessed. The Feature does not require changes to the architecture or any existing standard? Please have a look here on the overarching architecture
- Potential risks or conflicts with existing architecture has been assessed
Justification: (Fill this out, if at least one of the checkboxes above cannot be ticked. Contact the Architecture Management Committee to get an approval for the justification)
Additional information
- I am aware that my request may not be developed if no developer can be found for it. I'll try to contribute a developer (bring your own developer)