Learning Outcomes:

  • Demonstrate the ability to write simple OOP Java programs.
  • Demonstrate the ability to apply knowledge and skills in object-oriented programming (OOP).
  • Demonstrate the ability to understand test cases that validate functionality of simple OOP Java programs.
  • Demonstrate the ability to debug and troubleshoot Java code without relying on a compiler or development environment to identify logic or compilation errors, and to correct those errors.


Edit Essential Action Points

Please carefully read and understand this entire page.

It not only contains important details about the test, but also ensures that you are aware of the rules and expectations so that you can avoid any issues.

There are action points you need to complete before the test day, and it is your responsibility to address them.



Quick Summary

  • Week 6
  • Wednesday 17th April
  • You MUST bring your student ID card to the test. Entry will be refused without it. You are allocated to a specific lab, so your ID card is your proof of identity and entry ticket.
  • Invigilated and in-person. You have a specific room location on campus, which you need to go and make sure you can log into the computers there.
  • You will be using the computer in the lab (not your own laptop or device).
  • You will be given practical programming exercises to complete.
  • You must be ready to enter your allocated lab room at 4:05pm.
  • An invigilator will assign you to a specific computer. You will not be able to choose which peer you sit next to.
  • We will use the first few minutes to make sure everyone is seated and successfully logged in. There might be 15-20 minutes “downtime” before the test actually starts, but this is the only way to make sure we can have everyone start at exactly the same time (and finish at the same time). During this downtime, you may either chat quietly with your peers, or you may use the time to review your notes. The invigilators will then give you the “go ahead”, where you will be required to put your notes away and start the test.
  • You will have 70 minutes to work on the questions. This is officially 60 minutes, but with extra 10 minutes for technical allowances. You may make use of the full 70 minutes if you wish. This also means, if you had “5 minutes of technical issues”, you are still compensated due to the extra 10 minutes.
  • Closed book: You will not be allowed to use the internet or any other resources.
  • You will not be allowed to use an IDE, Copilot, ChatGPT, etc. You must write code directly into the CodeRunner editor.
  • You are not allowed to leave the room during the last 20 minutes of the test. If you leave the room, you will not be allowed to re-enter. When you want to leave, you must wait until one of the instructors is available to check you have submitted, and to also “sign you off”. You will not be able to leave when there are only the invigilators in the room, as their role is to invigilate, not to sign you off. Read more below.



CodeRunner Exam website

This is the website you will use to complete the test:

https://coderunnerexam.auckland.ac.nz

This is the usual CodeRunner website you’ve been using for the 10x CodeRunner exercise. This is a special “Exam” mode of CodeRunner with extra restrictions and extra security checks. For example, you are only allowed to be logged in from one tab/device, otherwise you will be automatically logged out from the other tab/device.



Practice Test 1

Edit Action Required!

This is the most important thing. It requires you to dedicate time well before the test to make sure everything is working for you.

