DTO Unit Testing

Question

Is testing getters and setters appropriate and necessary?

I think they have no logic, and they cannot crash or throw any exceptions.

Answer 1

You should not unit test DTO receivers and setters unless they contain complex logic that requires some testing.

Answer 2

, , . - , , .

, , , - C & P:

private String foo;
private String bar;

String getFoo() {return foo;}
String getBar() {return foor;}

: , . ? - , , ? , ? - ?

Answer 3

GOOS, , " " ( , DTO).

. " " , .

Answer 4

... - >

setTest(String test) {
   this.test = test;
}

- , ( - , .):

String token=";";
   setTestTwo(String testTwo) {
   this.testTwo = testTwo + tokenString;
}

Answer 5

/ unit test :
1. Code coverage 2. Automated regression testing

, junit, , , .

Answer 6

Using modern tools, this is not so much effort:

import static com.google.code.beanmatchers.BeanMatchers.hasValidBeanConstructor;
import static com.google.code.beanmatchers.BeanMatchers.hasValidBeanEquals;
import static com.google.code.beanmatchers.BeanMatchers.hasValidBeanHashCode;
import static com.google.code.beanmatchers.BeanMatchers.hasValidBeanToString;
import static com.google.code.beanmatchers.BeanMatchers.hasValidGettersAndSetters;
import static org.hamcrest.CoreMatchers.allOf;
import static org.hamcrest.MatcherAssert.assertThat;
import static org.junit.Assert.assertNotNull;

public class Test {

    @Before
    public void setUp() throws Exception {
    }

    @Test
    public void testFlatFileReaderMetadata_Parameters() throws Exception {

        assertNotNull(new Test());

        assertThat(Test.class, allOf(hasValidBeanConstructor(), hasValidBeanEquals(), hasValidGettersAndSetters(),
                hasValidBeanHashCode(), hasValidBeanToString()));
    }
}