Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Responded to a similar question some days ago <a href="https://stackoverflow.com/questions/1601073/nunit-mocking-not-working-for-singleton-method/1601438#1601438">here, mocking a Singleton</a>. The original post is for C#.Net as regards mocking a singleton's behaviour, but should still apply.</p> <p>As regards the singleton pattern, there isn't anything wrong with it per se - in many cases we want to centralize logic and data. However, there is a very big difference between a singleton and a static class. Building your singleton as a static class hard codes that implementation to every consumer in your application - which makes unit testing very difficult!</p> <p>What you want to do is define an interface for your singleton, exposing the methods for your consumers to use. Your consumers in turn are <strong>passed</strong> a reference to an implementing class by whomever instantiates them [typically this is your application, or a container if you are familiar with Dependency Injection\Inversion of Control].</p> <p>It's this framework, whomever is instantiating the consumers, that is responsible for ensuring one and only one instance is floating around. It's really not that great a leap from static class to interface reference [as demonstrated in link above], you just lose the convenience of a globally accessible instance - i know i know, global references are terribly seductive, but Luke turned his back to the Dark Side, so can you!</p> <p>Generally speaking, best practices suggest avoiding static references, and encourages progamming against interfaces. Remember, it is still possible to apply the singleton pattern with these constraints. Follow these guidelines, and you should have no problem unit testing your work :)</p> <p>Hope this helps!</p> <hr> <p><strong>singleton != public static class</strong>, rather <strong>singleton == single instance</strong></p>
    singulars
    1. This table or related slice is empty.
    1. POHow can I test a Singleton class with DUnit?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USjohnny g
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow can I test a Singleton class with DUnit?
      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. VTUndeletion
    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. This table or related slice is empty.
 

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