Databases
StackOverflow2013
Postsdbo
POTDD'ing MVC Controllers to drive design
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POTDD'ing MVC Controllers to drive design
    primarykey
    data
    text
    <p>I am starting out on a new project (well, restarting an existing one), and trying to adopt TDD (for the nth time) for all the benefits that it should bring.</p> <p>I believe that TDD will result in my tests driving me to write only the code that I need to write, but it will drive me to write the code that I NEED and not leave some out.</p> <p>This is where my current state of uncertainty comes in.</p> <p>Consider the story:</p> <p>"A user must be able to add a widget, doing so they are taken to view the details of the newly added widget."</p> <p>OK, so working from the UI (as that's where a user will add their widget from, and not using Visual Studio and a set of assemblies that I write)... I begin with the following test, writing the very minimal so that the test passes.</p> <p>So I started out with the controller throwing a NotImplementedException, then returning a View()... the following was the first point that I had written the fewest lines I could to make the test pass.</p> <pre><code>[TestFixture] public class WidgetControllerTester { [Test] public void Create_IfBusinessModelIsValid_ReturnRedirectToRouteResultToDetailsAction() { // Arrange var currentUser = new User { DisplayName = "Fred", Email = "fred@widgets.com", Password = "pass", Status = UserStatus.Active }; var model = new WidgetModel(); var controller = new WidgetController(); // Act var actionResult = controller.Create(currentUser, model); // Assert actionResult.AssertActionRedirect().ToAction("Details"); } } public class WidgetModel { } public class WidgetController: Controller { public ActionResult Create() { return View("Create"); } [HttpPost] public ActionResult Create(User currentUser, Widget model) { return RedirectToAction("Details"); } } </code></pre> <p>Now I realise that additional tests for invalid models and checking of model state will evolve from additional stories.</p> <p>However I can't see a clear path of how I would leverage additional tests to drive further code within the controller.</p> <p>For instance, I know at some point I will want to make a WidgetService call from the Create action. Am I missing something obvious (not being able to see the wood for the trees kind of stuff) how I can progress the controller code with additional tests?</p> <p>Talking about the WidgetService, I expect that I will write a WidgetServiceTester and for th e time being references within the controller will most likely be mocked.</p> <p>Some thoughts I have had... </p> <ul> <li>Create a new test called Create_IfModelIsValid_WidgetIsAddedToRepository, but how does this clearly lead onto service calls in the controller action? </li> <li>I need to write a more detailed story stating that the model needs to be inserted into the repository/database, etc?</li> <li>Am I muddling up elements of TDD and XP?</li> </ul> <p>Thanks for reading, I would appreciate any feedback and insights to the best practice for progressing.</p> <p>Joe.</p> <p><strong>EDIT 27 Feb 2010</strong></p> <p>I found the following article Iteration #6 – Use Test-Driven Development (on asp.net) (<a href="http://www.asp.net/%28S%28ywiyuluxr3qb2dfva1z5lgeg%29%29/learn/mvc/tutorial-31-cs.aspx" rel="nofollow noreferrer">http://www.asp.net/%28S%28ywiyuluxr3qb2dfva1z5lgeg%29%29/learn/mvc/tutorial-31-cs.aspx</a>) which demonstrates the sort of thing I was after, however they seem to consider addition of repository/service to the controller as re-factoring... I personally don't agree, am I wrong? :)</p> <p>I'm going to think about writing a test that checks the ViewData of the Details action and update this question once I have.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USJoe
    1. USJoe
    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. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POTDD'ing MVC Controllers to drive design
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POTDD'ing MVC Controllers to drive design
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POTDD'ing MVC Controllers to drive design
      1. USRobert Harvey
      1. VTFavorite
    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