Databases
StackOverflow2013
Postsdbo
POHow to mock a method with functional arguments in Scala?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHow to mock a method with functional arguments in Scala?
    primarykey
    data
    text
    <p>I'm trying to mock a method call that takes a call-by-name argument:</p> <pre><code>import org.scalatest.WordSpec import org.scalatest.mock.MockitoSugar import org.mockito.Mockito._ import org.junit.runner.RunWith import org.scalatest.junit.JUnitRunner trait Collaborator { def doSomething(t: =&gt; Thing) } trait Thing @RunWith(classOf[JUnitRunner]) class Test extends WordSpec with MockitoSugar { "The subject under test" should { "call the collaborator" in { // setup val m = mock[Collaborator] val t = mock[Thing] // test code: this would actually be invoked by the SUT m.doSomething(t) // verify the call verify(m).doSomething(t) } } } </code></pre> <p>I'm primarily interested in Mockito since that's what I'm using, but I'd be interested to see whether any of the major mock frameworks is capable of this kind of testing. The Test fails at runtime on the <code>verify</code> line, with an error like</p> <blockquote> <pre><code>Argument(s) are different! Wanted: collaborator.doSomething( ($anonfun$apply$3) &lt;function&gt; ); -&gt; at Test$$anonfun$1$$anonfun$apply$1.apply(Test.scala:27) Actual invocation has different arguments: collaborator.doSomething( ($anonfun$apply$2) &lt;function&gt; ); -&gt; at Test$$anonfun$1$$anonfun$apply$1.apply(Test.scala:24) </code></pre> </blockquote> <p>If I'm understanding the situation correctly, the compiler is implicitly wrapping <code>t</code> in a nullary function that returns <code>t</code>. The mock framework is then comparing that function to the one produced in the test code, which is equivalent but not <code>equals()</code>.</p> <p>My case is a relatively simple version of the problem, but I think this would be an issue with any higher-order function.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAaron Novstrup
    1. USAaron Novstrup
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POHow to mock a method with functional arguments in Scala?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POHow to mock a method with functional arguments in Scala?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POHow to mock a method with functional arguments in Scala?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't understand how this relates to the Apple iPad.
      singulars
      1. POHow to mock a method with functional arguments in Scala?
      1. USMitch Blevins
    2. COCould you describe how it doesn't work more clearly or include some test code. It's hard to know what's going on here with just the verify shown.
      singulars
      1. POHow to mock a method with functional arguments in Scala?
      1. USGeoff Reedy
    3. COI made the example runnable as written and included the actual output associated with the failure.
      singulars
      1. POHow to mock a method with functional arguments in Scala?
      1. USAaron Novstrup
 

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