Test Driven development on .net and xunit.png

xunit.tar.gz

Basic Tests

Unit/Integration Tests

End-to-end Tests

Basic Tests with coverage

Unit/Integration Tests with coverage

Test-driven development (TDD) is a proven way of developing high-quality applications with clean and well-maintainable code. In this course, you will learn how to use the xUnit testing library to apply the principles of test-driven development on .NET.

You will start this course by reviewing the fundamentals of xUnit and how automated testing works on .NET. Then, you will practice the key TDD fundamentals. After this, you will move to more advanced topics, such as mocking, understanding the testing pyramid, running integration tests against hosted apps, etc.

By the end of the course, you will have learned how to develop high-quality software by following the TDD principles. You will also have learned how to use xUnit to write any automated tests supported by .NET.

Using xUnit for Test-Driven Development in .NET

To validate that the value inside a specific field, variable, or property has an expected value at the end of the test

To validate that the system has been set up correctly before running the tests

To verify that the objects that the tests interacted with are in the correct state after the code under test has been invoked

To verify that the input data is in the right state before running a test

**(Select all that apply.)** What assertions in automated tests are used for? 

(Select all that apply.) What assertions in automated tests are used for?

Which static method would you use on the inbuilt xUnit `Assert` class to validate if two values are the same?

Which static method would you use on the inbuilt xUnit <code>Assert</code> class to validate if two values are the same?

Because performing certain assertions with the inbuilt `Assert` class is impossible

**(Select all that apply.)** What are the reasons for using Fluent Assertions or Shouldly over the built-in xUnit assertion functionality? 

(Select all that apply.) What are the reasons for using Fluent Assertions or Shouldly over the built-in xUnit assertion functionality?

Passing an `Action` instance into the `Throw` method

Adding the `Throw` extension method to the `Should` invocation on an `Action` instance

By applying the `Throw` extension method directly on the `Action` instance

By passing an `Action` instance into a static `Throw` method

How can you use Fluent Assertions to determine if a specific type of exception is thrown for a specific method invocation?

How can you use Fluent Assertions to determine if a specific type of exception is thrown for a specific method invocation?

`ShouldBe` with an expression that returns a negative value as a parameter

Which extension method of Shouldly can determine if two variables don’t hold the reference to the same object?

Which extension method of Shouldly can determine if two variables don’t hold the reference to the same object?

Test your knowledge of assertions in xUnit.

Introduction to Automated Testing

Test-Driven Development

Assertions as a Key Part of Automated Tests

Different Types of Automated Tests

Mocking External Dependencies

Working with Code Coverage Metrics

Summary

Appendix

Quiz Yourself on Automated Test Assertions