Advent of Code 2022

This project contains solutions to the Advent of Code 2022 challenge in Kotlin. Advent of Code is an Advent calendar of small programming puzzles by Eric Wastl.

Solutions

• Day 1: 🍪 Calorie Counting -- Day1.kt
• Day 2: ✂️ Rock Paper Scissors -- Day2.kt
• Day 3: 🎒️ Rucksack Reorganization -- Day3.kt
• Day 4: ⛺️️ Camp Cleanup -- Day4.kt
• Day 5: 📦 Supply Stacks -- Day5.kt
• Day 6: 📱 Tuning Trouble -- Day6.kt
• Day 7: 💾 No Space Left On Device -- Day7.kt
• Day 8: 🌳 Treetop Tree House -- Day8.kt
• Day 9: 📿 Rope Bridge -- Day9.kt
• Day 10: 📺 Cathode-Ray Tube -- Day10.kt
• Day 11: 🙈 Monkey in the Middle -- Day11.kt
• Day 12: ⛰ Hill Climbing Algorithm -- Day12.kt
• Day 13: 📦 Distress Signal -- Day13.kt
• Day 14: ⏳ Regolith Reservoir -- Day14.kt
• Day 18: 🍩 Boiling Boulders -- Day18.kt
• Day 23: 🌱 Unstable Diffusion -- Day23.kt
• Day 24: 🌨 Blizzard Basin -- Day24.kt
• Day 25: 💯 Full of Hot Air -- Day25.kt

Features

• Gradle setup so you can run a specific day or all days on the command line (see Running)
• Timings for each part of each day
• Input for each day automatically exposed in String and List form
• Junit 5 and AssertJ test libraries included (see ** Testing**)
• Starter .gitignore

Running

Project is already setup with gradle. To run the app:

• Navigate to top-level directory on the command line
• Run ./gradlew run to run all days
• Run ./gradlew run --args $DAY where $DAY is an integer to run a specific day
• Run ./gradlew run --args "$DAY1 $DAY2 $ANOTHERDAY" to run a subset of days

Testing

Project includes JUnit and AssertJ and a stub unit test to get you going. To run all tests:

• Navigate to top-level directory on the command line
• Run ./gradlew test
• Add --info, --debug or --stacktrace flags for more output

By default, instantiations of Day classes in tests will use the input files in src/test/resources, not those in src/main/resources. This hopefully gives you flexibility - you could either just copy the real input into src/test/resources if you want to test the actual answers, or you could add a file of test data based on the examples given on the Advent of Code description for the day. The stub Day1Test class shows a test of the functionality of Day1 where the test input differs from the actual input.

Architecture

• Inputs go into src/main/resources and follow the naming convention input_day_X.txt
• Solutions go into src/main/kotlin/days and implement the Puzzle interface
• Solutions follow the naming convention DayX
• It is assumed all solutions will have two parts
• It is assumed that the puzzle input is provided through the primary constructor
• You can use the InputReader methods for reading input
• To get started simply replace src/main/resources/input_day_1.txt with the real input and the solutions in Day1 with your own