Sample ASP.NET MVC 5 app I wrote to explore automated web testing, singleton abuse, basic EF 6, and a few other things.
JavaScript CSS C# Other
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.

Monopoly sample project

This is a sample app I (@pseale) wrote to explore ASP.NET MVC 5, automated web testing, singleton abuse, basic EF 6, and a few other things. I am nowhere near finished implementing all of Monopoly, nor did I ever intend to get close to finishing. The UI is ugly and conspicuously AJAX-free.


Download/clone this project's source, get all NuGet packages, run the app (it creates its own LocalDB database in App_Data), and read the source as desired.

To run the web tests, use any NUnit test runner and run the entire test suite. The test run will fire up an IISExpress instance and a Selenium-driven browser. Chrome is default. Browser tests work for Chrome and Firefox. IE mostly works, but lies about cookies--in other words, IE doesn't work.

VS2013 version note: I created this sample project with a copy of Visual Studio 2013 Preview (emphasis on Preview), so if you're running the RC or anything newer, there might be some weirdness with Nuget packages. For example, all of the MVC 5 Identity packages have changed significantly; even some of the package names have changed.

Things I am mildly to moderately ashamed of

  1. UI. I did the minimum possible on top of what the base template (and twitter bootstrap) provided. With that said, I'm not ashamed of my paint-fu, though perhaps I should be.
  2. My automated web test harness is interesting, and better than anything I could find in ~30 minutes of browsing frameworks and sample projects. With taht said, it still has some major problems that will show up quickly if you try to just copy/paste use it on a real project with CI. I may fix them, but I haven't yet.
  3. As of today (2013-09-21), the test helpers are disorganized. I plan to experiment with them, but if they don't change...just know I meant to change them.
  4. I'm moderately ashamed of how I put zero (0) behavior on most of my model objects, but threw all the behavior on Game (the aggregate root). I either have to spread around the behavior like a strong domain model, or completely strip Game of all behavior like an anemic domain model, for consistency.
  5. My "fast tests" project sucks...I think. Maybe. Given I have comprehensive web tests, and given I was rarely at a loss for how to implement the simple behavior, I felt little need to add unit tests that covered things already covered by the web tests. Just be aware that I'm aware that I don't have many unit tests--whether I'd lean this heavily on end-to-end tests on a real project is a good question, just be aware that I am capable of writing more unit tests.
  6. My git checkin history is like a stream of consciousness with a few desperate cries for help. When working on solo projects I use source control as a lazy way to back up my work, as reading the commits for this project quickly shows. I could have (still can) go back and clean up the history so that each well-labeled commit represents a single change. But I didn't, and I won't.
  7. Don't look at SecretAdminController.

Things you may find interesting

  1. This is the only sample app I've seen with a working web test harness. This may be the first you've seen as well.
  2. I'm experimenting with simplicity for my domain model and surrounding code. Specifically, my "model/domain" code is implemented using dumb domain objects, static Query/Command objects, and all static Service objects. I am aware of the downsides of not using dependency injection ( ) and am experimenting with this anyway. So far, so good.
  3. If you are looking for examples for how to use Coypu (the .NET capybara-alike framework), well, here's some.
  4. This is the only MVC 5 sample app I have found, so it may be the first one you've found. I've taken advantage of some MVC 5 features, though in some cases (like Identity) I have twisted it into something you won't be able to reuse.
  5. I am (eventually) going to use EF 6, and (again) I haven't seen a sample app that uses it.