Programming 3

The Oracle

For each assignment, you will have access to an oracle available on the submission server that will allow you to check if your implementation is correct. The oracle checks that your code passes all the correctness tests that will later be used in the assignment control. Also, it checks that your implementation is properly documented. It will send you a message to your official UA email account with the result (this may take a few minutes).

Been an oracle, it will not give you clues about what errors you have, it will only answer if the code and/or the documentation are correct or not. When submitting your code to the oracle, you will receive one of these possible responses:

• Documentation: sin errores / CON ERRORES
• Code evaluation: OK / INCORRECTO / NO COMPILA

You should target a documentation verdict sin errores and an OK in code evaluation. If you have errors in the documentation, use the Javadoc checker on your code. Unpack it and read the README.txt file to learn how to use it.

A INCORRECTO verdict indicates that your code does not meet some of the specifications in the assignment. This is verified through a series of automatic unit tests in addition to those provided with the assignment.

A NO COMPILA verdict obviously indicates that your code does not compile or the unit tests being used do not compile against your code. This is due to some error in your code (a misspelled class or method name, misspecified visibility, misspecified arguments, etc.).

Teachers do not answer online requests to review your code. In particular, we do not answer requests like ‘The oracle told me that my code is incorrect/doesn’t compile. I attach my code so you can tell me where it fails’.

Take advantage of the face-to-face lab sessions if you want the teacher to take a look at your code to answer your questions. You can also make use of the Moodle practice forum to answer questions about the assignments. ALERT! never post code to the forum!!.

The assignment control

Each assignment is evaluated by means of an in-lab control. In said control you will be asked to implement the corresponding assignment, for which it is in your interest to have done it before at home, and checked with the oracle that you did it well. On the day of the control you will have to do it again, but in person at the laboratory, except for the javadoc documentation part.

At an assignment control, a submission will be enabled on the submission server where you must upload your code. Unlike the oracle, you will not receive any report about the result of your code evaluation. The grading of your code will be published at the end of the week in which the control is carried out.

Conditions for taking the assignment control:

• You must not enter the lab (even if it is the session starting time) until the teacher indicates to do so.
• You must sit in the position indicated to you.
• You should not turn on the PC until the teacher tells you to do so.
• The use of personal computers during a control is not allowed. You will need to use the lab computer to implement and submit your code to the submission server.
• You must not carry any kind of notes on paper with you. Everything you need to do the control will be available on the lab computers.
• It is absolutely forbidden to connect any device to the laboratory computers during the controls. The connection of external USB or similar devices is monitored. The detection of connection of an external device to the computer that you are using to take the control implies a score of zero in the corresponding assignment.
• You can only submit your work during the control session of your lab group, from the lab assigned to your group, and from a single PC of that lab. Any other submission attempt that does not meet these conditions will be detected and will lead to a score of zero in the corresponding control.
• You can make several submissions during the control session, always fulfilling the above conditions.
• As in any evaluation test, the regulations of the University of Alicante about assesment tests.