CodeWithMosh - Unit Testing for C sharp Developers [AhLaN]
movies, software, shows...
Files
| 001 What is Automated Testing~.mp4 | 5.6 MB | ||
| 002 Benefits of Automated Testing~.mp4 | 10.9 MB | ||
| 003 Types of Tests~.mp4 | 18.9 MB | ||
| 004 Test Pyramid~.mp4 | 5 MB | ||
| 005 The Tooling~.mp4 | 13 MB | ||
| 006 Source Code~.mp4 | 338.8 KB | ||
| 006 source-code-completed-1~.zip | 22 MB | ||
| 006 source-code-starter-1~.zip | 19.2 MB | ||
| 007 Writing Your First Unit Test~.mp4 | 15.5 MB | ||
| 008 Testing All the Execution Tests~.mp4 | 11.6 MB | ||
| 009 Refactoring with Confidence~.mp4 | 4.4 MB | ||
| 010 Using NUnit in Visual Studio~.mp4 | 9.2 MB | ||
| 011 What is Test-Driven Development~.mp4 | 6.6 MB | ||
| 012 Course Structure~.mp4 | 7.1 MB | ||
| 013 Summary~.mp4 | 1.3 MB | ||
| 014 Asking Questions~.html | 1.7 KB | ||
| 015 Introduction~.mp4 | 1.4 MB | ||
| 016 Characteristics of Good Unit Tests~.mp4 | 4 MB | ||
| 017 What to Test and What Not to Test~.mp4 | 8.6 MB | ||
| 018 Naming and Organizing Tests~.mp4 | 6.9 MB | ||
| 019 Introducing Rider~.mp4 | 3.7 MB | ||
| 020 Writing a Simple Unit Test~.mp4 | 5.8 MB | ||
| 021 Black-box Testing~.mp4 | 11.5 MB | ||
| 022 Set Up and Tear Down~.mp4 | 6 MB | ||
| 023 Parameterized Tests~.mp4 | 8.6 MB | ||
| 024 Ignoring Tests~.mp4 | 2.3 MB | ||
| 025 Writing Trustworthy Tests~.mp4 | 14 MB | ||
| 026 Developers Who Dont Write Tests~.mp4 | 22.9 MB | ||
| 027 Summary~.mp4 | 2.6 MB | ||
| 028 Introduction~.mp4 | 763 KB | ||
| 029 Testing Strings~.mp4 | 9.8 MB | ||
| 030 Testing Arrays and Collections~.mp4 | 9.9 MB | ||
| 031 Testing the Return Type of Methods~.mp4 | 6.1 MB | ||
| 032 Testing Void Methods~.mp4 | 7.3 MB | ||
| 033 Testing Methods that Throw Exceptions~.mp4 | 6.9 MB | ||
| 034 Testing Methods that Raise an Event~.mp4 | 7.4 MB | ||
| 035 Testing Private Methods~.mp4 | 15.7 MB | ||
| 036 Code Coverage~.mp4 | 7 MB | ||
| 037 Testing in the Real-world~.mp4 | 15.9 MB | ||
| 038 Summary~.mp4 | 1.5 MB | ||
| 039 19- Exercise- FizzBuzz~.mp4 | 2 MB | ||
| 040 20- Solution- FizzBuzz~.mp4 | 9.4 MB | ||
| 041 Exercise- DemeritPointsCalculator~.mp4 | 1.5 MB | ||
| 042 Solution- DemeritPointsCalculator~.mp4 | 26.5 MB | ||
| 043 Exercise- Stack~.mp4 | 1.4 MB | ||
| 044 Solution- Stack~.mp4 | 26.7 MB | ||
| 045 Introduction~.mp4 | 6.1 MB | ||
| 046 Loosely-coupled and Testable Code~.mp4 | 8.5 MB | ||
| 047 Refactoring Towards a Loosely-coupled Design~.mp4 | 14.5 MB | ||
| 048 Dependency Injection via Method Parameters~.mp4 | 8.4 MB | ||
| 049 Dependency Injection via Properties~.mp4 | 4.6 MB | ||
| 050 Dependency Injection via Constructor~.mp4 | 10.6 MB | ||
| 051 Dependency Injection Frameworks~.mp4 | 5.7 MB | ||
| 052 Mocking Frameworks~.mp4 | 3.2 MB | ||
| 053 Creating Mock Objects Using Moq~.mp4 | 12.4 MB | ||
| 054 State-based vs. Interaction Testing~.mp4 | 3.6 MB | ||
| 055 Testing the Interaction Between Two Objects~.mp4 | 6.9 MB | ||
| 056 Fake as Little As Possible~.mp4 | 6.9 MB | ||
| 057 An Example of a Mock Abuse~.mp4 | 7.5 MB | ||
| 058 Who Should Write Tests~.mp4 | 8.9 MB | ||
| 059 Exercise- VideoService~.mp4 | 1.6 MB | ||
| 060 Refactoring~.mp4 | 9.9 MB | ||
| 061 Testing~.mp4 | 14.9 MB | ||
| 062 Exercise- InstallerHelper~.mp4 | 2.2 MB | ||
| 063 Refactoring InstallerHelper~.mp4 | 7.5 MB | ||
| 064 Testing InstallerHelper~.mp4 | 14.1 MB | ||
| 065 Exercise- EmployeeHelper~.mp4 | 4.1 MB | ||
| 066 Refactoring EmployeeController~.mp4 | 9.1 MB | ||
| 067 Testing EmployeeController~.mp4 | 7 MB | ||
| 068 Introduction~.mp4 | 5 MB | ||
| 069 Test Cases~.mp4 | 8.1 MB | ||
| 070 Extracting IBooking Repository~.mp4 | 17.3 MB | ||
| 071 Writing the First Test~.mp4 | 11.6 MB | ||
| 072 Refactoring~.mp4 | 20.9 MB | ||
| 073 Writing the Second Test~.mp4 | 4.4 MB | ||
| 074 Fixing a Bug~.mp4 | 11.5 MB | ||
| 075 Writing Additional Tests~.mp4 | 14.9 MB | ||
| 076 Introduction~.mp4 | 7.4 MB | ||
| 077 Refactoring For Testability~.mp4 | 18.6 MB | ||
| 078 Fixing a Design Issue~.mp4 | 7.2 MB | ||
| 079 An Alternative Solution~.html | 1.7 KB | ||
| 080 Writing the First Interaction Test~.mp4 | 20.6 MB | ||
| 081 Keeping Tests Clean~.mp4 | 16.3 MB | ||
| 082 Testing a Method is Not Called~.mp4 | 15.7 MB | ||
| 083 Another Interaction Test~.mp4 | 15 MB | ||
| 084 Extracting Helper Methods~.mp4 | 19.8 MB | ||
| 085 Testing Exceptions~.mp4 | 10.3 MB | ||
| 086 Coupons to My Other Courses~.html | 2 KB | ||
| Download - Lynda,Udemy,Skillshare,Teamtreehouse,Frontend Masters,Pluralsight,Phlearn,Coursera,Egghead,MasterClass~.txt | 204 B | ||
| Downloaded from Ahlanedu.com~.txt | 1 KB | ||
| Visit us at www.Ahlanedu.com~.url | 0 B | ||
| ▲ 91 total files | |||
Description
---------------------------------------------------------------------------------
-----------------------------------------------------------------------------------
Proudly Presents
-----------------------------------------------------------------------------------
Code With Mosh - Unit Testing for C# Developers [AhLaN]
SUPPLiER.......: WWW RELEASE DATE......: 02/10/20
Uploader.......: abidmail Collector.........: abidmail
... About This Course ...
Why learn unit testing?
Why write extra code? Wouldn’t that take extra time to write? Would that slow you down? Why not just run the application and test it like an end user?
Thinking like this is the mistake lots of people make. I used to make it myself. I’ve had to learn the hard way!
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.
As your application grows, the cost of manual testing grows exponentially. And you’re never 100% sure if you’ve fully tested all the edge cases. 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 have shown that the later a bug is caught in the software development lifecycle, the more costly it is to the business.
Automated tests help you to catch bugs earlier in the software development lifecycle, right when you’re coding. These tests are repeatable. Write them once and run them over and over.
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
All Comments