- Evaluate two peer iPs Sat, Oct 12th 2359
1 Evaluate two peer iPs Sat, Oct 12th 2359
This activity is worth 2x2=4 participation points.
- Wait for the email notifying you which iPs are allocated for you to evaluate. When the email is sent out, it will also be announced via course announcements.
- Download the latest JAR file of the first iP by following the link provided.
- Locate the User Guide of the app by following the link provided in that email.
- Open the Canvas survey (the one named
iP Peer Evaluation 1) that you will be using to submit your evaluation and take note of the things you need to evaluate. - Run the jar file in the following manner:
- Put the jar file in an empty folder
Reason: prevent data files created by other jar files you tested earlier from interfering with the current jar file. - Open a terminal, and navigate to the folder you put the JAR file in (e.g.,
cd smoke-test/ip1)
Reason: data files will be created relative to the folder the terminal is currently in. - Run the
java -versioncommand to confirm you are using Java 17.
Mac user, confirm you are using the exact Java distribution we have prescribed here. - Run the jar file using the
java -jar "{file_name}"command (rather than double-clicking) in the same terminal.
- Put the jar file in an empty folder
- Do a light testing of the app (not more than 10 minutes) to ensure the claimed features actually exist and there are no obvious bugs.
- Do a quick examination of the code (~ 5 minutes) by following the provided link.
- Submit your evaluation using the survey.
- Repeat the above steps for the 2nd iP allocated to you (use the survey
iP Peer Evaluation 2).
If both iPs crash or fail severely in a similar fashion, the problem may be on your side. Please contact the teaching team to ask how to proceed. - Take note of the effort required for a typical iP: After seeing two more iPs, you should now be in a better position to estimate how much you need to do for the tP (reason: the expected implementation effort for the tP is estimated with reference to the implementation effort required for a typical iP).