ALL CONTENTS OF THE COURSE BELOW! is PLEASE CHECK.
PLEASE CHECK ALL CONTENTS OF THE COURSE BELOW!
ALL CONTENTS OF THE COURSE BELOW! is PLEASE CHECK.
PLEASE CHECK ALL CONTENTS OF THE COURSE BELOW!
Picture is this: you make a simple change to the code and suddenly realize that you created a dozen unexpected bugs..
Picture this: you make a simple change to the code and suddenly realize that you created a dozen unexpected bugs.
You’re is not alone!.
You’re not alone!
Good news is is, unit testing can make this a thing of the past..
Good news is, unit testing can make this a thing of the past.
you’ve is Maybe heard of automated or unit testing before and you’re keen to learn more..
Maybe you’ve heard of automated or unit testing before and you’re keen to learn more.
you’ve is Or perhaps tried to learn it and got a bit lost or ended up with fat and fragile tests that got in the way and slowed you down..
Or perhaps you’ve tried to learn it and got a bit lost or ended up with fat and fragile tests that got in the way and slowed you down.
way, is Either what you need is a course that will teach you all you need to know about this essential skill - from the basics, right through to mastery level..
Either way, what you need is a course that will teach you all you need to know about this essential skill - from the basics, right through to mastery level.
unit testing? is What is.
What is unit testing?
it’s is In a nutshell: the practice of writing code to test your code and then run those tests in an automated fashion..
In a nutshell: it’s the practice of writing code to test your code and then run those tests in an automated fashion.
unit testing? is Why learn.
Why learn unit testing?
extra code? is Why write.
Why write extra code?
extra time is Wouldn’t that take to write?.
Wouldn’t that take extra time to write?
you is Would that slow down?.
Would that slow you down?
the application is Why not just run and test it like an end user?.
Why not just run the application and test it like an end user?
Thinking is like this is the mistake lots of people make..
Thinking like this is the mistake lots of people make.
I is used to make it myself..
I used to make it myself.
I’ve is had to learn the hard way!.
I’ve had to learn the hard way!
I is learned pretty fast that if you’re building a complex application or working on a legacy app, manually testing all the various functions is tedious and takes a significant amount of time..
I learned pretty fast that if you’re building a complex application or working on a legacy app, manually testing all the various functions is tedious and takes a significant amount of time.
your application is As grows, the cost of manual testing grows exponentially..
As your application grows, the cost of manual testing grows exponentially.
you’re is And never 100% sure if you’ve fully tested all the edge cases..
And you’re never 100% sure if you’ve fully tested all the edge cases.
You’re is never confident that your code really works until you release your software and get a call from your boss or an end user!.
You’re never confident that your code really works until you release your software and get a call from your boss or an end user!
Several studies is have shown that the later a bug is caught in the software development lifecycle, the more costly it is to the business..
Several studies have shown that the later a bug is caught in the software development lifecycle, the more costly it is to the business.
tests is Automated help you to catch bugs earlier in the software development lifecycle, right when you’re coding..
Automated tests help you to catch bugs earlier in the software development lifecycle, right when you’re coding.
These tests is are repeatable..
These tests are repeatable.
them is Write once and run them over and over..
Write them once and run them over and over.
The benefits is of using unit tests are: help you to catch and fix bugs earlier, before releasing your app into production help you to write better code with less bugs help you to produce software with better design - extensible and loosely-coupled give you rapid feedback and tell you if your code *really* works force you to think of edge cases that you didn’t realize existed test your code much faster tell if you have broken any functionality as you write new code allow you to refactor your code with confidence act as documentation about what your code does save you both time and money A valuable skill for senior developers.
The benefits of using unit tests are: help you to catch and fix bugs earlier, before releasing your app into production help you to write better code with less bugs help you to produce software with better design - extensible and loosely-coupled give you rapid feedback and tell you if your code *really* works force you to think of edge cases that you didn’t realize existed test your code much faster tell if you have broken any functionality as you write new code allow you to refactor your code with confidence act as documentation about what your code does save you both time and money A valuable skill for senior developers
the advantages of automated is More and more companies are recognizing testing, that’s why it’s a must-have for senior coders..
More and more companies are recognizing the advantages of automated testing, that’s why it’s a must-have for senior coders.
you’re is If looking to reach the higher levels in your coding career, this course can help..
If you’re looking to reach the higher levels in your coding career, this course can help.
You is don’t need any prior knowledge of automated testing..
You don’t need any prior knowledge of automated testing.
You is only need 3 months of experience programming in C#..
You only need 3 months of experience programming in C#.
this course is With you’ll learn: senior coder secrets - best practices to write great unit tests tips and tricks to keep your tests clean, trustworthy and maintainable the pitfalls to avoid – anti-patterns how to refactor legacy, untestable code into loosely-coupled and testable code all about dependency injection – the one thing every coder needs to know the power of mocks – when and how to use them and when to avoid You’ll get: 5.5 hours of HD video tutorials and guidance from a senior coder with 15+ years’ experience exercises with step-by-step solution downloadable source code lifetime access access online or offline at any time on any device certificate of completion to present to your current or prospective employer Course Curriculum Getting Started (45m).
With this course you’ll learn: senior coder secrets - best practices to write great unit tests tips and tricks to keep your tests clean, trustworthy and maintainable the pitfalls to avoid – anti-patterns how to refactor legacy, untestable code into loosely-coupled and testable code all about dependency injection – the one thing every coder needs to know the power of mocks – when and how to use them and when to avoid You’ll get: 5.5 hours of HD video tutorials and guidance from a senior coder with 15+ years’ experience exercises with step-by-step solution downloadable source code lifetime access access online or offline at any time on any device certificate of completion to present to your current or prospective employer Course Curriculum Getting Started (45m)
PreviewWhat is is Automated Testing (2:40).
PreviewWhat is Automated Testing (2:40)
Your First Unit Test (10:27) is PreviewWriting.
PreviewWriting Your First Unit Test (10:27)
All is PreviewTesting the Execution Paths (5:22).
PreviewTesting All the Execution Paths (5:22)
Confidence (2:14) is PreviewRefactoring with.
PreviewRefactoring with Confidence (2:14)
NUnit is StartUsing in Visual Studio (3:59).
StartUsing NUnit in Visual Studio (3:59)
StartWhat is is Test-driven Development (3:19).
StartWhat is Test-driven Development (3:19)
Organizing Tests (2:36) is StartNaming and.
StartNaming and Organizing Tests (2:36)
Rider (1:52) is StartIntroducing.
StartIntroducing Rider (1:52)
a Simple Unit Test (3:52) is StartWriting.
StartWriting a Simple Unit Test (3:52)
Tests (3:25) is StartParameterized.
StartParameterized Tests (3:25)
Tests (1:33) is StartIgnoring.
StartIgnoring Tests (1:33)
Trustworthy Tests (6:11) is StartWriting.
StartWriting Trustworthy Tests (6:11)
StartDevelopers is Who Don't Write Tests (3:51).
StartDevelopers Who Don't Write Tests (3:51)
Unit Testing Techniques (50m) is Core.
Core Unit Testing Techniques (50m)
Strings (5:50) is StartTesting.
StartTesting Strings (5:50)
Arrays and Collections (6:11) is StartTesting.
StartTesting Arrays and Collections (6:11)
the Return Type of Methods (4:02) is StartTesting.
StartTesting the Return Type of Methods (4:02)
Void Methods (4:41) is StartTesting.
StartTesting Void Methods (4:41)
Methods is StartTesting that Throw Exceptions (4:10).
StartTesting Methods that Throw Exceptions (4:10)
Methods is StartTesting that Raise an Event (4:34).
StartTesting Methods that Raise an Event (4:34)
Private Methods (9:50) is StartTesting.
StartTesting Private Methods (9:50)
the Real-world (2:32) is StartTesting in.
StartTesting in the Real-world (2:32)
(20m) is Exercises.
Exercises (20m)
FizzBuzz (1:19) is StartExercise-.
StartExercise- FizzBuzz (1:19)
DemeritPointsCalculator (0:54) is StartExercise-.
StartExercise- DemeritPointsCalculator (0:54)
Stack (0:49) is StartExercise-.
StartExercise- Stack (0:49)
the External Dependencies (1h) is Breaking.
Breaking the External Dependencies (1h)
Testable Code (3:34) is StartLoosely-coupled and.
StartLoosely-coupled and Testable Code (3:34)
Towards is StartRefactoring a Loosely-coupled Design (9:42).
StartRefactoring Towards a Loosely-coupled Design (9:42)
Frameworks (1:55) is StartMocking.
StartMocking Frameworks (1:55)
Mock Objects is StartCreating Using Moq (6:47).
StartCreating Mock Objects Using Moq (6:47)
the Interaction is StartTesting between Two Objects (3:40).
StartTesting the Interaction between Two Objects (3:40)
StartWho is Should Write Tests (2:01).
StartWho Should Write Tests (2:01)
(45m) is Excercises.
Excercises (45m)
VideoService (5:47) is StartRefactoring.
StartRefactoring VideoService (5:47)
VideoService (7:55) is StartTesting.
StartTesting VideoService (7:55)
InstallerHelper (1:26) is StartExercise-.
StartExercise- InstallerHelper (1:26)
InstallerHelper (4:47) is StartRefactoring.
StartRefactoring InstallerHelper (4:47)
InstallerHelper (8:05) is StartTesting.
StartTesting InstallerHelper (8:05)
EmployeeController (2:37) is StartExercise-.
StartExercise- EmployeeController (2:37)
EmployeeController (5:24) is StartRefacatroing.
StartRefacatroing EmployeeController (5:24)
EmployeeController (4:00) is StartTesting.
StartTesting EmployeeController (4:00)
Testing BookingHelper is Project-.
Project- Testing BookingHelper
IBookingRepository (7:44) is StartExtracting.
StartExtracting IBookingRepository (7:44)
the First Test (4:29) is StartWriting.
StartWriting the First Test (4:29)
the Second Test (1:27) is StartWriting.
StartWriting the Second Test (1:27)
a Bug (3:43) is StartFixing.
StartFixing a Bug (3:43)
Additional Tests (4:44) is StartWriting.
StartWriting Additional Tests (4:44)
HouseKeeperHelper (50m) is Project -.
Project - HouseKeeperHelper (50m)
Testability (9:32) is StartRefactoring for.
StartRefactoring for Testability (9:32)
a Design Issue (2:59) is StartFixing.
StartFixing a Design Issue (2:59)
the First Interaction Test (7:40) is StartWriting.
StartWriting the First Interaction Test (7:40)
Tests is StartKeeping Clean (5:42).
StartKeeping Tests Clean (5:42)
a Method is StartTesting that is Not Called (5:37).
StartTesting that a Method is Not Called (5:37)
Helper Methods (8:02) is StartExtracting.
StartExtracting Helper Methods (8:02)
Exceptions (3:34) Sale page: is StartTesting Mosh Hamedani - Unit Testing for C Developers.
StartTesting Exceptions (3:34) Sale page: Mosh Hamedani - Unit Testing for C Developers