Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I'd argue that you are expecting a result from your test that implies the use of several dependencies, arguably not qualifying it as a unit test, especially because of an implied dependency on EF.</p> <p>The idea here is that if you acknowledge that your BookService has a dependency on EF you should use a mock to assert it interacts correctly with it, unfortunately EF doesn't seem to like to be mocked, so we can always put it under a repository, here's an example of how that test could be written using Moq:</p> <pre><code>[Test] public void AssignAuthorToBook_NewBookNewAuthor_CreatesNewBookAndAuthorAndAssociatesThem() { var bookRepositoryMock = new Mock&lt;IBookRepository&gt;(MockBehavior.Loose); IBookService service = new BookService(bookRepositoryMock.Object); var book = new Book() {Id = 0} var author = new Author() {Id = 0}; service.AssignAuthorToBook(book, author); bookRepositoryMock.Verify(repo =&gt; repo.AddNewBook(book)); bookRepositoryMock.Verify(repo =&gt; repo.AddNewAuthor(author)); bookRepositoryMock.Verfify(repo =&gt; repo.AssignAuthorToBook(book, author)); } </code></pre> <p>The id being set is something that you would use an integration test for, but I'd argue that you shouldn't worry about the EF failing to set the Id, I say this for the same reason you should not worry about testing if the .net framework does what it's supposed to do.</p> <p>I've written about interaction testing in the past (which I think is the right way to go in this scenario, you are testing the interaction between the BookService and the Repository), hope it helps: <a href="http://blinkingcaret.wordpress.com/2012/11/20/interaction-testing-fakes-mocks-and-stubs/">http://blinkingcaret.wordpress.com/2012/11/20/interaction-testing-fakes-mocks-and-stubs/</a> </p>
    singulars
    1. This table or related slice is empty.
    1. POUnit testing: TDD with POCO Objects with navigation properties (relationship fixup)
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USRui
    1. USRui
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTBountyClose
    1. COI've just remembered, although this might not seem very useful other than for making a more interesting example: if you had a test in your book service that checked if the Id of the book was 0, it would first add the book (same for the author) and then call AssignBookToAuthor, all using the Repository's mock. This way you would be testing the behavior of adding the book and the author if they were new and then assigning them to each other, all without a call to the DB
      singulars
      1. PO
      1. USRui
    2. COThanks. In our service implementation, the service is manipulating the domain objects directly (it could be `book.Author = author;`) rather than calling a repo method `repo.AssignAuthorToBook(book, author)`. The main problem with our tests is that they are testing business logic by the way the IDs / navigation properties are set on the domain objects, often a lot more complex than a simple author/book relationship, which is the main reason I'm bothered by the way it is done currently.
      singulars
      1. PO
      1. USSilverlightFox
    3. COPS. Please could you update your answer with your suggestion in your comments? I'm not sure I follow - it would make your example clearer.
      singulars
      1. PO
      1. USSilverlightFox
 

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