Creating a basic MVC 6 web application with Entity Framework 7 and xUnit - Part 1

In my first post I'm showing you how to set up a basic MVC 6 web application with Entity Framework 7. Before we do any controllers, or creating any databases, we use xUnit and moq for creating a mock database context and testing our service. You can clone the repository with this sample from Github.

1. Creating the projects

Open Visual Studio 2015 RC and select New project.

Make sure you choose .NET Framework 4.6. Now create an empty ASP.NET 5 project.

Now create two projects of type Class Library, Sample1Data and Sample1DataTests:

You should now have 3 projects in your solution:

Next we need to install MVC 6, Entity Framework 7 and xUnit. To do this, we don't use the NuGet UI. It's easier to edit the project.json file of each project and adding the references there. Enjoy the Intellisense ;). Begin with the Sample1 project. Make sure you dependencies section looks like this:

As you can see, we already added a dependency to our Sample1Data project. Next up is the Sample1Data project:

And finally the Sample1DataTests project. Don't forget the commands part needed for the test runner.

Here we need to comment out the dnxcore50 framework since it's currently not supported by moq. This isn't a problem here since it's just the test project.

Now save and rebuild the solution. NuGet should automatically download all packages.

2. Defining a model and creating a simple test

In our Sample1Data project we need to add 2 classes: The model and a service class. Additionally, we add an interface for our data context.

Now that we have our data classes ready, we can write our first unit test in Sample1DataTests:

We aren't using MVC yet, but you can already add an implementation for the IDataContext in the web project:

Now we need to add this data context in Startup.cs

Rebuild the solution and open up the test explorer (in the VS menu, choose Test, Windows, Test Explorer). Now click Run all and our first test should be found, run and pass.

In the next parts we're connecting to a database, add controllers, add client-side code using TypeScript and add unit tests for testing this client-side code.

Comments

Post a Comment

Popular posts from this blog

Debugging Lua scripts in VS Code using MoonSharp

Image
Using MoonSharp as Lua interpreter in a .NET application is quite easy, but the docs lack of a good explanation on how to debug the Lua scripts. MoonSharp provides a Visual Studio Code extension and a .NET package for a debug server. I’m going to show how to implement the server using a simple .NET Core Console application. I won’t explain much about Lua or MoonSharp itself, so I expect you have at least some knowledge on how to use MoonSharp. You can find my demo application on GitHub . Preparing the environment For using MoonSharp, we need to install these NuGet packages: MoonSharp MoonSharp.Debugger.VsCode In VS Code you have to install the MoonSharp Debug extension. Make sure to use the latest VS Code version – in an older version the current line in the debugger wasn’t highlighted. In the launch.json, you have to put the debugServer object inside the configuration. The official documentation is wrong here. Loading the script For this demo, I added just one simple gl
Keep reading

Testing the response body of middleware in ASP.NET Core

Testing custom middleware in ASP.NET Core is very easy (e.g. for the response status code), but it’s a bit tricky if you want to test the response body because DefaultHttpContext uses a Null-Stream for the body and thus is always empty. Creating an implementation of HttpContext is way too much overhead, but you can use a custom Stream object for the response body of DefaultHttpContext . Here is how you do it. // use this memory stream for the response body var responseBodyStream = new MemoryStream(); var context = new DefaultHttpContext(); context.Features.Get<IHttpResponseFeature>().Body = responseBodyStream; var middleware = new MyMiddleware(async (c) => { await Task.Delay(0); }); await middleware.Invoke(context); // reset the position responseBodyStream.Position = 0; // read the body string bodyContent = new StreamReader(context.Response.Body).ReadToEnd();   The trick is to access the IHttpResponseFeature of the DefaultHttpContext and to use a custom MemoryStream
Keep reading

Creating a basic MVC 6 web application with Entity Framework 7 and xUnit - Part 2

Image
In this blog post we will connect to an actual database, create the tables using the code-first approach and add some initial data. Be aware that migrations seem to be a bit buggy at the moment, but my solution was (at least for me) the most stable one. You can clone the repository with this sample from Github . 1. Creating a database First, open the sql server object explorer (in the V iew  menu). I use the default MSSQLLocalDB for this example, but you can use any running SQLServer. Now add a new database to this SQL Server. Specify a database name and the location where to put the database file. Finally, we need the connection string for this database. Get to the properties of the newly created database and copy the connection string. 2. Necessary changes before the migrations Before we can run any migration, we have to set up some things. Create a Config.json in the Sample1 project and add your connection string. Attention: you have to escape the backsla
Keep reading