Hein Meling
Hein Meling
We could also provide a notification to students that their committed push did not trigger any test execution of a known assignment. This is sometimes relevant when a change is...
Once we've implemented #1409 this type of notification would become somewhat irrelevant, since GitHub would show that their repository is behind the `assignments` repository.
Low-hanging fruits implies that we should fix the ones that gives the most bang for the buck (as in time invested). Not 100 % score!
While fresh in my memory, let me add that we could pre-run some variant of the following command for every update/push to the `tests` repository. Let me name the script...
This is how I imagine this working. When I run tests locally, like this: ```sh go test -tags solution -run TestGorumsPaxos_ ``` It already produces this: ```json {"TestName":"TestGorumsPaxos_ClientQSpec","MaxScore":1,"Weight":20} {"TestName":"TestGorumsPaxos_ClientHandleQF","MaxScore":7,"Weight":20} {"TestName":"TestGorumsPaxos_FiveReplicas","MaxScore":1,"Weight":50}...
I think the table should be left-aligned, next to the back-arrow.
We should do this.
We should revisit this in the context of recent updates related to `tests.json`. There is also some interesting new things coming in the [testing package in Go 1.25](https://tip.golang.org/doc/go1.25#testingpkgtesting).
@JosteinLindhom This looks useful and we should bring over the finishing line.
Key point that we may want to avoid: Leaderboard. I'm mentioning because it is bound to come up, since it may not be conducive to a good learning environment.