Advanced Unit Testing C# Code with NUnit and Moq - Part 1
- 3.9
-
![]()
![]()
![]()
![]()
Brief Introduction
Learn basics of unit testing, NUnit and Moq frameworks, unit testing asynchronous and multithreaded code.Description
Unit tests are written to test small parts (units) of the code. Properly written unit tests help us find bugs at a very early stage of the development process. Ability write good, functional unit tests is expected from developers for almost all development tasks.
NUnit is a very popular unit testing framework used by C# developers. Since we need to isolate the code block in order to test it, we sometimes need to prepare fake implementations for the dependencies that tested code block uses. These fake implementations are generally called "test doubles". Moq is another popular framework used to create automatic "test doubles" in a unit test.
This course starts with unit testing, test-double basics and includes introductory level lessons for NUnit and Moq frameworks that are just enough for you to start using them. You can learn more about them from the resources provided at the end of each section.
Writing unit tests for ordinary classes and methods are mostly easy. But there are some methods and classes that need special attention while writing unit tests. Asynchronous and multithreaded operations are two examples to them.
This course suggests different ways for testing asynchronous, multithreaded operations and timers.
I hope you enjoy the course.
Requirements
- Requirements
- Familarity with unit testing and NUnit framework.
Mustafa Kök
3.9 Raiting
Cracking Python Interview Questions On Programming
- 3.7
-
![]()
![]()
![]()
![]()
![]()
Cracking Python Interviews: Automation and Development ( 12 hrs of python interview questions on programming) Welcome to Cracking the Python Interview...
Advanced Unit Testing C# Code with NUnit and Moq - Part 1
- 3.9
-
![]()
![]()
![]()
![]()
![]()
Learn basics of unit testing, NUnit and Moq frameworks, unit testing asynchronous and multithreaded code. Unit tests are written to test small parts (units) of the code....
