Drop input validation (negative values).

Tests crash when run with initial solution.

Running the initial solution (or indeed any solution which returns a non-numeric value) reveals the solution to the user in the stack trace.

Reraising: random tests have bare assertions inside a describe

Random test code is extremely bizarre and should probably be modified:

• 25 tests is not a lot
• Shuffling a set of already randomly generated inputs achieves nothing
• Why are you even building a list via appending (or even building a list of cases at all), just run the tests as you generate them

Kata cannot be passed since there's no assertion done when all of the results are correct.

You should use test.assert_approx_equals instead, or add else statement containing test.pass_() in the assert_almost_equal function.

Whatever formula you're using is clearly incorrect anyway, as it gives negative area at alpha >= 37.83.

Also, why suddenly use angle in degrees in this kata? You used angles in radians in the previous kata. It seems that your katas are inconsistent with themselves.

The title "should return '12' for (0, 2)" is incorrect, and very misleading.

• There is no random tests. Codewars kata need to have random tests.
• Missing tests for cases like a, a+1.