Have Geek Brain

Debug Test Required Suggestions

I have a debug test as part of the interview .. I was thinking if someone can help with this approach when I am faced with a large codebase and have to find bugs inside this within an hour or two. This will be a Java core based application (I think) on Eclipse 3.2+

+2


a source to share


4 answers


The answer that the interviewer probably observes is "what's your overall strategy?" You'd better have an approach that makes sense to him or her. This is the general approach that I recommend for debugging (whether or not it is for a test):



  • Recover the error, document additional results as you go.
  • Bonus points for writing unit test for automatic error recovery.
  • Is it a crash or a misbehavior to categorize a mistake? Your analysis will probably be different.
  • Confirm the debug / logging level as soon as shown.
  • Look for log files / artifacts that the application may have generated to help troubleshoot the problem.
  • Preview through probable code, look for anything suspicious.
  • Take a divide and conquer approach. Use a crude binary search to determine where the code is working and where it is not working. Perhaps use breakpoints or print statements. In the meantime, there is no need to worry about it. ”
  • After you find it, add unit test cases to narrow it down explicitly.
  • Add documentation to explain what you found, comments in the unit test code would be great.
  • Correct mistake. Remarks on the fix would be good too.
  • TRY YOUR CORRECTION. Test it logically, methodically (boundary conditions, etc.).
  • When this is done, ask the interviewer to review your bug fixing code.
+2


a source


Not a complete answer, but you can use methods for remote debugging as well

alt text



This can help you find errors when you don't have a complete Eclipse project, but only an external application (with its sources) that will crash.

+2


a source


I hate to say this, but if you don’t know how to approach this problem yet, there’s a good chance you don’t have the level of experience / experience they need. Trying to learn between now and the interview probably won't help much.

On the positive side, you have already reached the detailed interview stage and this is a good sign. And despite your problems, you may well already be reaching your minimum level of debugging experience / skill ... or your other attributes may be sufficient to get the job done.

+2


a source


Let me know how it goes. Sounds complicated. I guess I would say that you know how to get a pile off your head.

0


a source






More articles:


All Articles