Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The insight is that what you need to mock is <code>socketClientFactory</code>. And then set it up to return a mock <code>SocketClient</code>.</p> <p>Given:</p> <pre><code>trait SocketClient { def frobnicate(): Unit } class ScannerBase(path: String) class XScanner[T &lt;: SocketClient]( confPath: String = "/etc/default/configPath", socketClientFactory: String =&gt; T ) extends ScannerBase(confPath) { val socket = socketClientFactory("Some Socket Name") socket.frobnicate } </code></pre> <p>(side note - your default value for <code>confPath</code> can never be used because there's no default value for <code>socketClientFactory</code>).</p> <p>then this should get you started (this is with Scala 2.9.x and ScalaMock2 - 2.10.x with ScalaMock3 will be slightly different, but not much so):</p> <pre><code>import org.scalatest.FunSuite import org.scalamock.scalatest.MockFactory import org.scalamock.generated.GeneratedMockFactory class ScannerTest extends FunSuite with MockFactory with GeneratedMockFactory { test("scanner") { val mockFactory = mockFunction[String, SocketClient] val mockClient = mock[SocketClient] mockFactory.expects("Some Socket Name").returning(mockClient) mockClient.expects.frobnicate val scanner = new XScanner("path/to/config", mockFactory) } } </code></pre> <p>For completeness, here's the same test in Scala 2.10.0 and ScalaMock3:</p> <pre><code>import org.scalatest.FunSuite import org.scalamock.scalatest.MockFactory class ScannerTest extends FunSuite with MockFactory { test("scanner") { val mockFactory = mockFunction[String, SocketClient] val mockClient = mock[SocketClient] mockFactory.expects("Some Socket Name").returning(mockClient) (mockClient.frobnicate _).expects() val scanner = new XScanner("path/to/config", mockFactory) } } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POScalaMock. Mock a class that takes arguments
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaul Butcher
    1. USPaul Butcher
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POScalaMock. Mock a class that takes arguments
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI'm not sure how this overcomes the fact that SocketClient takes 1 argument. I can't write: val mockClient = mock[SocketClient] mockFactory.expects("Some Socket Name").returning(mockClient) Because mock[SocketClient] won't compile. Are you suggesting I modify SocketClient to take no arguments or have default values for all the arguments? Even if no defaults make sense. Thanks very much for replying btw.
      singulars
      1. PO
      1. USjangoolie
    2. COAh, sorry - I missed that wrinkle first time around. Right now, ScalaMock3 can only mock traits and no-args classes. But if you control SocketClient, you should still be fine - create a trait which defines the methods and implement it in your class: trait SocketClientBase; class SocketClient(...) extends SocketClientBase. Then you can mock SocketClientBase and you should be good? Or am I missing something?
      singulars
      1. PO
      1. USPaul Butcher
    3. COAlso of note Even if I copy your code exactly I can't get it to compile. I get: overriding method nestedSuites in trait SuiteMixin of type => scala.collection.immutable.IndexedSeq[org.scalatest.Suite]; [error] method nestedSuites in trait Suite of type => List[org.scalatest.Suite] has incompatible type [error] class ScannerTest extends FunSuite with MockFactory {
      singulars
      1. PO
      1. USjangoolie
 

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