Development: Fix execution of exercise template integration tests on Linux systems

[b-fein]

Checklist

General

• I tested all changes and their related features with all corresponding user types on a test server.
• This is a small issue that I tested locally and was confirmed by another developer on a test server.
• Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
• I chose a title conforming to the naming conventions for pull requests.

Server

• Important: I implemented the changes with a very good performance and prevented too many (unnecessary) and too complex database calls.
• I strictly followed the principle of data economy for all database calls.
• I strictly followed the server coding and design guidelines.
• I added multiple integration tests (Spring) related to the features (with a high test coverage).
• I documented the Java code using JavaDoc style.

Motivation and Context

The tests require an installation of Maven and Java 17 to run. On Linux systems, one approach to find Java 17 was using /usr/libexec/java_home. However, this tool is specific to Mac systems, thus resulting in always failing tests.

Description

• Only calls /usr/libexec/java_home on Mac systems.
• Instead of failing the tests if Maven or Java 17 cannot be found, skip them. This is achieved by using JUnit assumptions. Gradle tests can still be executed in case Maven could not be found but Java 17 was found.

Steps for Testing

Prerequisites:

• local development setup

1. Run the tests in ProgrammingExerciseTemplateIntegrationTest. If either Maven or Java 17 cannot be found, they are skipped instead of failing. If both Maven and Java 17 can be found, they are executed (like e.g. in the CI pipeline on Bamboo or GitHub Actions).

Review Progress

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Test Coverage

unchanged

---

@coderabbitai ignore

[Strohgelaender]

Thank you, code looks good.

[SimonEntholzer]

Code lgtm, and running the tests locally works as described. I don't have maven, so some are ingored, as described.
Before the fix:

After the fix: