Testing – With Mock Objects

Testing – With Mock Objects

• 1.
  Testing – withMock objects Emmett Walsh
• 2.
  A common problem •Writing a test for a DAO manager – End up writing same test as that for the DAO(s) – Pre-populate DB before tests – Verify DB during/after tests • Not true unit test – more an integration test • If DAO fails , the manager test fails • Would be nice not to have to rely on DB
• 3.
  A Solution • Allowdummy/mock DAO (or other classes) be injected into class under test • Provide setters for objects we would like to mock
• 4.
  Creating Mock objects •Create mock impl of interface that returns ‘fake’ results (i.e. no db access involved) • Or subclass current implementation and override methods • Example…
• 5.
  private class MockFormulaDAOimplements IFormulaDAO { public int create(Formula formula, ORDatabaseTransaction transaction) throws DatabaseException { if (formula != null){ //return canned response return 1; } else { throw new NullPointerException(); } } . . . Etc Etc.
• 6.
  Disadvantages • Time consuming •Pollutes code base • More maintenance (e.g. if interface changes) • Much effort involved to add more sophisticated features (e.g. param checking, call order)
• 7.
  Mock frameworks • Mockito • JMock • JMockit (allows mocking of static methods) • Powermock (allows mocking of static methods) • EasyMock
• 8.
  Advantages • Remove thegrunt work • Allows to easily simulate collaborators in a test • Offers more features – Order checking of calls to mock object – Param checking in calls to mock object – Can run in various modes (nice v strict) – Mature (Easymock 4yrs, at v2.5.1, lots docs)
• 9.
  EasyMock • Generates mockobjects on the fly from interfaces or classes (uses java.lang.reflect.Proxy) • Uses a 4 stage lifecycle – Create mock(s) – Set expectations on the mocks – Put mock(s) in ready mode – Verification of expectations (i.e. the expected methods got called on the mock(s) )
• 10.
  Demo • FormulaManagerTest.java (currentlyuses hand made mocks)
• 11.
  Results • Code coveragebefore EasyMock – Block 64% – Line 64% • Code coverage after EasyMock – Block 100% – Line 100%
• 12.
  EasyMock - Conclusion •Helps us write better tests in shorter time • Allows us to possible separate unit tests from integration tests – they run fast! • True unit tests could possibly be run at customer site as a quick sanity check ??? • Easy – low learning curve • Reliable – comes with its own unit tests, 180+ test classes
• 13.
  End