Skip to main content

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests:

Write tests for all public methods

Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early.

public class Calculator {

    public int Add(int a, int b) {
        return a + b;
    }
}
[TestClass]
public class CalculatorTests {
    [TestMethod]
    public void Add_ShouldReturnCorrectSum() {
        // Arrange
        Calculator calculator = new Calculator();
        int a = 1;
        int b = 2;
        // Act
        int result = calculator.Add(a, b);
        // Assert
        Assert.AreEqual(3, result);
    }
}

Test boundary conditions 

Make sure to test boundary conditions, such as null inputs or extreme values, to catch any edge cases that may cause problems.

public class Validator {

    public bool IsPositive(int number) {
        return number > 0;
    }
}
[TestClass]
public class ValidatorTests {
    [TestMethod]
    public void IsPositive_ShouldReturnFalseForZero() {
            // Arrange
            Validator validator = new Validator();
            // Act
            bool result = validator.IsPositive(0);
            // Assert
            Assert.IsFalse(result);
        }
        [TestMethod]
    public void IsPositive_ShouldReturnTrueForPositiveNumber() {
        // Arrange
        Validator validator = new Validator();
        // Act
        bool result = validator.IsPositive(3);
        // Assert
        Assert.IsTrue(result);
    }
}

Use a consistent naming convention :

Use a consistent naming convention for your tests, such as [MethodName]_Should[ExpectedBehavior], to make it clear what the test is testing. 

Keep your tests independent :

Make sure that your tests are independent of each other and don't rely on external state. This helps ensure that your tests are reliable and reproducible. 

Run your tests frequently:

Ideally after every code change we need to run unit tests to catch bugs early in the development process.

Labels:
Location: 5Q6QCR95+G6

Comments

Post a Comment

Popular posts from this blog

How To See Logs Of Dropped Tables From The Database in MS SQL.

Here, I will explain you how you can see logs of users. Step 1 : First, create a new database with name "test". Step 2 : Create a new table. Step 3 : Now, go and drop the table by running the following command. Step 4 : Now, select your database under Object Explorer and go to Reports >> Standard Reports >> Schema Changes History. Step 5 : You will then see the schema change history. The report will show you who has dropped this table. Finally, you can locate the user activity with the help of log.
Post a Comment
Read more

How To Deploy .net Core Application On Linux

Here, I can explain steps to deploy .net core application on linux machine. Step 1 - Publish your .net Core application: First, create a .net core application on VS; you can make an MVC project or Web API project and if you already have an existing project, then open it. Right Click on your project Click on publish Now create a new publish profile, and browse the folder where you want to publish your project dll Click on publish so it will create your dll in the folder Step 2 - Install required .net Module on Linux: Now we have our web application dll and now we need to host it on the Linux environment. First, we need to understand how the deployment works in Linux. .Net applications run on Kestrel servers and we run Apache or Nginx server in Linux environments, which acts as a proxy server and handles the traffic from outside the machine and redirects it to the Kestrel server so we will have Apache or Nginx server as the middle layer. In this article, we will use Apache as a proxy ser
Post a Comment
Read more

List Of Commonly Used Angular Commands

1) To get the npm version,    npm -v 2) To get the node version,    node -v 3) To get the Angular version,    ng v  4) To get the Jasmine version,    jasmine -v  5) To get the Karma version,    karma --version  6) To install Angular CLI,    npm install @angular/cli -g   npm install @angular/cli 7) To install the next version of Angular CLI, v   npm install @angular/cli@next  8) To get help in the terminal,    ng help 9) To create a new project in Angular,    ng new project-name  10) To skip external dependencies while creating a new project,    ng new project-name --skip-install  11) To run the Angular project,   ng serve (or) npm start (or) ng serve --force  12) Dry Run,   ng new project-name --dry-run 13) To create a new component in the Angular Project,   ng generate component component-
Post a Comment
Read more