Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You are reusing your context, in order to have tests independent from one another you probably need to refresh your context after each test to reset everything.</p> <p>I will suppose you are using Junit 4.5+. It would be similar with other test frameworks. </p> <pre><code>@RunWith(SpringJUnit4ClassRunner.class) @ContextConfiguration(locations={"mycontext.xml"}) @DirtiesContext(classMode = ClassMode.AFTER_EACH_TEST_METHOD) public class MyTestClass { ... // my tests ... } </code></pre> <p>You can put the <code>@DirtiesContext</code> at the method level if the methods that need "fixing" are few, but if you are using Spring your best option is to do it after every test.</p> <p>Anyway, I don't think you should be using mocks/spies in integration tests:</p> <ul> <li><p>In unit tests, use mocks (if you want) and inject manually. Here you want to verify the behaviour of your tested bean as a unit, so you isolate it from the rest by using mocks. This also has the advantage that JUnit isolates your tests by using a different instance of the test class for each test, so unless you use <code>static</code> or other test-unfriendly practices everything will just work.</p></li> <li><p>In integration tests, use real beans and let Spring inject. Here the goal is to verify that beans interact well with one another / with the environment (database, network, ...) You do <em>not</em> want to isolate beans here, so you should not use mocks.</p></li> </ul> <p>See <a href="http://static.springsource.org/spring/docs/3.0.0.RELEASE/reference/html/testing.html#testcontext-support-classes" rel="noreferrer">Spring documentation about testing</a> for more detailed explanations.</p>
    singulars
    1. This table or related slice is empty.
    1. POCreating a new instance of a bean after each unit test
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USgpeche
    1. USgpeche
    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. COThanks for the code example. As I have commented on Eugen's answer I mixed the two kinds of tests up. This is what I'll be using in my real integration tests :)
      singulars
      1. PO
      1. USgeoffreydv
    2. COThank you very much. This can also be applied on TestNG-Testclasses that extend `AbstractTestNGSpringContextTests`.
      singulars
      1. PO
      1. USSebastian Saip
 

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