title: During suite tests EasyMock says 0 matchers expected 1 recorded
body: <p>So I've been using EasyMock's class extension for a while now. All of a sudden I'm getting this exception, but only when I run the entire test suite:</p>
  
  <pre><code>java.lang.IllegalStateException: 0 matchers expected, 1 recorded.
  at org.easymock.internal.ExpectedInvocation.createMissingMatchers(ExpectedInvocation.java:42)
  at org.easymock.internal.ExpectedInvocation.&lt;init&gt;(ExpectedInvocation.java:34)
  at org.easymock.internal.ExpectedInvocation.&lt;init&gt;(ExpectedInvocation.java:26)
  at org.easymock.internal.RecordState.invoke(RecordState.java:64)
  at org.easymock.internal.MockInvocationHandler.invoke(MockInvocationHandler.java:24)
  at org.easymock.internal.ObjectMethodsFilter.invoke(ObjectMethodsFilter.java:56)
  at org.easymock.classextension.internal.ClassProxyFactory$1.intercept(ClassProxyFactory.java:74)
  at com.protrade.soccersim.data.emulator.matrix.PositionCategoryMatrix$$EnhancerByCGLIB$$c5298a7.getPossession(&lt;generated&gt;)
  at com.protrade.soccersim.data.emulator.stats.team.PossessionCalculatorUnitTest.testDeterminePossessionHomeWin(PossessionCalculatorUnitTest.java:45)
  </code></pre>
  
  <p>The code involved is this little beauty (trimmed a bit):</p>
  
  <pre><code>    @Before
  public void setUp() throws Exception {
      homeTeam = createMock( PositionCategoryMatrix.class );
      awayTeam = createMock( PositionCategoryMatrix.class );
      ...
  }
  
  @Test
  public void testDeterminePossessionHomeWin() {
      expect(homeTeam.getPossession()).andReturn( 0.15151515 );
      expect(awayTeam.getPossession()).andReturn( 0.01515152 );
      replay( homeTeam, awayTeam );
      ...
  }
  </code></pre>
  
  <p>The exception is being thrown on the first expect. And it really doesn't make sense. It says it's getting a matcher, but the method doesn't even take an argument. And odd enough it's only during test suites! I'm creating a new mock in the @Before, so it shouldn't be inheriting anything from somewhere else (not that some other method would have a matcher on it)</p>
  
  <p>So, any ideas?</p>