This kinda defeats the purpose, but still the right call nonetheless

Ok, thank you. At least now I know where the problem lies. So it's supposed to test how many points Tottenham has. But how would you know this without having solved the kata in the first place?...
Copying my code to an editor and running it with

lt = LeagueTable.new
lt.push("Tottenham 4 - 1 Sunderland")
puts lt.get_points("Tottenham")

gives me 3, not 4 however...

My get_points method is

def get_points(team_name)
    sum = 0
    for match in @matches
      if match.values.max != match.values.min  # someone won
        if match[team_name]==match.values.max
          sum += 3
        end
      else  # draw
        sum += 1
      end
    end
    sum
  end

where matches consists of hashes like {"Tottenham" => 4, "Sunderland" => 1} representing a single match.

Test.assert_equals(lt.get_points("Tottenham"), 3, "Nope!")

My code fails a test under the heading "Totenham should now have 4 goals for":

Nope! -  Expected: 3, instead got: 4

right after the test

Test Passed: Value == 4

What is this second test supposed to check? Is the heading maybe missing some information as it seems to check something more than just how many goals Totenham has? The stderr log just gives

/runner/frameworks/ruby/cw-2.rb:60:in `block in describe': Nope! -  Expected: 3, instead got: 4 (Test::Error)
	from /runner/frameworks/ruby/cw-2.rb:46:in `measure'
	from /runner/frameworks/ruby/cw-2.rb:51:in `describe'
	from /runner/frameworks/ruby/cw-2.rb:202:in `describe'
	from main.rb:131:in `block in <main>'
	from /runner/frameworks/ruby/cw-2.rb:55:in `block in describe'
	from /runner/frameworks/ruby/cw-2.rb:46:in `measure'
	from /runner/frameworks/ruby/cw-2.rb:51:in `describe'
	from /runner/frameworks/ruby/cw-2.rb:202:in `describe'
	from main.rb:91:in `<main>'

you're actually returning a new string object here, while the problem description is asking you to return the same string in a mutated form.
You can simply add '!' to do that.
Nice solution though!

Great kata.

Noice kata!

I swear I mean that in the nicest way possible. Generally not good to inherit from Hash, but this solution is super clever.

gross. I love it.

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

Why choosing a class name that may conflict with a built-in class?

• JS Node 12. should be enabled

• Python new test framework should be used

• Ruby 3.0 should be enabled

isnt there any correct output example ?

'Non-linear sequence' should be tested in sample tests