[grade-school] a student can't be in two different grades test

I think the test means that a name can only be accepted in one grade and prevent duplicates. so typescript school.add('Aimee', 2) school.add('Aimee', 1) should prevent the second add while accepting the first one (because it is not a duplicate) . However the test expects an empty array : expect(school.grade(2)).toEqual([])
I think it is not a real use case to delete the first entry when a duplicate is being added. what do you think ?

You are correct. This has been fixed in problem specifications uuid 6a03b61e-1211-4783-a3cc-fc7f773fba3f but the typescript tests have not been updated.

this seems still open…

line 92 should be
expect(school.grade(1)).toEqual([])
instead of
expect(school.grade(2)).toEqual([])

is the patch as simple as this? or are there more hidden implications?

No it’s not. The tests should be in sync with the problem specs, and this probably means changes in a lot of places.

@tasx i might have been way too optimistic :-(
is there a guide/doc for developers/supporters you could point me too to help out?
in previous exercises on TS track i believe i have experienced couple more of these oddities and would like to help.

This is also an issue in the Javascript track.

This appears to still be an issue on the TypeScript track. The instructions state “If a test attempts to add the same student more than once, your implementation should indicate that this is incorrect.” but the test expects later additions to take precedence.

Yup. The track has some exercises that are out of date and need maintainer syncing.

It looks like Grade School was synced last year for JavaScript per Update tests grade-school by jagdish-15 · Pull Request #2747 · exercism/javascript · GitHub. @SleeplessByte, if you’d like, I can sync the Grade School tests for TypeScript. There’s a couple of reimplemented tests to watch out for from what I recall.