This page describes how the on-site tests will look like and eventually will also contain description of the (big) homework assignment.
Please, have a look at the course guide page for details how the grading works.
On-site tests
This is the schedule for the on-site tests. The test will be held at the beginning of the lab (duration of the test is 45 minutes).
| Week (date) | Topic |
|---|---|
| 09 (April 13 - April 17) | T01: Git versioning system |
| 12 (May 4 - May 7 + May 15) | T02: Shell scripting |
| 14 (May 18 - May 22) | T03: make build tool |
You are expected to come to the lab you have enrolled to.
Because of state holiday on May 8, the T2 examination for Friday labs will be postponed by a week. We are aware it is not optimal but the schedule for this semester has virtually no complete week (i.e., teaching in all days of a week) during the second half of the semester.
Your solution will be submitted through GitLab or through other Git repository: make sure you can perform a clone via a command-line client.
You are allowed to use our webpages, off-line manpages and you can consult your notes and solutions to examples that are part of the lab materials.
You are not allowed to use any other devices (cell phones, your own laptops etc.), consult other on-line resources (the machines will have restricted access to the Internet anyway) or communicate your solution to other students (and vice versa).
In other words, the on-site tests require that you can solve the tasks on your own with technical documentation only.
Any attempt to bypass the above rules (e.g. trying to use AI assistant on your cell phone) means failing the course on the spot.
You are free to ask for clarification from your teacher if you do not understand the assignment, obviously. We can provide limited hints if it is clear that you are heading in the right direction and need only a little push.
Please, see also the general rules in the course guide.
Quizzes
Quizzes will be given on labs 02, 03, 04, 05, 06 and 07 (and 08 for Friday labs).