Exercism GDScript Track

Exercism exercises in GDScript.

Testing

There are two options for iterating over all exercises to see if their exemplar/example implementation passes all the tests. Option B also allows single-exercise verification and overriding which Docker image to use for the test runner.

Option A: Via local godot

To set up for testing, clone https://github.com/exercism/gdscript-test-runner and move its contents to /opt/test-runner:

git clone https://github.com/exercism/gdscript-test-runner.git
sudo mkdir -p /opt/
sudo mv gdscript-test-runner/ /opt/test-runner/

To test the exercises, run godot --headless -s bin/verify-exercises.gd from the present repo's root (not the gdscript-test-runner repo root).

Option B: Via docker

The docker verifier is included in the present repo, just run this from its root:

bin/verify-exercises-in-docker

If you want to verify a single exercise:

bin/verify-exercises-in-docker two-fer

If you want to verify all exercises against a specified test runner:

bin/verify-exercises-in-docker -i my-local-image

This allows maintainers to preview upgrades to the test runner.

Track linting

configlet is an Exercism-wide tool for working with tracks. You can download it by running:

./bin/fetch-configlet

Run bin/configlet lint to verify if all exercises have all the necessary files and if config files are correct. Run configlet fmt to check formatting.