Do this in the days BEFORE the Test day. Do not leave it to the Test day!

  1. You should already be familiar with the CodeRunner Exam website, as you have been using it for the 10x CodeRunner exercises.
  2. This means you are already well aware of the importance of coding directly into the CodeRunner editor. If you’ve been going against our recommendation (which was to directly code in CodeRunner for the 10x exercises), then you might have a hard time in the Test. If that’s you, you need to pay special attention to the Practice Test 1 and make sure you are at least making up for it (for your own good) by coding directly in CodeRunner Exam.
  3. To help you refamiliarise with the style, and general CodeRunner Exam mode, there is a Practice Test 1 you must attempt.
  4. Go to your your allocated lab (see allocations at the bottom to know where you must go). You are not allowed to go to any other lab without prior approval, and you will be denied entry to a lab room you are not allocated to. Don’t risk it, otherwise you will lose valuable time that will not be compensated for. We are strict on this, as we have to ensure that we have enough space for everyone.
  5. At your allocated lab, log into one of the computers using your usual UoA credentials.
  6. Go to the CodeRunner Exam website (https://coderunnerexam.auckland.ac.nz).
  7. Make sure you not only try to log into the CodeRunner Exam website, but you specifically try do this in your allocated lab to ensure you can log in from there.
  8. You should then attempt the “Practice Test 1” (see the “Practice Test 1” section on the CodeRunner Exam website). This will give you a good idea of what the test format will be like.
  9. Note that there are a few questions in the Practice Test 1. While we attempt to give a few practice questions here, the Real Test 1 will have a different combination of questions (but formatted the same way). More details on this below.
  10. The Practice Test 1 is available from NOW until Wednesday 3:00pm of the Real Test 1 day (i.e., it will close and be hidden an hour before the Real Test 1).
  11. Furthermore, all other exercises in CodeRunner will be made hidden an hour before the Real Test starts. So make sure you don’t leave it too late to study and review.
  12. This gives you well over a full week in which to go and check that you can access the CodeRunner Exam mode in your allocated lab.
  13. Unlike the Real Test 1, you can attempt the Practice Test 1 as many times as you like. This is to allow you to practice and familiarise yourself as much as you would like.
  14. However, in the Real Test 1 you will only have one attempt/submission.
  15. This practice test is more about you familiarising with the CodeRunner Exam technology on the Real Test 1, and ensuring you have all the necessary access to complete the Real Test 1.



Real Test 1 Format

  • There will be a total of 6 programming tasks to do.
  • The 6 tasks will total 40 marks (weighted to 20% of your grade), broken up into 6 tasks of different weights.
    • Question 1 is worth 6 marks (3% of your grade).
    • Question 2 is worth 5 marks (2.5% of your grade).
    • Question 3 is worth 5 marks (2.5% of your grade).
    • Question 4 is worth 5 marks (2.5% of your grade).
    • Question 5 is worth 9 marks (4.5% of your grade).
    • Question 6 is worth 10 marks (5% of your grade).
  • Use the above weighting to decide where to spend more or less time.
  • Each programming task will have a different number of test cases (each test case is worth one mark).
  • All test cases will be shown to you. There are no hidden test cases. This is to ensure you know exactly what is being tested.
  • Code comprehension is important (and being assessed in this manner), you need to understand what the test cases are doing, and what the expected output is.
  • Each programming task will give you 15 “free” checks. On the 16th check, it will incur a 5% penalty. This goes up in increments of 5% until a maximum of 25% penalty. The nature of the test is to assess your ability to write basic Java programs. Therefore, you should not be using up all your checks, especially for basic syntax. By this stage, you should be able to write basic Java programs without needing to check every line.
  • Every programming task will give you starter code. You will copy-paste this, and immediately paste it into the CodeRunner Exam editor. This is to save you time, so you can focus on the main task at hand.
  • You will be given 70 minutes to complete the entire test. This includes an extra 10 minutes to allow for any technical issues that may arise (on top of the official 60 minutes).
  • Even though you have 70 minutes, you should aim to complete the test in 60 minutes. This will give you an extra 10 minutes overall for any potential technical issues/delays you might have. There are some easy marks you can get quickly, and some harder ones that may take longer. You should aim to get the easy marks first, and then spend more time on the harder ones if you have time left over.
  • If you believe there is something unclear or a mistake in the Test, please do your best. The invigilators will not be able to answer any questions. Given that we have so many concurrent rooms, and short timeframe for the test, we will not “announce” any mistakes/errors. Instead, we will take them into account once the marks are being finalised. So, if you believe there is a mistake, please do your best, and we will take it into account when marking. We believe this is the best, to avoid any (further) confusion, unfairness, or distraction during the test.



(Automatically) Submitting in CodeRunner Exam

  • You will only have one submission attempt.
  • Near the end of the test, a timer will appear in the top-right corner of the the CodeRunner Exam. This will count down, and once it reaches 0, you CodeRunner will automatically submit the test for you.
  • However, you should make sure you do a Check if you edited the code, in case you introduced some compilation error. If there is a compilation error, then all test cases for that task would fail! So, make sure you do a Check before submitting, even if it’s automatically submitted for you!



Warning about Compilation Errors

Do not write a lot of code without checking it. Make sure you are checking your code regularly.

Be extremely careful with compilation errors.

Do not attempt to “save checks” in order to avoid the penalties for 16+ checks (which are capped at a generous 25%). Is it worth risking a compilation error (that might get you 100% penalty for not compiling) in order to avoid a 5% penalty? No!

If you introduce a compilation error, then all test cases for that task would fail! So, make sure you do a Check well before submitting! You might need time to “fix” a compilation error!

Otherwise, it’s automatically ZERO for that task even if you otherwise had the correct code before the minor edit!

We will NOT be able to go back and review past submissions. This is not only a very manual and timely process that is impractical for the number of students we have, but it also goes against the learning outcomes of the course and most of its assessments: You are able to write code that compiles and runs, and you are able to debug and troubleshoot your code if it doesn’t compile or run.

There are many reasons why you might encounter compilation errors. You’ve been given plenty of opportunity throughout the semester to practice using CodeRunner, so you should be familiar with the common pitfalls.

Do NOT make major changes to your code in the final seconds, as under the pressure you are more likely to make mistakes.

Edit

Edit

Edit


These are just a few examples of compilation errors. Again, make sure you practice how to work directly in CodeRunner, and how to check your code regularly, to avoid such errors that might cost you a lot of marks.



Test Rules

Edit

Bring your student ID card to the test. Entry will be refused without it.

You are allocated to a specific lab, so your ID card is your proof of identity.

Your Test will not be accepted for marking if the invigilators did not check your ID card and sign you off on the attendance sheet. Anyone not signed off on the attendance sheet will not have their test accepted for marking.

If possible, try to have the same haircut and facial expression as on your ID card. This will make it easier for the invigilators to verify your identity.


  • Bring your student ID card to the test. Entry will be refused without it. You are allocated to a specific lab, so your ID card is your proof of identity. You will be marked as in attendance by the invigilators as you enter the room. Only students who are marked as in attendance will have their test marked.
  • If you need 2FA to log into the computers, make sure you have your phone with you. This is on you to ensure you can log in.
  • Be ready to enter the allocated room at 4:05pm. You don’t want to arrive last minute, as you will waste (your own) test time, distract others, and risk not being allowed in. Invigilators will prioritise invigilating the room, and cannot immediately attend to you if you are late (you will have to wait until an instructor arrives to sign you in, again wasting your own valuable test time).
  • No one is allowed to arrive late. If you arrive late, you will not be allowed to enter the room.
  • No one is allowed to leave in the first 20 minutes.
  • No one is allowed to leave in the last 20 minutes. If you leave the room, you will not be allowed to re-enter.
  • Make sure the invigilators mark you as in attendance. You will not be allowed to leave the room without them taking note of it.
  • You are NOT allowed to have any other software applications or extra tabs open on the computer you are using. You are only allowed to have the CodeRunner Exam website open. Only one tab. Only one computer. Only one browser. Only one window.
  • This means you cannot visit the dedicated SOFTENG 281 course website, ACP, (or any other website for that matter). Only CodeRunner Exam is permitted. We will also be hiding the other CodeRunner exercises, so you cannot access them during the Test.
  • There will be invigilators at both ends of the room. They will be checking:
    • That you are not using any other applications or tabs.
    • That you are not “switching” between tabs or windows.
    • That you are not using any other devices.
    • That you are not referring to any notes or books.
  • Make sure you go to toilet before the test. You will not be allowed to (immediately) leave the room during the test. We have a limited number of invigilators, and do not have allowance to have someone immediately accompany you to the toilet, as we need to ensure the integrity of the test throughout. If you need to momentarily leave, you will need to wait until the invigilator calls another invigilator (there will be additional invigilators allocated to go from room to room) to come over and accompany you. Don’t worry, we won’t go into the toilet with you. But we’ll ask you to leave your bag and phone in the room.
  • If you leave the test unattended, you will not be allowed to return.
  • It goes without saying, you cannot use an IDE, you cannot use Copilot, you cannot use ChatGPT, you cannot use NotePad, etc. You must write code directly into the CodeRunner Exam editor.
  • CodeRunner Exam provides extra integrity checks and enhanced logging. These logs will be reviewed, along with your lab computer logs (of websites visited during the test time), along with logs to the course website. Any logs that are suspicious will be investigated, and will result in an Academic Misconduct incident being filed for your Test (at the very least, this will result in a mark of ZERO). Don’t risk it.
  • You can only submit the test once. CodeRunner will ask you to confirm are you sure you want to submit. Once you submit, you cannot go back and you will be locked out. You won’t be able to come back into the room to continue the test. So, only submit if you are 100% sure you are finished. Make the most of it, and use the full 70 minutes.



Content Covered

The test will cover the content from the first half of the course. You should be familiar with the concepts covered in class, particularly how they were applied in the in-class programming exercises demonstrated. The Test is a way to not only assess your ability to apply those concepts, but also your ability to do practical programming tasks (i.e., like your assignments). The exercises will, of course, naturally be simpler in nature that your assignments.

But in a nutshell, there will be a total of 6 tasks from Nasser’s section, namely:

  • Java classes,
  • constructors,
  • instances,
  • instance methods/fields,
  • static fields/methods,
  • inheritance,
  • polymorphism,
  • equals(),
  • toString(),
  • creating and working with ArrayLists,
  • and so on.

The marks will be allocated based on functionality. Each task will have a number of test cases. You get as many marks are there are test cases that pass. Each test case is worth one mark, for a total of 40 marks weighted to 20% of your grade. The more test cases that a task has, the more marks it will be worth.

There are no marks for style (indentation, naming, commenting, etc.). It is purely on functionality. If all test cases pass, well done, even if it goes against all the style guidelines you grew to love thanks to GradeStyle.


If you feel something has been missed out, please email Nasser (n.giacaman@auckland.ac.nz) or ask on Ed Discussion, and more will be elaborated. 

All the best for the Test!



Tips for the Test

  • Budget your time per task based on the number of test cases it has. If one is taking up more time than it’s worth, leave it alone and move onto another one. This is because some of the tasks might have easy marks to gather with less effort than others. Don’t let difficult parts of one task sacrifice your time for other easy parts of another task.
  • Attempt every task. Make sure you copy the entire “Starter Code” and paste it in. For some of the questions, you can probably even complete most of the question by doing things with your eyes closed. For example: adding fields, initialising fields in the constructor, completing the getters, etc. You should be on “autopilot mode” for these things.
  • To avoid typos that will cause compilation errors (and waste your attempt counts), a good thing to do is to “copy-paste” variable/field/method names, or use code completion in CodeRunner (Ctrl + Space). Or, in the case of fields, you can maybe give it super short simple names so there’s less to type out. Remember, you aren’t getting marks for code style, so you can call variables whatever you want.
  • In the case of expected outputs of a particular format, what you can do is copy the expected output from one of the test cases and paste it immediately above the area you are coding inside a // comment. Then immediately below it, you replicate that format using that to guide you.
  • Try and be efficient in your coding. Even though you aren’t getting marks for “code reuse”, it will help you to think about reusing existing methods instead of relying on accessing fields (as it might need executing other code etc).
  • It goes without saying, that the best thing to do is to practice directly in CodeRunner with the Practice Test 1 (plus you’d have already completed the weekly CodeRunner exercises). It’s important you set the expectation of what you can and cannot do in CodeRunner, and how to navigate around it when you encounter problems such as compilation errors. Remember you don’t have a full IDE to help you.
  • If you don’t practice enough in CodeRunner, you might find yourself spending a lot of time on things that you could have easily avoided.
  • Some helpful shortcuts:
    • Ctrl + Space will give you a list of suggestions for the current context. This is particularly useful for method names, variable names, etc. This is not only helpful to speed up your typing, but also to avoid typos.
    • Ctrl + / will toggle between commenting and uncommenting out the currently-selected line(s). This is useful if you want to keep code you want to come back to if you need while you work on something else, or to add some of the description of the expected output.
    • Double click on a word will highlight it. This is useful for copying and pasting, again to avoid typos and save time:
      • Ctrl + C to copy
      • Ctrl + V to paste


Below you will find a video walking through answering CR1-CR5, which might help give you ideas on strategies to tackle the test:



What are the main restrictions?

  • You will be using the lab computers (not your own laptop).
  • You will be given programming exercises to complete in CodeRunner.
  • You will not be allowed to use the internet or any other resources.
  • You will not be allowed to use an IDE, Copilot, ChatGPT, etc.
  • You will not be allowed to refer to any notes.
  • You will not be allowed to have any other application open (other than CodeRunner in a single web browser tab).

How to best prepare?

This is a practical programming test, so the best way to prepare is to practice, practice, and practice your programming.

Here are some suggestions:

  • Do all the practice exercises provided, such as:
    • The CodeRunner exercises,
    • The Get Your Hands Dirty exercises,
    • The REWIND exercises,
  • Play around with and tweak all the ACP exercises to explore what happens when you change things, and make them your own.
  • Be confident you can do the exercises:
    • Without referring to any notes or other resources,
    • Without relying on the compiler to tell you what’s wrong,
    • Without relying on an IDE to help you write the code,
    • Without relying on Copilot or ChatGPT to help you write the code,
    • Without relying on the internet to help you write the code,
    • Without relying on Bob, Jenny, or your classmates to help you write the code.
  • Get started on the assignments early, as this provides excellent practical programming experience and confidence.
  • Repeat the above magical recipe 17 million times (or until you feel confident).



Your Allocated Lab Room

Please make sure you only attend the lab below.

You will not be allowed to enter any other lab, and the invigilators will be checking your ID card to ensure you are in the correct lab on entry.

While this list only includes your first name (and username to cross-check), the invigilators will have the full names and student IDs to cross-check.

Edit

Some of the rooms below are not immediately easy to find. So do not leave it to the last hour to go searching for your room. By being late, you risk not being allowed into the room at all until an instructor comes to sign you in, and you will waste your own valuable test time. Invigilators are not allowed to let you in after the test starts.

Also, remember, you should anyway have gone well in advance to your allocation lab room to make sure you can log in (and access CodeRunner Exam) specifically from that room.


439-G08

  • Ayesha (abab484)
  • Samuel (ylee903)
  • Bridie (bmce589)
  • Aaron (ahas673)


439-427

  • Jamie (jbar339)
  • Ryan (rgin216)
  • Miguel (mpen506)
  • Eric (elee607)
  • Jojo (jmei608)
  • Kevin (kkim985)
  • Ivory (thua238)
  • Jesse (jli876)
  • Lewis (lazz729)
  • Daniel (dkim848)
  • Anand (akri368)
  • Elijah (esal695)
  • Shakeer (sdev821)
  • Osbert (oche369)
  • Lanna (llag396)
  • Jake (jkim837)
  • Owen (osun093)
  • Ikenna (iuna331)
  • Miguel (mbal759)
  • Nicholas (nwil850)
  • Patrick (pshe539)
  • Aref (aosm976)
  • Henry (hly852)
  • Hao (hyan713)
  • Shazeel (sali153)
  • Kalupahana (ibha186)
  • Kevin (kwan244)
  • Wallace (wwu295)
  • Gab (alum086)
  • Ajith (apen181)


439-433

  • Lucas (ljun123)
  • Ahil (ahus071)
  • Uday (ujai264)
  • Adil (amur986)
  • Alex (abro522)
  • Leo (lvan346)
  • Zubair (zyah987)
  • Yash (yram171)
  • Adam (awoo445)
  • Yukyung (ylee818)
  • Vineet (vsor198)
  • Juny (eejl016)
  • David (dyu343)
  • Paul (pcha004)
  • Eddie (hkim807)
  • Joanna (jkim960)
  • Junheng (cmia215)
  • Hui (hfen382)
  • Zhihao (zliu348)
  • Atul (akod059)
  • Erica (engi850)
  • Raina (rlim538)
  • Kevin (dvu878)
  • Jolyon (jbis394)


405-328

  • Ethan (kqua446)
  • Jonathan (jgol495)
  • Saketh (skop291)
  • Caleb (cshe333)
  • Rudra (rpat943)
  • Wenzhe (wzha508)
  • Sewni (spei902)
  • Jeniffer (jfet156)
  • David (yilm466)
  • Damian (dtua408)
  • Thinamsan (tpra228)
  • Muntasir (mmas199)
  • Aldonza (hwat294)
  • Reynhard (rbui853)
  • Samuel (sang530)
  • Rafe (rbea432)
  • Shah (shus469)
  • Bochuan (bhou951)
  • Sean (sbau949)
  • Kimberley (kzhu796)
  • Chaeeun (clee482)
  • Phoebe (pfun094)
  • Rebekah (rmas773)
  • Diya (dkur670)
  • Quin (qmcc945)
  • Danika (dmon373)
  • Nick (ncoo109)
  • Pranit (pkan633)
  • Soroush (snas404)
  • Jiaxin (jyan420)
  • Oorja (ogan176)


405-326

  • Grace (gxu660)
  • Alexander (asim255)
  • Kieran (kmck133)
  • Anna (aryu462)
  • Daniel (dtie151)
  • Jim (hli605)
  • Wenjing (wyua331)
  • Kartik (kmal768)
  • Ibrahim (iwah144)
  • Daniela (droj056)
  • Subeen (sban919)
  • Di (dhua391)
  • Kurt (kluc619)
  • Arnav (abha257)
  • Tyren (tfru173)
  • Jack (jmat640)
  • Yichao (wany722)
  • Ella (ewil853)
  • Salomia (sjob296)
  • Matheus (mger154)
  • Manan (mpat501)
  • Khushie (kjun638)
  • Saiyad (smun623)
  • Ahmad (akam677)
  • Sam (hye071)
  • Anthony (apan786)
  • Rayaan (rraj313)
  • Shon (xli330)
  • Lyonne (laba812)
  • Zhenting (zwan373)


401-312

  • Zara (zcol623)
  • Newton (nyua944)
  • Amanda (phao209)
  • Nadia (nask472)
  • Shrirang (sekb555)
  • Oscar (oko158)
  • Anna (achi359)
  • Andy (ahua579)
  • Shihoo (spar820)
  • Seerat (sman833)
  • Anna (ahai431)
  • Michelle (mwan364)
  • Jayde (jlal056)
  • Nathan (nthe160)
  • Richman (rtan654)
  • Tyler (tyou333)
  • Oshan (opre469)
  • Sean (ytse120)
  • Agam (aahk798)
  • Eason (echa931)
  • Bailey (bgib630)
  • Jemy (jjej813)
  • Henry (hgao080)
  • Josh (jshi444)
  • Johnson (rzha972)
  • JooHyun (jkan172)
  • Om (opat597)
  • Andrew (ajeo563)
  • Miles (mmak111)
  • Tom (tron042)
  • Caleb (cjun818)
  • Logan (ldou101)


401-311

  • Toshiro (tmen190)
  • Jaeha (jcha513)
  • Taha (tbas606)
  • Tania (tpan328)
  • Raiyan (rkha931)
  • Jerry (pkim777)
  • Blake (byul423)
  • Conrad (cang688)
  • Aolin (ayan607)
  • Tonny (tche867)
  • Charan (cgaz516)
  • Nathan (ndso791)
  • Junyuan (jliu778)
  • Leon (llei074)
  • Leo (hpan363)
  • Calvin (cnai408)
  • Lulu (lli393)
  • Aryan (awal599)
  • Angela (zpen457)
  • Glen (gmal045)
  • Connor (nhar865)
  • Johnny (jcur152)
  • Rebecca (rnga701)
  • Albert (ayua214)


401-307

  • Silva (she940)
  • Riley (rmar633)
  • Ming (mgoy303)
  • Brian (shan790)
  • Gian (gmoh887)
  • Connie (cdin152)
  • Ella (ema340)
  • Ashwin (nisa397)
  • Minseo (mkim719)
  • Josh (jbag235)
  • Ethan (esia821)
  • Soham (skul970)
  • Lemuel (lvin900)
  • Macy (mbut885)
  • Sky (sgib237)
  • Reuben (rsta265)
  • Jack (jhar629)
  • Perry (pxie161)
  • Joe (hugn924)
  • Gibson (ggao363)
  • Brian (bhua898)
  • Aye (athu157)
  • Ron (ycho760)
  • Kabir (ksik996)
  • Cole (cbro435)
  • Viraaj (vkap589)
  • Edward (elia955)
  • Amir (amah664)
  • Eric (eche101)
  • Damian (drob588)
  • Ashkan (aaza463)


303S-175

  • Matthew (mman808)
  • Christian (cmot464)
  • Luca (llat663)
  • Daniel (mkim670)
  • Ryan (rsmi948)
  • May (mtha724)
  • Jinhao (ajhz011)
  • Navi (ngam724)
  • Daniel (dmun793)
  • Marie (mpat928)
  • Kyle (klim385)
  • Lucy (llia622)
  • Beren (besk864)
  • Milan (mahu925)
  • Alex (atee059)
  • Jacky (ajhz488)
  • Huyin (hson435)
  • Joshua (jfen705)
  • Robert (rwar748)
  • Dhruv (dsaw164)
  • Dimitri (pwat943)
  • Isaac (ihoo440)
  • Annie (jli917)
  • Amish (akmu146)
  • David (dma765)
  • Inseo (ilee973)
  • Will (wmas516)
  • Divyanshu (dkha055)
  • Meara (mkee115)
  • Liam (lhal844)
  • Liam (lbyr117)
  • Thomas (tdic873)
  • Abhishek (adey750)
  • Charlotte (cset571)
  • Toma (tmir110)
  • Emmanuel (eara128)


302-160

  • Leon (lfan827)
  • Finn (fkee774)
  • Nicky (ntia856)
  • Jeremy (jmul290)
  • Rebekah (rleg709)
  • Mikael (mjun868)
  • Prisha (psin207)
  • Weyman (wwon485)
  • Ken (kcao565)
  • Pablo (pper327)
  • Rhett (rmur989)
  • David (dli630)
  • Sam (steb012)
  • Moksh (mman402)
  • Ethan (elau447)
  • Mark (tzha578)
  • Harry (hma481)
  • Alastair (ahac139)


260-024/CompLab9

  • Mohammad (mkab524)
  • Zhiyuan (zfu276)
  • Pavle (pfil701)
  • Muhammad (mmoh314)
  • Zhanhang (zzho965)
  • Ryan (rsin531)
  • Eedong (ejeo051)
  • Dominic (dfor626)
  • Nathan (ntur101)
  • Co (cche441)
  • Hunter (hrob997)
  • Leo (lchu848)
  • Joshua (jmak320)
  • Jessica (yxie884)
  • Jimmy (cli942)
  • Jade (szho466)
  • Mellisa (mche403)
  • Kieran (kjoe685)
  • Nico (nabr105)
  • Dev (dpat391)
  • Jerry (ajhz216)
  • Jeruh (jkim828)
  • Ravi (rgre692)
  • Qiyu (qche619)
  • Skandh (sbha564)
  • Alexander (aski294)
  • Steven (shua365)


260-022/CompLab8

  • Brandon (bcha389)
  • Arthur (ali867)
  • Gavin (jchi648)
  • Ammar (aazi826)
  • Joshua (jwed606)
  • Muhammad (mmuh167)
  • Rithinath (rrav470)
  • Tristan (thal182)
  • Ryan (hlee999)
  • Thor (tbri557)
  • Dev (dkmu854)
  • Adam (amcm539)
  • Julie (xkan320)
  • Hartej (hbas168)
  • Jamie (jlah077)
  • Ken (sden589)
  • Kai (ksat689)
  • Dhruv (deri361)
  • Willow (jkoh800)
  • Diya (dvak904)