Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Create a mock with Mockito (in "Java statements" context):</p> <pre><code>${:importStatic('org.mockito.Mockito.mock')}${Type} ${mockName} = mock(${Type}.class); </code></pre> <p>And in "Java type members":</p> <pre><code>${:import(org.mockito.Mock)}@Mock ${Type} ${mockName}; </code></pre> <p>Mock a void method to throw an exception:</p> <pre><code>${:import(org.mockito.invocation.InvocationOnMock,org.mockito.stubbing.Answer)} doThrow(${RuntimeException}.class).when(${mock:localVar}).${mockedMethod}(${args}); </code></pre> <p>Mock a void method to do something:</p> <pre><code>${:import(org.mockito.invocation.InvocationOnMock,org.mockito.stubbing.Answer)}doAnswer(new Answer&lt;Object&gt;() { public Object answer(InvocationOnMock invocation) throws Throwable { Object arg1 = invocation.getArguments()[0]; return null; } }).when(${mock:localVar}).${mockedMethod}(${args}); </code></pre> <p>Verify mocked method called exactly once:</p> <pre><code>${:importStatic(org.mockito.Mockito.verify,org.mockito.Mockito.times)} verify(${mock:localVar}, times(1)).${mockMethod}(${args}); </code></pre> <p>Verify mocked method is never invoked:</p> <pre><code>${:importStatic(org.mockito.Mockito.verify,org.mockito.Mockito.never)}verify(${mock:localVar}, never()).${mockMethod}(${args}); </code></pre> <p>New linked list using Google Guava (and similar for hashset and hashmap):</p> <pre><code>${import:import(java.util.List,com.google.common.collect.Lists)}List&lt;${T}&gt; ${newName} = Lists.newLinkedList(); </code></pre> <p>Also I use a huge template that generates a Test class. Here is a shortened fragment of it that everyone interested should customize:</p> <pre><code>package ${enclosing_package}; import org.junit.*; import static org.junit.Assert.*; import static org.hamcrest.Matchers.*; import static org.mockito.Matchers.*; import static org.mockito.Mockito.*; import org.mockito.Mockito; import org.slf4j.Logger; import org.mockito.InjectMocks; import org.mockito.Mock; import org.mockito.runners.MockitoJUnitRunner; import org.junit.runner.RunWith; // TODO autogenerated test stub @RunWith(MockitoJUnitRunner.class) public class ${primary_type_name} { @InjectMocks protected ${testedType} ${testedInstance}; ${cursor} @Mock protected Logger logger; @Before public void setup() throws Exception { } @Test public void shouldXXX() throws Exception { // given // when // TODO autogenerated method stub // then fail("Not implemented."); } } // Here goes mockito+junit cheetsheet </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUseful Eclipse Java Code Templates
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USmantrid
    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. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm curious: why would you need to mock the logger?
      singulars
      1. PO
      1. USVladimir Sizikov
    2. COyou can verify the mocked logger was called in case an exception was caught (failure scenario). that's espacially useful if you don't intend to rethrow it but want assert it's not silently ignored.
      singulars
      1. PO
      1. USmantrid
 

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