Dear participants,

the mutant pipeline of the individual phase has just been released.

To register tests that should run against the mutants you have to register them in the function registerSystemTestsMutantSimulation. All other tests will not run against the mutants including the tests registered in registerSystemTestsMutantValidation. Please make sure that all tests that are registered for the mutants pass against the reference as the mutants will only be executed if the tests in registerSystemTestsMutantSimulation do not fail.

In total there are 10 mutants and as with the mandatory test set, you will have jokers (i.e., a number of mutants that you do not need to find). For the mutants you will have 3 jokers.

We have also uploaded a file in the General section of the materials giving you a small hint about what each mutant might be about.

Furthermore, we have released a optional test set. You don't have to pass these tests they are only there to help debug potential problems.

Best,
the SE Lab Team

Dear participants,

we have just released the feedback on your voluntary submissions. You can find it on your personal status page in the CMS.

Remember to submit your final class diagram and project description until Monday, 07.10.2024 4pm.

We have also released a document with the test descriptions of the mandatory test set in the Materials section.

Please also don't forget the course evaluation (the Links are also on your personal status page) which is possible until next Monday.

Starting on Monday there will be office hours everyday from 10am to 12pm and from 2pm to 4pm. You can find which room the office hours will be in in the Timetable of the course later today.
In these office hours the tutors will answer questions about the implementation and testing.

Best,
the SE Lab Team

Dear participants,

we have released the test pipelines for the mandatory validation, component, and full scenario tests. There are 50 tests in total and you have 2 jokers (that means you have to pass 48 out of 50 tests).
The results are again pushed to the results branch of your repositories.

Remember that there is the design submission deadline (class diagram and project description) on Monday at 4pm. By then, we will also release the mutants.

Best,
the SE Lab Team

Dear Participants,

We have added some clarifications and simplifications to the specification of the individual phase.

In particular we changed the following:

- Changed the decision on where to repair/refuel/unload to closest station and tie-breaker by lowest id (not with cost anymore)

- removed space at the end of two log-messages (before the dot)

- clarified the length for unloading and repairing (1 tick)

Best regards,

The SE-Lab Team

Dear participants,

we have just created your repositories in the GitLab. Furthermore, we have uploaded four files in the Materials section of the CMS:

• The project description of the group phase reference you got.
• The Latex template for the project description.
• The class diagram of the reference implementation you got as a .pdf file
• The class diagram as a .puml file

This Wednesday, you can upload a draft of your project description in the CMS (we will enable the submission in a little while) and get feedback until Friday at 2pm.

Best,
the SE Lab team

Dear participants,

We have completed the evaluation of the group phase (Code Submission).
You can find the results on your personal status page in the CMS.

On Monday, the individual phase of this year's SE Lab starts.
There will be a lecture on Monday morning at 9:30, in which the individual phase will be presented.

Best,
The SE-Lab team

Dear participants,

as the group phase comes to a close tomorrow evening, we have increased the test runs for your projects to approximately every 30 minutes.

Also, the tutors have kindly offered to extend tomorrows office hour until the deadline at 6pm. The office hour will take place in room 013 in building E1 2.

Also please don't forget the introduction of the individual phase project next Monday at 9:30am in the GHH.

Best,
the SE Lab Team

Dear participants,

we have just released a set of optional systemtests that will from now on be run on your implementations. These are not relevant for passing but rather there to help you narrow down potential problems in your code.

Furthermore, we have increased the number of runs that each group will have in a day. Our tests will now be executed every three hours on your implementations if you pushed changes to main in the corresponding time frame.

Best,
the SE Lab Team

Dear participants,

the mutant pipeline has just been released.

To register tests that should run against the mutants you have to register them in the function registerSystemTestsMutantSimulation. All other tests will not run against the mutants including the tests registered in registerSystemTestsMutantValidation. Please make sure that all tests that are registered for the mutants pass against the reference as the mutants will only be executed if the tests in registerSystemTestsMutantSimulation do not fail.

In total there are 25 mutants and as with the mandatory test set, you will have jokers (i.e., a number of mutants that you do not need to find). For the mutants you will have 2 jokers.

We have also uploaded a file in the General section of the materials giving you a small hint about what each mutant might be about.

As a bonus (since the pipelines started so late), each group will get one additional mutant run on our server, which you can request anytime from tomorrow until Friday morning by telling your tutor.

Best,
the SE Lab Team

Dear participants,

starting today there will be an office hour every day from 2pm to 4pm this week. The office hour today will be in Room 206 E1 1. For the following days please check the timetable on the day of the office hour.

For the office hour you are only allowed to send one or two students per group at a time because of space restrictions.

Best,
the SE Lab Team

Dear participants,

From now on, we run the set of tests that are mandatory to pass on your implementation as well as your tests on our reference implementation (using the function called 'registerSystemTestsReferenceImpl' in the SystemTestRegistration.kt file).
We have three categories of tests: validation tests, component tests, and full tests.
The validation tests check how you handle correct and incorrect configuration files,
component tests check the behavior of your implementation for specific parts of the simulation, and 
full tests check the behavior of your implementation for the whole simulation.
Please note that we only test changes that you have pushed to your main branch.
Please also note that we stop running the tests as soon as your server crashes 10 times (SERVER_FAIL or TIME_OUTS).

On Monday, we will release a second set of tests to the three categories that will be optional for passing the course but help to debug your simulation.
Additionally starting on Monday, we run your tests (registered in the function 'registerSystemTestsMutantSimulation' in the SystemTestRegistration.kt file) against mutants of the reference implementation to check whether your tests are able to detect the introduced faults.
However, we will only run your tests on our mutants, if all tests registered in this function succeed on our reference implementation.

Important: You have to pass at least 97 out of the 100 mandatory tests to be able to pass the group phase.
You can find a document with all the mandatory tests in the Materials (CMS) under General with a short description of the test scenarios.

Best, 
Your SE-Lab Team