Python example tests are not fixed: it's still using Test and Find_ways.

Should we follow the Java method naming conventions then?

yes looks like issue with double precision (your solution differ with <=1 e.g. test solution is 37711260989l and yours is 90l)

once try with double m and double n

Same

It is very similar to number partition problems , isn't it? There are already lots of katas related with standart partition problem.

I'm getting slight errors on the larger test cases for Java. I passed all the tests using the same approach with python, so either I'm missing some quirk in using longs or some of the Java test cases are off.

plz do check and approve if you like the java translation of this kata by me

Also, you might have to resubmit your solution, sinnce i fixed the 0 case.

Yeah, sorry.. Wasn't thinking right

According to the tests Find_ways(27, 0) should return 1 but is there really a way that zero numbers can be summed to 27?
In the description you talk about A and B. In the initial solution you use m and n.
Please use snake_case for function names in Python, i.e. find_ways instead of Find_ways. See Kata Best Practices.
Please add randomized tests. See the Python Test Suite Best Practises.

Ok, I've tried converting this program to python 3.4.3, for user convinience

Umm... I'm having trouble turning the FindWays (camelCase) to Find_ways, even though I keep refreshing. What should i do?

Yeah srry.. I've been learning a new language, and still having trouble switching back