Skip to content

Conversation

@Day509
Copy link

@Day509 Day509 commented Dec 8, 2025

Fixes [#13327]

Outline of Solution

This pull request introduces a new GitHub Actions workflow for component testing on JDK 17 and 21, adds a utility script for extracting failed test reports in HTML, and makes minor improvements to code style and exception handling in integration tests. The most significant changes are the addition of CI/CD automation and tooling for better test reporting, along with minor codebase cleanup.

CI/CD and Tooling Enhancements:

  • Added a new workflow file .github/workflows/jdk17-21.yml to run build and tests across JDK 17 and 21, supporting multiple test types and automating artifact uploads for test reports.
  • Introduced extract_failed_tests_html.sh, a shell script that generates an HTML summary of failed tests from log files to improve test failure visibility.

Codebase and Test Improvements:

  • Updated integration tests to consistently include EntityAlreadyExistsException in method signatures where relevant, improving exception handling and clarity. [1] [2] [3] [4] [5] [6] [7] [8]
  • Minor code style and import optimizations in FieldValidator.java, including improved collection initialization and additional imports for future extensibility. [1] [2] [3] [4]

Configuration Cleanup:

  • Removed the version declaration from docker-compose.yml to streamline the configuration.

Day509 and others added 27 commits October 16, 2025 16:03
Co-authored-by: AbdBoutchichi <AbdBoutchichi@users.noreply.github.com>
[Fixes TEAMMATES#13327] Adding performance logs and deduplicate entries for email
cleaning and resolving vulnerabilities
@github-actions
Copy link

github-actions bot commented Dec 8, 2025

Hi @Day509, thank you for your interest in contributing to TEAMMATES!
However, your PR does not appear to follow our contribution guidelines:

  • Description must reference the issue number the PR is fixing, e.g. Fixes #<issue-number> (or Part of #<issue-number> if the PR does not address the issue fully)

Please address the above before we proceed to review your PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants