Creation of a new branch - test-infrastructure, which is responsible …

[GRIGAeo]

…for test automation. All changes related to test coverage will be made in this branch going forward. This commit includes the following changes: renaming the file ci.yaml to ci-docs.yaml and creating a new file ci-tests.yaml, which runs tests on every push and pull request in any branch

[GRIGAeo]

Adding a new branch and creating a configuration file that automatically runs tests on pushes and pull requests.

[gsvgit]

Бездумная нейронка детектед. Лучше пользоваться максимально свежими версиями action-ов.

[gsvgit]

Я правильно понимаю, что мы собираем тестовое покрытие тесов? Несколько загадочно выглядит.

[GRIGAeo]

Это так, меня не много смутил данный action для работы с многомодульными проектами. Я решил явно указать пути до xml отчётов, но я щас проверил ещё раз. По-моему этот action вообще не принимает дополнительных аргументов, а сам всё находит. Так что щас подправлю эту часть кода и в следующем PR всё будет нормально

[GRIGAeo]

This PR introduces the following changes:

1. Test Coverage Reporting Setup

   Configured generation of test coverage reports (XML, CSV, HTML) for the generator and solver modules.

   The following coverage thresholds have been set per module:

    Instructions: 95%
   
    Branches: 80%
   
    Lines: 80%
   
    Methods: 85%
   
    Classes: 90%
   

Current Coverage Metrics:

solver module:

    INSTRUCTIONS: 58.24%

    BRANCHES: 43.55%

    LINES: 54.48%

    CYCLOMATIC: 44.77%

    METHODS: 53.33%

    CLASSES: 78.21%

generator module: all metrics are currently 0%.

2. CI Workflow for Coverage Reports

   Added a CI workflow that generates a test coverage report for the entire project on:

    push events
   
    pull_request events
   
    manual workflow dispatch
   

3. Publishing to GitHub Packages

   Integrated and configured the maven-publish plugin in the solver and generator modules to publish JAR files to GitHub Packages.

4. Automated Publication on New Releases

   Added a configuration file to automatically publish JAR files to GitHub Packages when a new version of the project is released.

[GRIGAeo]

This PR introduces the following changes:

1. Fixed JAR file publishing

• Added a separate publisher module responsible for publishing the JAR file and POM file to GitHub Packages.
• The published JAR file will now contain only the compiled source code files, while the POM file will include references to the project's dependencies.

2. Fixed and improved the project build files for test coverage reporting

• In the generator module, any newly added unit tests will now be taken into account when generating the coverage report.
• Fixed the jacocoTestCoverageVerification task in the solver and generator modules.

[github-actions]

Overall Project	51.31%	❌

There is no coverage information present for the Files changed