Enabling the Roc track for testing?

I think the Roc track is almost ready, it has 27 practice exercises, a test runner, the snippet-extractor, cli, and tokei now support Roc, and automation is setup, the documentation is ready, and I asked for a logo.

  • Could the site admins please enable this track for testing?
  • Would any track maintainers be interested in testing this new track?
1 Like

I’ll be happy to test the track.

Some trivial feedback:

Consider increasing the difficulty of

  • flatten-array
  • house
  • luhn
  • wordy

to be in the range 4…7 (Medium), instead of 1…3 (Easy).

A typo in docs/TESTS.md :

If you’ve solved the exercise, you should see 0 failed test
=>
If you’ve solved the exercise, you should see 0 failed tests

1 Like

Tada: https://exercism.org/tracks/roc!

3 Likes

Thanks for your feedback @keiraville, I’ll fix these issues asap.
And thanks for enabling the track for testing @ErikSchierboom , I’m stoked! :star_struck:

2 Likes

roc/config.json at 37c1f5007e1306c04b25da65448d1554cdd1272c · exercism/roc · GitHub needs to be set to true otherwise we can’t open the online editor.

Before launch, exercise difficulties should be adjusted globally like keiraville mentioned. You can probably source difficulties from a similar track as a starting place, but this quickly becomes more of an art than a science. The important thing is that levels 1 - 3 are displayed on the site as easy, 4 - 7 medium, and 8 - 10 hard. The student won’t be able to distinguish level 1 from 2 at a glance.

Related to that, you probably want to sort the exercise list in the config because that affects how the student sees the exercises on the website. Some tracks sort alphabetically regardless of exercise name, some by actual difficulty level (1 - 10) and then alphabetically within each level, and others by displayed difficulty group (easy, medium, and hard) and then alphabetically in each group. There are pros and cons to each approach.

There’s also a minor typo in roc/config.json at 37c1f5007e1306c04b25da65448d1554cdd1272c · exercism/roc · GitHub where it should be “Roc is works well”.

2 Likes

I’ve set test_runner to true, and I’ve set the exercise difficulties, and sorted by (difficulty, name), making sure that Hello World comes first.
I’ve also fixed the typos.
Thanks everyone! :pray:

Hello :slight_smile:

One key thing to mention is that now the track is syncing with the website, changing any UUIDs is a very bad thing. So please ensure that that doesn’t accidently happen during your work.

Thanks for all you’re doing! :blue_heart:

Hi Jeremy,
Gotcha, I’ll make sure that doesn’t happen. :+1:

2 Likes

I’ve started testing the track, it’s really nice! One little issue is the fact that there’s no syntax highlighting in the online editor. I’ll look into this.

1 Like

A few Roc devs would like to test the track. Could you please add them to the list of testers? Their github logins are: isaacvando, smores56, and bsassoli.
Thanks

You should be able to find both ways of syntax highlighting via Enable syntax highlighting | Exercism's Docs.

Congrats on the new track!

2 Likes

I just added bsassoli to the list of Roc devs who would like to test the Roc track. Thanks

The links in roc/docs/RESOURCES.md at main · exercism/roc · GitHub
aren’t proper Markdown for URLs so they’re rendered as text instead at https://exercism.org/docs/tracks/roc/resources. The other docs appear correct.

Otherwise, I’ve done 7 exercises so far, and things look pretty decent. Good job :slight_smile:

1 Like

Thanks @BNAndras , I just fixed the RESOURCES.md issue.

Btw, could you please confirm when the Roc devs above have been added to the list of testers of the Roc track? And if it’s not too much to ask, could you please set syntax highlighting for the online editor to Elm? Roc’s syntax is quite similar to Elm’s. :pray:

1 Like

We can’t just add them as testers (we have no such concept). The only way in which this can be done is to make those devs part of the Roc team on github. Do you want that?

(I would recommend you doing this if they are going to help you out, even if it’s just testing and giving feedback. It’s relative easy to kick them out when no longer necessary)

I’m fine with adding them to the team BTW, just want to confirm they’re okay with it (they’ll get notifications by default). If they are okay with it, please have them create Exercism account and make sure they link their account to GitHub (update/check at Exercism).

Thanks @ErikSchierboom. All three have confirmed that their Exercism account is connected to GitHub, and they all agreed to be added to the Roc team on GitHub. Their Exercism logins are: isaacvando, smores56, and bsassoli.

I suggest at this stage adding branch protection, @ErikSchierboom.