https://github.com/petertseng/adventofcode-common

Common test runner and utility scripts for https://adventofcode.com, not specific to any particular year
https://github.com/petertseng/adventofcode-common

advent-of-code

Last synced: 17 days ago
JSON representation

Common test runner and utility scripts for https://adventofcode.com, not specific to any particular year

• Host: GitHub
• URL: https://github.com/petertseng/adventofcode-common
• Owner: petertseng
• License: apache-2.0
• Created: 2019-12-15T22:52:11.000Z (about 5 years ago)
• Default Branch: master
• Last Pushed: 2024-11-26T11:42:29.000Z (2 months ago)
• Last Synced: 2024-11-26T12:22:00.853Z (2 months ago)
• Topics: advent-of-code
• Language: Ruby
• Homepage: https://adventofcode.com
• Size: 22.5 KB
• Stars: 0
• Watchers: 3
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Advent of Code common

## Test runner

Common test runner for Advent of Code, since I have many solutions in different years and different languges.

**No test inputs are provided in this repo**, by the request of the Advent of Code team.

While the act of publicly posting inputs is [not actively discouraged](https://www.reddit.com/r/adventofcode/comments/e7khy8/are_everyones_input_data_and_by_extension/faofziv/), it is still [preferred](https://www.reddit.com/r/adventofcode/comments/e9p81a/advent_of_code_in_a_different_language_every_day/fal59uy/) that we do not do it.

Therefore, to use this test runner, you will have to provide it your own test cases.

I considered only posting sample inputs (provided in the problem statements publicly to all players, not to any one specific player) in this repo, and then I'd be able to publicly demonstrate (via Travis CI) that my solutions work on those sample inputs, but I considered this not worth it, and also potentially in violation of the team's wishes, since there definitely is an edict against posting puzzle statements.

Expected test format:

Place tests in directory matching this form: {sample,secret}-cases/20??/

In any such directory:

* Tests for a day start with the zero-padded day number, then any arbitrary string afterward.

* An input file ending in .in may be given, or argv arguments may be given in a file ending in .argv.

  If both are provided, the test runner will treat the two as a single test, passing both the file and the arguments.

* Corresponding output file ends in .out.

For example a test might be sample-cases/2015/01a.in and sample-cases/2015/01a.out