JUnit General - 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?

Q

Do You Need to Write a Test Class for Every Class That Need to Be Tested?

✍: FYICenter.com QA Team

A

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, 4780👍, 0💬

What Is JUnit TestCase?
What Is JUnit TestCase? JUnit TestCase is the base class, junit.framework.TestCase, used in JUnit 3.8 that allows you to create a test case. TestCase class is no longer supported in JUnit 4.4. A test case defines the fixture to run multiple tests. To define a test case Implement a subclass of TestCa... 2008-02-26, 5045👍, 0💬

What Is JUnit TestSuite?
What Is JUnit TestSuite? JUnit TestSuite is a container class, junit.framework.TestSuite, used in JUnit 3.8 that allows you to group multiple test cases into a collection and run them together. TestSuite class is no longer supported in JUnit 4.4. Each test runs in its own fixture so there can be no ... 2008-03-04, 4952👍, 0💬

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? 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 ... 2008-02-26, 4781👍, 0💬

Under What Conditions Should You Not Test Get() and Set() Methods?
Under What Conditions Should You Not Test Get() and Set() Methods? The JUnit FAQ provides a good answer to this question: Most of the time, get/set methods just can't break, and if they can't break, then why test them? While it is usually better to test more, there is a definite curve of diminishing... 2008-02-19, 4727👍, 0💬

All rights in the contents of this web site are reserved by the individual author. fyicenter.com does not guarantee the truthfulness, accuracy, or reliability of any contents.