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:
Do You Need to Write a Test Class for Every Class That Need to Be Tested?
Do You Need to Write a Test Class for Every Class That Need to Be Tested?
✍: FYICenter.com QA Team
This is a simple question. But the answer shows your organization skills.
The technical answer is no. There is no need to write one test class for each every class that need to be tested. One test class can contain many tests for many test target classes.
But the practical answer is yes. You should design one test class per test target class for low level basic tests. This makes your test classes much easier to manage and maintain.
You should write separate test classes for high level tests that requires multiple target classes working together.
2008-02-26, 5416👍, 0💬
Popular Posts:
.NET INTERVIEW QUESTIONS - What is the difference between System exceptions and Application exceptio...
What is the output of printf("%d")? 1. When we write printf("%d",x); this means compiler will print ...
What is the difference between Session State and ViewState? ViewState is specific to a page in a ses...
What is V model in testing? V model map’s the type of test to the stage of development in a project....
Can you explain what is “AutoPostBack” feature in ASP.NET ? If we want the control to automatically ...