There is a test which creates a cube with value 2, then it sets c.Side = 3;, and checks if volume is 27. That means your code isn't updating the values accordingly. Overall this doesn't seem like a kata issue, so I'll close it.

@auvsexvc true but once 7kyu fails on this part, only way to recover is to console log init, getters, setters Side values as while test is ok, it checks for 2 different property Side setter. I couldn't recover from this.

Nothing wrong withe a Kata. Your code is just wrong. Return the right value for v and s prop.

I have this problem too. Do you have solution for this?

I have the same problem.
Language is c#

even simple test case of 121111111 would knock it out but none of them were made to catch simple brute force loops

C# issue: currently function expects (int[,] input), while actually it should be (string[][] input). For 7kyus this might cause issues.

It's has some odd test case. It passes side 2 value but expects result of value 3.
(Volume should be 27, Expected: 27, But was: 8)
(Volume should be 54, Expected: 54, But was: 24)
Through the console output I see that passed value was indeed 2 and not 3. Though if I destroy my algo to get answers it wants suddenly it expects correct result so I can't pass neither way.