Clean Code – How to Write Amazing Unit Tests

1

Introduction

00:00 • 3min

2

The Seven Minute Workout for the Amazon Echo Dot

03:28 • 5min

3

Using Your Practical Knowledge, the Experience You've Gained Overtime

08:30 • 2min

4

I'm Trying to Learn Angular Tooye

10:05 • 2min

5

Getting a Copy of Clan Code?

12:18 • 2min

6

YU Should Watch the Video and See What's Going On

14:46 • 2min

7

Alete, I Love Unit Tests

16:31 • 2min

8

You May Not Write Production Code Until You Have Written a Failing Unit Test

18:07 • 2min

9

Is Dirty Tests Better Than No Test Code?

20:32 • 2min

10

Is There a Point in Writing Testable Tests?

22:51 • 4min

11

Is Your Test Code as Important as Your Production Code?

26:28 • 3min

12

Coating Blocks Dot Net, Slash Reviews and Hook Us Up

29:27 • 3min

13

I'm in the Same Boat, My Friends

32:18 • 3min

14

Test Readability in Unit Tests

35:16 • 2min

15

Is There an Intigration Test?

37:02 • 2min

16

The Density of Expression

39:02 • 5min

17

The Giveen Wind and the Giveen Syntax

44:10 • 5min

18

Unit Tests for Tia, No Enterprise, Large Solution

48:49 • 3min

19

Is There a Single Assert Versus Multiple Assess?

51:34 • 2min

20

Is the Current State Equal to This String?

53:26 • 5min

21

I Don't Care About the Assertion, Right?

58:26 • 2min

22

Is It Possible to Assert a Unit Test?

01:00:49 • 4min

23

Test Depends on Each Other or a Specific Order?

01:04:37 • 2min

24

The Three Laws, Part 2

01:06:27 • 5min

25

How to Write a Unit Test in Visual Studio

01:11:51 • 5min

26

How to Get Free Stickers for Coating Blocks

01:16:53 • 4min