This project contains my solutions for the Advent of Code 2016 in Kotlin. Advent of Code is an Advent calendar of small programming puzzles by Eric Wastl.
- Day 1: ๐ No Time for a Taxicab -- Day1.kt
- Day 2: ๐พ Bathroom Security -- Day2.kt
- Day 3: ๐บ Squares With Three Sides -- Day3.kt
- Day 4: ๐ช Security Through Obscurity -- Day4.kt
- Day 5: โ๏ธ How About a Nice Game of Chess? -- Day5.kt
- Day 6: ๐ฃ Signals and Noise -- Day6.kt
- Day 7: ๐ป Internet Protocol Version 7 -- Day7.kt
- Day 8: ๐ Two-Factor Authentication -- Day8.kt
- 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
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
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.
- Inputs go into
src/main/resources
and follow the naming conventioninput_day_X.txt
- Solutions go into
src/main/kotlin/days
and implement thePuzzle
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 inDay1
with your own