Where the crane is at first should be mentioned.
Should we follow the Java method naming conventions then?
All the preloaded stuff should be in the fixture.
New test framework should be used.
Fixed tests should contain edge cases: empty boxes, operations without 0, operations with non-final 0.
boxes
operations
0
What's the point in returning a string rather than a list?
The function name should be in snake_case in Python.
snake_case
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
Thanks. Approved.
thank you :)
Looks OK. Will approve.
thank you for your help....changes made now it will return int[] plz approve if u like it
You should use
import static org.junit.Assert.assertArrayEquals;
it was giving issues in test class when comparing ...so i decided to convert that array to string
Loading collection data...
Where the crane is at first should be mentioned.
Should we follow the Java method naming conventions then?
All the preloaded stuff should be in the fixture.
New test framework should be used.
Fixed tests should contain edge cases: empty
boxes
,operations
without0
,operations
with non-final0
.What's the point in returning a string rather than a list?
The function name should be in
snake_case
in Python.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
Thanks. Approved.
thank you :)
Looks OK. Will approve.
thank you for your help....changes made now it will return int[]
plz approve if u like it
You should use
it was giving issues in test class when comparing ...so i decided to convert that array to string
Loading more items...