You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@isis.apache.org by "Dan Haywood (JIRA)" <ji...@apache.org> on 2014/06/20 10:34:24 UTC

[jira] [Updated] (ISIS-813) Provide the ability to mock out domain services in integration tests.

     [ https://issues.apache.org/jira/browse/ISIS-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Haywood updated ISIS-813:
-----------------------------

    Description: 
As inspired by this thread: http://markmail.org/thread/v3qptyjsrvsxi2j2 

Usually in an integration test we want the "real" implementations of our domain services.  That's certainly the case for repositories etc that connect to "our" database.

But for domain services that connect to the outside world (eg hit an external web service), it'd be useful to be able to replace the real implementation with a mock, and have this mock be used in the running system instead.

That mock would probably need to have a fairy liberal set of expectations, eg (in JMock) use allowing() or ignoring(); so I can see a bit of experimentation might be needed to make this work smoothly.  But it undoubtedly would be valuable.


  was:
See thread: http://markmail.org/thread/v3qptyjsrvsxi2j2




> Provide the ability to mock out domain services in integration tests.
> ---------------------------------------------------------------------
>
>                 Key: ISIS-813
>                 URL: https://issues.apache.org/jira/browse/ISIS-813
>             Project: Isis
>          Issue Type: New Feature
>          Components: Core
>    Affects Versions: core-1.5.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: core-1.6.0
>
>
> As inspired by this thread: http://markmail.org/thread/v3qptyjsrvsxi2j2 
> Usually in an integration test we want the "real" implementations of our domain services.  That's certainly the case for repositories etc that connect to "our" database.
> But for domain services that connect to the outside world (eg hit an external web service), it'd be useful to be able to replace the real implementation with a mock, and have this mock be used in the running system instead.
> That mock would probably need to have a fairy liberal set of expectations, eg (in JMock) use allowing() or ignoring(); so I can see a bit of experimentation might be needed to make this work smoothly.  But it undoubtedly would be valuable.



--
This message was sent by Atlassian JIRA
(v6.2#6252)