This is the top class module! Your team has very good and
solid C# knowledge, can implement industrial and
demanding projects in C#?
Yet errors and bugs are piling up? Your team spends more
time debugging and correcting than developing more
features? Every new requirement becomes a challenge? A
small change in one place causes code to break in other
places? The team has many quality discrepancies? Only a
few people know code very well, so the whole project
depends on them? Worse, these experienced people are
unhappy? Because they have to be permanently available
even on vacation and have to jump in every time a new
bug occurs?
It is exactly in such cases that it makes sense for your
entire C# team to master the art of writing Clean Code
and Clean Unit Test and put it into practice in their
daily work. As a result, the code is permanently
improved and more understandable for all team members,
code quality and productivity increase. Because if every
developer produces above-average code, the quality of
the code improves from day to day. As a positive side
effect, this makes it easier for new employees in your
team to get started and familiarize themselves with the
code base.
With Clean Code and Clean Unit Test, your team produces
effective C# code, high-quality code that is easy to
extend, test, and understand, and can respond quickly to
new requirements. Your team's productivity and quality,
as well as your customers' satisfaction, increase when
you can meet deadlines, deliver stable software, and set
certain quality standards in the process.
The
Effective
C#: Clean
Code and
Unit Test
topics
module includes
the following
focus
areas:
- How can I recognize bad code?
- Clean Code and Risk Management
- SOLID and OOP Code Principles
- Clean Code Rules for names, comments, functions
- Clean Code rules for classes, objects, data
structures
- Clean Code rules for exception handling
- Functional programming in C#
- Functional programming in C#
- Effective C#: Best Practice
- .NET Core Unit Testing: MSTest, NUnit, xUnit
- NUnit Foundation: Annotation, Assertion,
Parameterized Test
- Finding test data: Equivalence classes and
boundary data test
- Naming test methods
- Test Driven Development (TDD)
- Test Double techniques: Mocks, Fakes, Stubs, and
Dummies.
- Mocking Frameworks: Moq Framework