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, 5561👍, 0💬
Popular Posts:
How To Insert Multiple Rows with a SELECT Statement? - MySQL FAQs - Managing Tables and Running Quer...
What is the sequence of UML diagrams in project? First let me say some fact about this question, you...
How comfortable are you with writing HTML documents entirely by hand? Everyone has a different prefe...
1. The basics first, please define the web in simple language? How is it connected with internet? Wh...
How To Retrieve Input Values for Checkboxes Properly? - PHP Script Tips - Processing Web Forms If mu...