Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This is a classic use case for dependency injection or a service locator. Instead of hardwiring your application to send emails, have your application get a notification service from the service locator, and have it call that. In production, configure the service locator to return an email sending service; in the test environment, configure it to return a service that does nothing, or add the notification to a list, or whatever.</p> <p>You don't need to go for the full whack dependency injection here: a very simple service locator will suffice. Similarly, the injection of the test notification service can be done through test fixture code. Here's a really simple example:</p> <pre><code>public static class ServiceLocator { private static INotificationService _notificationService = new EmailNotificationService(); public static INotificationService NotificationService { get { return _notificationService; } } // For test use only public static void SetNotificationService(INotificationService notificationService) { _notificationService = notificationService; } } </code></pre> <p>(A real service locator would provide a more flexible interface, along the lines of IServiceContainer/IServiceProvider, so that you could mock out multiple different services; this is just to illustrate the idea.)</p> <p>Then in your test code:</p> <pre><code>[SetUp] public void Setup() { ServiceLocator.NotificationService = new DiscardingService(); } </code></pre> <p>(Using NUnit terminology here for the method that gets run before each test -- not sure what the MSTest equivalent is.)</p> <p>An advantage of this is that you can now test that the right notifications are being sent: have your test notification service capture the notifications in a list, and you can make assertions about that list to verify that notifications are being sent and are correct.</p> <p>Again, note that this is not a full explanation of DI or service locators, and my sample code is by no means the best way to do it.</p>
    singulars
    1. This table or related slice is empty.
    1. POIs there any way to identify if it is a test or not (.NET)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USitowlson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POIs there any way to identify if it is a test or not (.NET)?
      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. VTUpMod
    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. VTAcceptedByOriginator
    1. COService locators are indeed a good solution.
      singulars
      1. PO
      1. USkrystan honour
    2. COkrystan: I don't like them much as they hide dependencies and pollute app code with "get this service, set this service" calls. Constructor-based DI means the app won't even build if the dependencies are not satisfied. With DI, It's easy to look at any piece of code in isolation and reason about its dependencies.
      singulars
      1. PO
      1. USMark Simpson
    3. COMark: fair point. The reason I didn't discuss DI in detail is that it requires a great deal more explanation than the simplistic service locator approach, and constructor-based DI would probably require considerably more refactoring of the original poster's application than a service locator would. But there's certainly a case that proper DI would likely be more maintainable as the scenario got more complex.
      singulars
      1. PO
      1. USitowlson
 

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