per Bug 79352 :
Please describe/specify the skeletons you want to be generated:

Framework Specification / Custom imports. Allow the user to specify which methods are used for assertEquals & assertArrayEquals. For example, to allow hamcrest assertions with custom matchers

Current: skeletons assume that tests are based on org.junit.Assert
Example: 
        import static org.junit.Assert.*;
        ...
        assertEquals(expResult, result);

Enhancement: allow user specification of assertion framework
Example:
        import static org.hamcrest.MatcherAssert.*;
        import static org.hamcrest.Matchers.*;
        ... 
        assertThat(result, is(equalTo(expResult)));

Components: 
   (a) allow specification of static imports  
   (b) allow user to override generation of the assertEquals, assertArrayEquals, etc statements