Failed test cases or “Wrong answer” status

Causes

Possible Resolution(s)

Mismatch of input and output values

Test cases fail when the input passed by your code may not be in the exact format as expected by the test case. Also, when the output returned by your code is not the exact expected output format, you will see a "Wrong answer" status.

• When you write your own programs, ensure that you've understood the expected input and output values. 

Causes

Possible Resolution(s)

Question comprehension -handling edge cases

If some of your Test cases have passed, but you see a "Wrong Answer" status for others, it may imply that your coding logic is unable to handle the corner cases expected from the solution. For example, test cases that validate boundary values may fail if you have not written the logic to check for boundary values.

• Your understanding of the question and the expected solution may differ. A problem can have multiple solutions, but your logical solution must be based on the given constraints in the question.

• Debug your code and validate different corner cases with custom inputs.

• Ensure that you have understood the expected solution and the various constraints explained in the problem statement. Modify your program or coding logic accordingly.

Causes

Possible Resolution(s)

Issues with code formatting or package guidelines

Check for other issues in your code, such as:

1. Extra/missing whitespaces

2. Newlines

3. Debug output values printed in the "Your Output" area. After debugging, you must remove or comment on your debug print statements in code.

4. Incorrect Class or Package names - (For Java, Scala, and Clojure projects, ensure that the correct naming guidelines are followed for Classes and Packages. This is required for your code to run and execute the test cases).