I was looking into syncing the Kotlin track, but a lot of the exercises seem to still use the v2 format for tests.toml and reports a lot of missing tests that aren’t actually missing.
What would be the way to go about syncing the Kotlin track?
Should the exercises be synced individually?
Should all of the formatting issues be resolved at once, then sync the tests that are actually missing after the formatting is updated?
That’s a question for the track maintainer. Generally if you’re applying a bunch of minor, simple changes (eg formatting), it can make sense to apply them to multiple exercises at once. If you’re changing the tests (eg adding new ones) it’s usually best to make one PR per exercise. It’s a balance between a ton of small PRs vs PRs that are too large. Large PRs are difficult to review and manage.
It’s generally best to fix any warnings before other changes. This makes it easier to ensure your other changes aren’t breaking any checks.
From past experience on other older tracks, I’d go exercise by exercise. You need to first verify that the tests.toml file still accurately represents the test suite and there’s been no significant divergence. Individual PRs makes it easier to track progress through the track, and if tests for an exercise need to be updated, you can do it at the same time. configlet sync --tests include -uye <slug> updates the tests.toml as a first step and then you just cross-reference the toml against the tests. If additional tests need to be added, it’s easy enough to look up the canonical data, but you may also need to update the example. I imagine it might be best to leave those exercises as draft PRs and then fix all the examples in one go at the end.
You could knock out an individual exercise pretty quickly, and doing single-exercise PRs means you can coordinate with others. For example, I was in that repo the other day flagging some tomls that didn’t actually need additional tests added.