You are modifying the original values in the dictionary, upon computing the summation, it will take into account unnecessary values in the previous iterations

OP solved it, closing

{'Cameron': 30}
'Cameron' should equal 'all'

{'Geoff': 30} this is ok in tests.

Maybe I misunderstood something, but why sometimes case with one student should equal name of this student and sometimes it should return "all"?

I need help with this one. My NASM fails the random tests.

I went and did it in C and I managed, but still my NASM seems to choose at random.

Interesting challenge.

@boandli is definitely onto something, I came here to report the same. The current problem statement requires "all" for 1 student, but the tests say otherwise. His post isn't labelled as an issue, so I'm raising it separately.

• Ruby 3.0 should be enabled (Refer this & this for more detail)

My JS solution passes the Basic Tests and then I get something like:

expected 'Ashley' to equal 'Charles'

for the Randoms. I'd appreciate clarification on this output. Thanks.

Please use new python test framework.

Why is this an OOP problem?

Fixed JS.

The problem is the random tests (at least in javascript, remember to mention the language when reporting an issue in a kata that has several languages) generate more than one student with the same name. So this:

Each student will have a unique name

isn't true;

This task definetely has a problem. My solution passed the test, and then failed with error kind of "expected Michael, but got Abram". (By the way, it's way too small information to solve the problem). But wonder is: then attempt was good without any changes in solution. I think, it should not be.