git-tester VS redis-tester

Thanks for the ideas — you're right that automating the UI-oriented testing is more difficult. We're already piloting some ideas in this area (e.g Build your own React) — but the current focus is on perfecting what we have.

Our testers are all OSS. Here's our git tester for example — https://github.com/codecrafters-io/git-tester.

Others can be found on our GitHub org.

Thanks for the great question. We support ~14 languages at the moment and are working on adding more. You can visit our tracks page (https://app.codecrafters.io/tracks) to see the courses available against each language.

As a 2-person team, we're prioritising making a complete experience for Go, Python & JS for starters (our most popular languages).

So far, our tests are language agnostic. Our testers are written in Go (they’re open source, example: https://github.com/codecrafters-io/redis-tester). The testers interact with user code by testing for observable behaviour - exit codes, stdout/stderr, files written etc.

Although the testers are language-agnostic, a lot of the educational “content” is language-specific. We emit language-specific hints in stages where appropriate, and have expert solutions that are language-specific. A lot of this is new, so we might not have coverage across all challenges - this will improve over time.

Does that help explain our setup a little better?