Unit Testing in C#

In Today’s blog will discuss importance of Unit test cases and other points.

Introduction:

Unit cases is software development process that is implemented and executed by software developer to ensure implemented logic is behaves as expected or not and function is return the values as expected.

Unit testing allows the developer to refactor the code and the process is to write test cases for the functions and specific code so if any issue is accrued then can be identified quickly.

Benefits of Unit Testing:

Writing the effective test cases you ensure you code will work as expected it to work in development process.

Unit test cases has the ability to find the problems in development stage.

Unit testing can improve the code quality of you application making it more maintainable and less error in you code. It is valuable tool for improving the code quality and performance of software application.

Unit test can help you to find the bugs in early stage. Unit testing is provide you to testing the block of code in order to identify the issues.

Different types of Unit testing framework:

There are couple of Unit testing framework type’s is available. Below mentation is most popular types of framework.

· NUnit:

· Xunit:

· Microsoft Unit Testing Framework (MSTest):

NUnit:

NUnit is a Unit testing framework and testing tools for all the .Net languages. NUnit is open source framework support all version of .Net framework.

NUnit has several versions, the latest version is NUnit 3.0

For Using the NUnit framework you need to install NUnit and NUnit3TestAdapter Nuget package.

NUnit provides different types of attributes like [Test], [Setup], [TearDown], [TestCases] etc.

NUnit provides some methods to verify expected output of test cases like Assert.AreEqual(), Assert.IsTrue()  , Assert.IsFalse(), Assert.IsNull()  , Assert.IsNotNull() , etc.

Xunit:

Xunit is popular open source testing framework for the .Net framework primary used in C#. It’s providing some concepts like test fixtures, test cases and test runners.

Installing Xunit
you can install necessary package of Xunit like Xunit package and xunit.runner.visualstudio.

Writing the Test Cases

In Xunit are methods marked with the [Fact] attribute. Each test cases represent different types of scenarios.

Xunit provides different types of method through the Assert class for different purpose, such as Equal,

True, False, NotNull etc. using this method we can verify expected output of methods.

Microsoft Unit Testing Framework (MSTest):

MS test is testing framework and commonly used for writing and running the test cases in .Net applications.

MSTest is Provide different types of attribute

[TestClass]: Applied on class level that is contains test method.

[TestMethod]: Applied to the test methods.

MSTest is provides different types of methods to verify the expected output of you code like Assert.AreEqual, Assert.IsTrue, Assert.IsFalse, Assert.ThrowException etc.

Moq:

Moq is mocking library in .Net mostly used with Unit testing framework like NUnit, Xunit, MSTest etc.

Moq allows you to create mock objects for any class or interface or Abstract class. You can define behavior of the mock object including setting return values for methods or specific code.

Primary advantage of Moq is its ability to specify setup for methods calls, allowing you to define how mock object should be work with particular method.

You can use Moq to create mock objects within your unit tests and verify the behavior of your code under the test cases.

What is the Code Coverage of unit Test?

Code coverage is report or metric that can help you to understand how much your code is tested by unit test.

Below is different types of Code Coverage behavior to cover the Code

Branch Coverage: Branch coverage specially cover percentage of branch like (if condition, statements, switch cases etc.) by unit test cases.

Line Coverage: Line coverage specially cover how many lines of source code have been tested by unit test cases.

This package “coverlet.collector” is required to generate the code coverage report.