Dear participants,

following you can find the time and place of the office hours for this week until Thursday. The office hours for Friday will be announced separately.

Best,
the SE-Lab team

Dear participants,

From now on, we run a first set of tests 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.
There will be no release of another set of tests after Monday.
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.

Best, 
Your SE-Lab Team

Dear participants,

We have uploaded the feedback for your submissions. You can find it on your personal status page in the CMS below the submission. 

Please note that, if you only see feedback for your class diagram draft, the feedback for your project description will be included there.
Otherwise, you will find the feedback for your project description below the submission of your project description.

Best regards,
Your SE-Lab Team

Dear participants,

we have updated the class diagram for the reference implementation that serves as a basis for your individual project. We included the missing classes and properties and fixed a lot of style issues.

As this is quite a big change, we postpone the deadline for the draft submission of your design to **Thursday, 12 October 2023, 9 am**, and you will receive feedback on your draft on **Friday, 13 October 2023, at 2pm**. Furthermore, we postpone the first deadline of the individual phase to **Monday, 16 October 2023, 2pm**. The deadline for the final submission of your project remains unchanged.

To make up for this inconvenience, you will not have to include all methods and properties of our classes in the class diagram you submit.
You only have to include your newly added classes and the existing classes you modify, and in these only include the properties and methods you change or add.

We are sorry for the inconvenience.

Best regards,
Your SE-Lab team

Dear participants,

We have completed the evaluation of the group phase.
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,

In order to provide more feedback about your implementation to you, we have decided to split the pipeline into three parts.

The first part will run our system tests on your implementation and part of your system tests on our implementation. You need to register these system tests in the SystemTestRegistration class in a function called 'registerSystemTestsReferenceImpl' in the SystemTestRegistration.kt file in the package systemtest. You can use this category for system tests for which you want to check the simulation behaviour of our reference implementation and to fix your system tests before including them in different parts of the pipeline.

The second part will run your system tests for the validation process on our reference implementation and, if all tests pass, run these system tests on mutants of our reference implementation in which we have introduced bugs regarding the validation of the configuration files. This second part is only concerned with the validation process of the configuration files, and will therefore only result in possibly incorrect
log messages before the 'Simulation start' message (i.e. the simulation behaves exactly as in the reference implementation). You need to register them in the SystemTestRegistration class in a function called 'registerSystemTestsMutantValidation' in the SystemTestRegistration.kt file in the package systemtest.

The third part will run your system tests for the simulation on our reference implementation and, if all tests pass, run these system tests on mutants of our reference implementation in which we have introduced bugs for the simulation of the scenario. The third part is only concerned with the simulation process itself, and thus will only result in the wrong log messages after the 'Simulation start' message (i.e. the validation process behaves exactly as in the reference implementation). You need to register them in the SystemTestRegistration class in a function called 'registerSystemTestsMutantSimulation' in the SystemTestRegistration.kt file in the package systemtest.

As the last two parts are independent of each other, you should only register your system tests for one part, as validation tests will not find any bugs in the simulation and vice versa.
The results of each part will be sent to you separately via email.

Note: Make sure you update the registration of your system tests correctly, otherwise you will not receive any results for your system tests.

By splitting the test pipeline into three separate parts, we also increase the number of runs, so you receive test results more frequently.
You will be able to trigger the pipeline for the first part by pushing to the 'main' branch of your repository about every 2 hours.
You will be able to trigger the pipeline for the second part by pushing to the 'main' branch of your repository about every 8 hours.
You will be able to trigger the pipeline for the third part by pushing to the 'main' branch of your repository about every 8 hours.

Best,
The SE-Lab Team

Dear participants,

to make testing easier for you, Youssef has written a Config Creator that allows you to easily create configuration files for your tests. The Config Creator is linked under Information in the CMS. There will be also a brief explanation in the forum on how to use it tomorrow.

Best,
the SE-Lab team

Dear participants,

From now on, we run a first set of tests on your implementation as well as your tests on our reference implementation. 
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).

As we only test your main branch, you have to make sure that you push a building version of your implementation to your main branch at least one hour before your
code review to give your reviewer the chance to check the status of your implementation.

On Friday, we will add a second set of tests to the three categories.
There will be no release of another set of tests after this Friday.
Additionally starting on Friday, we run your tests 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 of your tests succeed on our reference implementation.

Best,
The SE-Lab team

Dear participants,

Tomorrow, Friday, September 08, the entry exam takes place on-site at the campus.

Since you are registered for the course in the CMS, you are automatically registered for the entry exam. (This is different from the exam registration in the LSF, which is possible and necessary for you to do until Monday, September 11).

Bring your student ID card and a photo ID card (e.g., passport) to the entry exam. No aids are allowed. Use only document-proof pens (no pencils!). Red or green pens are not permitted.

The tasks are formulated in English and German. You can provide your answers in either of both languages.

The entry exam is going to take place in multiple lecture halls simultaneously. Admittance to the lecture halls is at 09:15; make sure to be in front of the assigned lecture hall on time. The assignment of participants to lecture halls was done according to the first letter of your surname (i.e., the surname used here in the CMS):

First letter A-H: Günter-Hotz lecture hall (GHH), building E2.2

First letter I-R: HS I, building E2.5

First letter S-V: HS II, building E2.5

First letter W-Z: HS III, building E2.5

You can also see which lecture hall you have been assigned to on your personal status page in the CMS.

In case of illness, please inform us immediately by e-mail to sopra@lists.se.cs.uni-saarland.de and submit a medical certificate as soon as possible.

Good luck, and see you tomorrow!

Best,
The SE-Lab team