All Questions
7 questions
20
votes
7
answers
29k
views
Should each method have a separate JUnit test class?
I am writing JUnit unit tests for my classes.
Is it better to have a separate class for each method, or have just one test class for every actual class?
2
votes
4
answers
2k
views
Creating new constructors to overwrite the existing instance variables for testing purpose
Is it good/bad practice to add more constructors just for test purposes (to mock the DOCs used in my SUT) like this :
public class A {
private B b = new B();
private C c = new C();
public ...
6
votes
1
answer
2k
views
Wrapping utility classes and injecting them for unit testing purposes
I found that it is so hard to test classes that depend on other utility classes
as java.nio.file.Files. It is also impossible to mock them using the classic unit testing stack (junit,mockito,..) ...
11
votes
3
answers
8k
views
Mocking concrete class - Not recommended
I've just read an excerpt of "Growing Object-Oriented Software" book which explains some reasons why mocking concrete class is not recommended.
Here some sample code of a unit-test for the ...
3
votes
2
answers
11k
views
Unit testing / How to validate private fields of a newly created object?
I have a basic unit test (for the sample) that involves this code:
void testShouldCreateACar() {
Car car = someone.createFerrari();
assertTrue(car.name == "Ferrari"); // can't access name since ...
4
votes
2
answers
886
views
Domain object model: query by id vs object
Let assume I have two simple model classes: Product and Brand
It is obvious I have a query method in Product class like this
Product product = Product.findById(123);
What if, I want to query ...
5
votes
3
answers
2k
views
Inheritance vs containment while extending a large legacy project
I have got a legacy Java project with a lot of code. The code uses MVC pattern and is well structured and well written. It also has a lot of unit tests and it is still actively maintained (bug fixing, ...