Databases
StackOverflow2013
Postsdbo
PODynamically adding JUnit tests to a test class
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODynamically adding JUnit tests to a test class
    primarykey
    data
    text
    <p>I find myself writing lots and lots of boiler plate tests these days and I want to optimize away a lot of these basic tests in a clean way that can be added to all the current test classes without a lot of hassle.</p> <p>Here is a basic test class:</p> <pre><code>class MyClassTest { @Test public void doesWhatItDoes() { assertEquals("foo",new MyClass("bar").get()); } } </code></pre> <p>Lets say if MyClass implements Serializable, then it stands to reason we want to ensure that it really is serializable. So I built a class which you can extend which contains a battery of standard tests which will be run along side the other tests.</p> <p>My problem is that if MyClass does NOT implement Serializable for instance, we still have a serialization test in the class. We can make it just succeed for non-serializable classes but it still sticks around in the test list and once this class starts to build it will get more and more cluttered. </p> <p>What I want to do is find a way to dynamically add those tests which are relevant to already existing test classes where appropriate. I know some of this can be done with a TestSuit but then you have to maintain two test classes per class and that will quickly become a hassle.</p> <p>If anyone knows of a way to do it which doesn't require an eclipse plug-in or something like that, then I'd be forever grateful.</p> <p>EDIT: Added a brief sample of what I described above;</p> <pre><code>class MyClassTest extend AutoTest&lt;MyClass&gt; { public MyClassTest() { super(MyClass.class); } @Test public void doesWhatItDoes() { assertEquals("foo",new MyClass("bar").get()); } } public abstract class AutoTest&lt;T&gt; { private final Class&lt;T&gt; clazz; protected AutoTest(Clazz&lt;T&gt; clazz) { super(); this.clazz = clazz; } @Test public void serializes() { if (Arrays.asList(clazz.getInterfaces()).contains(Serializable.class)) { /* Serialize and deserialize and check equals, hashcode and other things... */ } } } </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USEmily
    1. USEmily
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. PODynamically adding JUnit tests to a test class
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODynamically adding JUnit tests to a test class
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODynamically adding JUnit tests to a test class
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAre you sure you want to unit test if a class that implements Serializable is really Serializable? Or was it just an example?
      singulars
      1. PODynamically adding JUnit tests to a test class
      1. USLuciano Fiandesio
    2. COYes, but there are other things I want to test too like nullability and such using the jsr-305 annotations. This is largely inspired by Guavas test framework, but it still requires a ton of boiler plate that I feel we should be able to avoid.
      singulars
      1. PODynamically adding JUnit tests to a test class
      1. USEmily
    3. COIMHO, a unit test should focus solely on the class under test. If your objects aren't getting marshalled properly, a functional/integration test will catch it.
      singulars
      1. PODynamically adding JUnit tests to a test class
      1. USSahil Muthoo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload