ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jacques Le Roux (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-2842) Add mocked unit test framework
Date Wed, 17 Jan 2018 17:12:00 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-2842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16329019#comment-16329019
] 

Jacques Le Roux commented on OFBIZ-2842:
----------------------------------------

Unfortunately this patch is deprecated, but the idea is interesting. Should we close or adapt
and continue, opinions?

> Add mocked unit test framework
> ------------------------------
>
>                 Key: OFBIZ-2842
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-2842
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: ALL COMPONENTS
>    Affects Versions: Trunk
>            Reporter: Bob Morley
>            Priority: Major
>         Attachments: OFBIZ-2842.patch, mockito-all-1.8.0-rc2.jar
>
>
> Add the ability to create "true" unit tests -- ones that only test the confines of the
method itself and using mocking techniques and dependency injection.  This focuses the unit
test on the actual code in the method and makes the assumption that other methods have been
properly tested and will work.  This does not suggest that there is not also value in unit
tests that test more of an integration between components (such as a test that will actually
invoke services using a the real dispatcher and manipulate entities with the real delegator).
> The goal of this will be to make it easy and very quick to test java-based methods (initial
focus on services) along with not having to start an ofbiz container creating a suite of very
quick method focused unit tests.
> I have attached a first pass at some of the base classes and a sample of a "mostly complete"
unit test for the DateDimensionServices class (which has one method).  Looking for feedback
on this approach, potential for community collaboration, and potential buy-in.  Some other
things that are still to be done --
> - more samples
> - integration into ant build
> - solution to the "static worker" issue
> - UtilResourceBundle solution (I have it partially commented out)
> - easy verification of service interface adherence (servicedef existance & IN/OUT
validation)
> - potential for GenericEntity get/set validation (verify entitydef adherence) (may not
want to do this)
> - investigate potential for mocked simple methods
> - ant driven code coverage metrics



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message