In Java, the type Integer is considered as deprecated and for removal :
src/test/java/TipCalculatorTest.java:8: warning: [removal] Integer(int) in Integer has been deprecated and marked for removal
assertEquals(new Integer(2), TipCalculator.calculateTip(30d, "poor"));
Duplicate?
Remove those silly arguments checks. If you do keep them in for some reason, change the return type. We now have mixed return types :/
Java fork (author inactive)
Integer
constructor, which triggers deprecation warnings (fixing this issue)In Java, the type Integer is considered as deprecated and for removal :
src/test/java/TipCalculatorTest.java:8: warning: [removal] Integer(int) in Integer has been deprecated and marked for removal
assertEquals(new Integer(2), TipCalculator.calculateTip(30d, "poor"));
Needs random tests
This comment is hidden because it contains spoiler information about the solution
Needs random test cases