Visual Studio and .NET's Unit Test Framework

Now after this project has loaded, it will have a file UnitTest1.cs in it, this is the file you will be automating; we have created all the Test Cases for the MathLibrary.dll (our business logic).

To Automate the Test Cases in Microsoft Visual Studio using the Unit Testing Framework, you need to understand a few more things.

1. Test Automation Framework: Microsoft has its Unit Testing Framework implemented in a namespace which is Microsoft.VisualStudio.TestTools.UnitTesting
2. [TestMethod] attribute: This is the attribute that needs to be present on each method that will represent a TestCase.
3. Assert class: This class is part of Microsoft's Unit Testing framework, and we can use this class to verify that our Actual and Expected are the same or not, etc.

As mentioned above for every Test Case we have to write Automation code.

Note. Before we start coding the Automated TestCases,don't forget to add all the References.

WebReferences etc. that your Test infrastructure will use.

I have covered Four Test Cases for the Sum Function in MathLibrary.dll

// Test Case #1: to verify if passed ints are returning Right Result
[TestMethod]
public void TestSumResultAreEqual()
{
    MathLibrary.MathClass objMath = new MathClass();
    Assert.AreEqual(24, objMath.Sum(12, 12));
}

// Test Case #2: to verify if passed ints are Not returning Right Result
[TestMethod]
public void TestSumResultAreNotEqual()
{
    MathLibrary.MathClass objMath = new MathClass();
    Assert.AreNotEqual(25, objMath.Sum(12, 12));
}

// Test Case #3: to verify if passed ints are actually Zero
[TestMethod]
public void TestSumThrowExceptionWhenZero()
{
    MathLibrary.MathClass objMath = new MathClass();
    try
    {
        objMath.Sum(0, 0);
    }
    catch (ArgumentException)
    {
        // logging code will go here
    }
}

// Test Case #4: to verify if passed ints are actually Negative
[TestMethod]
public void TestSumThrowExceptionWhenNegative()
{
    MathLibrary.MathClass objMath = new MathClass();
    try
    {
        objMath.Sum(-123, -456);
    }
    catch (ArgumentException)
    {
        // logging code will go here
    }
}

Once you have coded all the Test Cases to Test the functionality, it's time to build the code and a TestProjectName.dll will be produced.

There are two ways to Test your automation code now.

1. Using the Visual Studio IDE: Build and then Run the project within Visual Studio; you will see all the TestMethods being executed and the Test Results are shown, as shown in the following image.
   
2. Using Visual Studio's command prompt: Open Visual Studio's command prompt and navigate to the folder where the TestProjectName.dll is located and then run this command.

   mstest /testcontainer:TestProjectName.dll
   

   

Summary

This article explained the approach to Test Automation using Microsoft Visual Studio's Unit Testing Framework. Some basic fundamentals about the framework, what is expected out of a test, and how to automate a business logic in a DLL form. The same approach can be used to even automate a WebService component etc.