Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 11 of 11
  1. #1
    New Coder
    Join Date
    Apr 2013
    Posts
    14
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Why do professionals talk so much about debug time?

    After learning java for a couple years now, I haven't ever had the issue of tremendous amounts of debugging time. Is this something that will come in time or do people just exaggerate? Are they talking more so about logic errors and how long it takes to spot them? Thanks

  • #2
    Senior Coder
    Join Date
    Aug 2006
    Posts
    1,295
    Thanks
    10
    Thanked 282 Times in 281 Posts
    I suspect you mean *testing* time, of which fixing bugs is a small piece. A comprehensive test plan on a large application can be quite the effort.

  • #3
    New Coder
    Join Date
    Jan 2013
    Location
    Canada
    Posts
    27
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Either that or what is called "unit testing," otherwise debugging manually can still be really time consuming, especially with black box testing.
    Microsoft MVP .NET Programming - (2012 - Present)
    ®Crestron DMC-T Certified Automation Programmer & Software Developer

  • #4
    Master Coder felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, Australia
    Posts
    6,642
    Thanks
    0
    Thanked 649 Times in 639 Posts
    Debugging time should be really small provided that sufficient time was spent on testing.

    Debugging is the process of finding the errors in the code that you missed finding during testing.
    Stephen
    Learn Modern JavaScript - http://javascriptexample.net/
    Helping others to solve their computer problem at http://www.felgall.com/

    Don't forget to start your JavaScript code with "use strict"; which makes it easier to find errors in your code.

  • #5
    New Coder
    Join Date
    Jan 2013
    Location
    Canada
    Posts
    27
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by felgall View Post
    Debugging time should be really small provided that sufficient time was spent on testing.

    Debugging is the process of finding the errors in the code that you missed finding during testing.
    "Debugging is the process of finding the errors in the code that you missed finding during testing." - That is not true, during your testing you may find bugs that need to be debugged to figure out what is causing the problem. You can't fix a bug just by testing, so they go hand in hand. Debugging is simply just the process of using the debugger..

    Debugging time is not guaranteed to be small either, and especially for larger projects because there is a lot more to consider when trying to figure out what might be causing a particular problem. Depending on the complexity of the fix, this may introduce more testing and debugging as well.

    Testing may provide hints as to where you should start debugging, but that won't mean debugging will be an easy task after plenty of testing necessarily. Debugging can still be a time consuming adventure regardless.
    Microsoft MVP .NET Programming - (2012 - Present)
    ®Crestron DMC-T Certified Automation Programmer & Software Developer

  • #6
    Master Coder felgall's Avatar
    Join Date
    Sep 2005
    Location
    Sydney, Australia
    Posts
    6,642
    Thanks
    0
    Thanked 649 Times in 639 Posts
    Quote Originally Posted by AceInfinity View Post
    "Debugging is the process of finding the errors in the code that you missed finding during testing." - That is not true, during your testing you may find bugs that need to be debugged to figure out what is causing the problem. You can't fix a bug just by testing, so they go hand in hand. Debugging is simply just the process of using the debugger.
    The errors you find and fix during testing are a part of the normal testing process. For it to be debugging implies that the code has already passed testing and is live. You will probably find lots of errors that need fixing during the testing process but they are not bugs unless they are still there once the code goes live.

    There should be a lesser requirement to search for where the error is during testing than there is for locating a bug as the test that produces the error should be testing a specific section of the code and so most of the time the cause of the error will be in that particular section of code whereas a bug could be anywhere and so the first step in debugging is to try to locate the portion of code it is in.

    The process for fixing errors found during testing is similar to but not identical to the process you use for debugging. With debugging you have the additional time constraint that it needs to be fixed yesterday and so the solution is often to apply a patch that would be completely unacceptable had the error been found during testing. During testing there is more time available for fixing and so it can be fixed properly instead of just being patched.

    You can use the debugger using testing and you can debug without using the debugger. That it is called a debugger does not mean that it can only be used for debugging.
    Stephen
    Learn Modern JavaScript - http://javascriptexample.net/
    Helping others to solve their computer problem at http://www.felgall.com/

    Don't forget to start your JavaScript code with "use strict"; which makes it easier to find errors in your code.

  • #7
    New Coder
    Join Date
    Jan 2013
    Location
    Canada
    Posts
    27
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by felgall View Post
    Debugging time should be really small provided that sufficient time was spent on testing.

    Debugging is the process of finding the errors in the code that you missed finding during testing.
    Quote Originally Posted by felgall View Post
    The errors you find and fix during testing are a part of the normal testing process. For it to be debugging implies that the code has already passed testing and is live. You will probably find lots of errors that need fixing during the testing process but they are not bugs unless they are still there once the code goes live.

    There should be a lesser requirement to search for where the error is during testing than there is for locating a bug as the test that produces the error should be testing a specific section of the code and so most of the time the cause of the error will be in that particular section of code whereas a bug could be anywhere and so the first step in debugging is to try to locate the portion of code it is in.

    The process for fixing errors found during testing is similar to but not identical to the process you use for debugging. With debugging you have the additional time constraint that it needs to be fixed yesterday and so the solution is often to apply a patch that would be completely unacceptable had the error been found during testing. During testing there is more time available for fixing and so it can be fixed properly instead of just being patched.

    You can use the debugger using testing and you can debug without using the debugger. That it is called a debugger does not mean that it can only be used for debugging.
    "You can use the debugger using testing and you can debug without using the debugger. That it is called a debugger does not mean that it can only be used for debugging." - But this was already my point.
    Microsoft MVP .NET Programming - (2012 - Present)
    ®Crestron DMC-T Certified Automation Programmer & Software Developer

  • #8
    New Coder
    Join Date
    Apr 2013
    Posts
    14
    Thanks
    0
    Thanked 0 Times in 0 Posts
    sorry for posting so late, thanks. I understand what you mean: I was confused and mixed debug time with compile time.

  • #9
    Regular Coder Nerevarine's Avatar
    Join Date
    Jan 2013
    Location
    Phendrana Drifts, Tallon IV, W-Class
    Posts
    285
    Thanks
    0
    Thanked 17 Times in 17 Posts
    Blog Entries
    3
    Compile time: Ugh. Compile time is "Do whatever you want for a few hours" time.
    Time kills us in our sleep and we watch it happen in our dreams. -K.K.
    THE END-ALL PROGRAMMING REFERENCE: CLICK HERE (Courtesy of Major Payne)
    My username was previously L0adOpt1c. :: Please read this before posting in the HTML/CSS forum.
    Validate your HTML here and your CSS here. :: Need basic HTML/CSS tutorials? Click here, don't post about it.

  • #10
    New Coder
    Join Date
    Apr 2013
    Posts
    14
    Thanks
    0
    Thanked 0 Times in 0 Posts
    haha that's the second best part!!

  • #11
    New Coder
    Join Date
    Oct 2013
    Posts
    12
    Thanks
    0
    Thanked 0 Times in 0 Posts
    debuging is great technique to find and remove the error in the code. so which really helpful in creating and designing the sites. so that's why the professional take look about the debug time. it's also know as testing which they made in prgramming. the manual debuging can take a bit time. that's why the professionals are interested in it cause of their work and quality of their work.


  •  

    Tags for this Thread

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •