You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a DevOps engineer, I want to include a fifth test suite for integration tests in dotCMS' core project, so that we can improve test coverage and ensure better software quality.
The main purpose is to not overload the rest of test suites which are kind on balanced in terms of the time it takes.
Acceptance Criteria
A new integration test suite is added to the existing test framework.
The new test suite is properly integrated into the CI/CD pipeline.
The pipeline execution times are analyzed and optimized to accommodate the additional test suite.
Documentation is updated to reflect the new test suite and its execution process.
Successful execution of the new test suite on at least three different builds.
dotCMS Version
main
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
to_define
Assumptions & Initiation Needs
The existing test framework allows for easy addition of new test suites.
Sufficient infrastructure and resources are available to support an additional test suite in CI/CD.
The test cases for the new suite are well-defined and align with core project requirements.
Quality Assurance Notes & Workarounds
If the new test suite significantly increases pipeline execution time, consider parallel execution or selective running strategies.
Ensure that test flakiness is addressed before full integration.
Sub-Tasks & Estimates
Define the structure and scope of the new integration test suite (4h)
Implement and configure the test suite (8h)
Modify the CI/CD pipeline to include the new test suite (6h)
The text was updated successfully, but these errors were encountered:
User Story
As a DevOps engineer, I want to include a fifth test suite for integration tests in dotCMS' core project, so that we can improve test coverage and ensure better software quality.
The main purpose is to not overload the rest of test suites which are kind on balanced in terms of the time it takes.
Acceptance Criteria
dotCMS Version
main
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
to_define
Assumptions & Initiation Needs
Quality Assurance Notes & Workarounds
Sub-Tasks & Estimates
The text was updated successfully, but these errors were encountered: