Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Integration Test Suite #31351

Closed
3 tasks
victoralfaro-dotcms opened this issue Feb 12, 2025 · 1 comment · Fixed by #31518
Closed
3 tasks

New Integration Test Suite #31351

victoralfaro-dotcms opened this issue Feb 12, 2025 · 1 comment · Fixed by #31518

Comments

@victoralfaro-dotcms
Copy link
Contributor

victoralfaro-dotcms commented Feb 12, 2025

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

  • 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)
@victoralfaro-dotcms victoralfaro-dotcms self-assigned this Feb 12, 2025
@victoralfaro-dotcms victoralfaro-dotcms moved this from New to Next 1-3 Sprints in dotCMS - Product Planning Feb 12, 2025
@victoralfaro-dotcms victoralfaro-dotcms changed the title Nre Integration Test Suite New Integration Test Suite Feb 12, 2025
@victoralfaro-dotcms victoralfaro-dotcms moved this from Next 1-3 Sprints to Current Sprint Backlog in dotCMS - Product Planning Feb 27, 2025
@victoralfaro-dotcms victoralfaro-dotcms moved this from Current Sprint Backlog to In Progress in dotCMS - Product Planning Feb 28, 2025
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants