jmsguy

7 ms·

1. 1.▲
   by jmsguy 11y ago

   Actually this is a really good talking point that's often the start of many interesting "discussions": Namely, what happens when you're done with the test-code-repeat cycle for a system under test and you want to make it
2. 2.▲
   by jmsguy 11y ago

   Unit tests should have exactly one system under test. That has to be a class, not an interface. You may mock dependencies that may/may not be interfaces. This is safer than using concrete dependencies whose behaviors may change once
3. 3.▲
   by jmsguy 11y ago

   My thoughts too: Sonar, or Checkstyle+PMD+FindBugs, is already ingrained in many of the larger codebases I've worked with. Of course this is purely anecdotal since I've only worked with +-30 over the years.
4. 4.▲
   by jmsguy 12y ago

   Not unless (a) your PC is routing traffic or (b) your PC is connected to a hub vs. a switch [1]. Unless one of these things is happening (even if your card is in promiscuous mode), those packets won't make it into your machine. [1] ht
5. 5.▲
   by jmsguy 12y ago

   > But I'm genuinely curious how most people classify the difference between api and library. JMS is an API [1], [2]. ActiveMQ [3] is an implementation of the JMS API. Commons BeanUtils [4] is a library. The library itself has an API