Test

In the question you already have a good definition about testing. It has a broader definition in Tests, TDD, Unit Test, QA, and the like. What's different about test concepts? .

So we can conclude that it is a measure to ensure quality. You verify that the software is compliant.

It is a development process as a whole. Testing lasts throughout the project lifecycle.

New tests are desirable. If a problem is detected by other means (a debugging, for example), a test to ensure that the problem does not recur is desirable.

Tests are done with specific tools that automate the process and codes that have the function of saying if something very specific generating the expected result or not.

The concern is with the result, not how you got there.

Debugging

Debugging is a process of repairing something that is known to be broken.

In general, it is punctual for a defect.

Often the process starts because a test detected that there is a defect.

It is something that simulates step by step execution manually, to find the reason for the problem and determine what needs to be changed to solve it.

In general it is done with the help of additional tools or extra code to determine what is happening and in the end when the problem is solved it is thrown away.

Focus is the detail of the execution, there is a concern with the algorithm and state changes.

  

Everyone knows that debugging is twice as difficult as writing a program in the first place. So, if you're as smart as you can, when you write it, why are you going to debug it?

     

- Brian Kernighan

What I would really like is that people who decide to learn to learn at least the basics of debugging, which helps to understand a little better what is being done. At times that "programming" seems to be copying ready codes and filling in gaps without understanding what you're doing, debugging seems like something unnecessary. Luckily we still have professionals interested in doing their best and understanding the whole process.