Programming exercises: Improve test build logs for Haskell exercises

[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.

Changes affecting Programming Exercises

• High priority: I tested all changes and their related features with all corresponding user types on a test server configured with the integrated lifecycle setup (LocalVC and LocalCI).
• I tested all changes and their related features with all corresponding user types on a test server configured with Gitlab and Jenkins.

Motivation and Context

As noted in #9159, the test runner disabled the console output to produce the XML instead. Therefore, the test results no longer show up in the build log which makes it harder to debug what is happening when setting up exercises.

Description

Updates the test template to produce both the console logs that then show up in the build log, and the XML needed to report the result back to Artemis.

Steps for Testing

Prerequisites:

• 1 Instructor

1. Create a new Haskell programming exercise.
2. The solution should pass all tests.
3. Look at the build logs in Jenkins, or download the build logs for the solution build in the build history tab of the course. The test results should show up in the log as well (example below).

Tests
  Properties
    Checked by SmallCheck
      Testing filtering in A:                  OK
        475 tests completed
      Testing mapping in A:                    OK
        19 tests completed
      Testing filtering in B:                  OK
        475 tests completed
      Testing mapping in B:                    OK
        19 tests completed
      Testing filtering in C:                  OK
        475 tests completed
      Testing mapping in C:                    OK
        19 tests completed
    Checked by QuickCheck
      Testing A against sample solution:       OK
        +++ OK, passed 100 tests.
      Testing B against sample solution:       OK
        +++ OK, passed 100 tests.
      Testing C against sample solution:       OK
        +++ OK, passed 100 tests.
  Unit Tests
    Testing selectAndReflectA (0,0) []:        OK
    Testing selectAndReflectB (0,1) [(0,0)]:   OK
    Testing selectAndReflectC (0,1) [(-1,-1)]: OK

All 12 tests passed (0.01s)

Testserver States

Note

These badges show the state of the test servers.
Green = Currently available, Red = Currently locked
Click on the badges to get to the test servers.

Review Progress

Code Review

• Code Review 1
• Code Review 2

Manual Tests

• Test 1
• Test 2

Test Coverage

unchanged

---

@coderabbitai ignore

[HawKhiem]

Tested on TS3. The solution build passed and the mentioned lines were indeed to be found in the build log