Zeus repo

• controlling maven of your project
• checking a style of code with Checkstyle
• testing students solutions with JUnit

• Zeus should be run in the root folder of the student's project, near your pom.xml. (EXAMPLE)

• In Google Cloud Shell, you have an alias — zeus = java -jar Zeus-XX.jar

• Use Java 17 and above

• jcb - Java Coding Bootcamp
• awj - Algorithms With Java
• jdd - Java Deep Dive
• cbe - Cloud Backend Engineer

• while writing the solution:
  • run code style checker separately
  • run tests separately for each day or even a separate test (the latter is optional)
• when submitting a job, you must use pass. The task can be completed in parts - it is not necessary to turn it in at once all day. You can even turn in only one point from your scoring card of the current day!

<ZEUS> — Zeus JAR file, example Zeus-49.jar

<KEY> — any available key, example: -h, -v, -d or course key. Different keys apply to Zeus itself and to individual Zeus commands.

<COMMAND> — any available command, example test

java -jar <ZEUS> <KEY>... <COMMAND> <KEY>...

An alias for Zeus is registered in Google Cloud. Therefore, the command will be like this: zeus <KEY>... <COMMAND> <KEY>...

• -dm,--developer-mode - developer mode
• -h,--help - show help
• -V,--version - show version

• show - show available courses or containers (in developing)
• style - run checkstyle for all or selected sources, you cannot pick a specific day to check the code style.
• test - run test containers. You can choose a specific day for testing.
• pass - run exam: run style and test in sequence
• maven - run maven presets or custom commands
• update - download the latest Zeus release

all commands have their own help menu, use key -h or --help to get help example: java -jar Zeus-49.jar pass -h

• show

• style

• test

• pass

• maven

• update - download the latest release of Zeus

java -jar Zeus-49.jar -hZeus

java -jar Zeus-49.jar style -h - show HELP about check-style command

java -jar Zeus-49.jar style — local run zeus style — Google Cloud Shell run

• java -jar Zeus-49.jar test jcb -w0 -d4 — run all tests of the week0 day4
• java -jar Zeus-49.jar test jcb -w0 -d4 --debug — run all tests of the week0 day4 in debug mode
• java -jar Zeus-49.jar test jcb -w0 -d4 -v — run all tests of the week0 day4 with long error's stack trace
• java -jar Zeus-49.jar test jcb -w0 -d4 -i0 — run only first test class of the week0 day4
• java -jar Zeus-49.jar test jcb -w0 -d4 -i1 — run only second test class of the week0 day4

jcb — tells Zeus which course to run tests from.

java -jar Zeus-49.jar test jcb -w0 -d4 -i1 -v — run only second test class of the week0 day4 END show extra-long error messages

zeus test jcb -w0 -d4 -i1 -v — the same, but in Google Cloud Shell

-v — special kay for test command, more verbose

java -jar Zeus-49.jar pass jcb - starts a code style check for the entire project, and then starts testing the entire project

java -jar Zeus-49.jar pass jcb -w0 -d4 -i0 - starts first checking the code style of the entire project, and then runs the tests specified: week0, day4, test class1

zeus pass jcb -w0 -d4 -i0 - the same, but in Google Cloud Shell