Categories:
.NET (357)
C (330)
C++ (183)
CSS (84)
DBA (2)
General (7)
HTML (4)
Java (574)
JavaScript (106)
JSP (66)
Oracle (114)
Perl (46)
Perl (1)
PHP (1)
PL/SQL (1)
RSS (51)
Software QA (13)
SQL Server (1)
Windows (1)
XHTML (173)
Other Resources:
Why Not Just Use a Debugger for Unit Testing?
Why Not Just Use a Debugger for Unit Testing?
✍: FYICenter.com QA Team
This is a common question in a job interview. You should answer it with these points:
Here is how the JUnit FAQ answers this question:
Debuggers are commonly used to step through code and inspect that the variables along the way contain the expected values. But stepping through a program in a debugger is a manual process that requires tedious visual inspections. In essence, the debugging session is nothing more than a manual check of expected vs. actual results. Moreover, every time the program changes we must manually step back through the program in the debugger to ensure that nothing broke.
It generally takes less time to codify expectations in the form of an automated JUnit test that retains its value over time. If it's difficult to write a test to assert expected values, the tests may be telling you that shorter and more cohesive methods would improve your design.
2008-02-06, 5245👍, 0💬
Popular Posts:
What are some advantages and disadvantages of Java Sockets? Advantages of Java Sockets: Sockets are ...
How To Give a User Read-Only Access to a Database? - MySQL FAQs - Managing User Accounts and Access ...
How To Join a List of Keys with a List of Values into an Array? - PHP Script Tips - PHP Built-in Fun...
How To Display a Past Time in Days, Hours and Minutes? - MySQL FAQs - Managing Tables and Running Qu...
What is the difference between const char* p and char const* p? In const char* p, the character poin...