1
00:00:00,660 --> 00:00:01,500
Instructor: All right, my friends,

2
00:00:01,500 --> 00:00:04,050
we've wrapped up our first testing application here

3
00:00:04,050 --> 00:00:06,570
and I think we've learned a whole lot along the way.

4
00:00:06,570 --> 00:00:07,500
There's definitely a lot of things

5
00:00:07,500 --> 00:00:09,000
that we could review inside this section

6
00:00:09,000 --> 00:00:11,910
but probably the most important thing I wanna tell you about

7
00:00:11,910 --> 00:00:14,310
is one of the topics we discussed later on.

8
00:00:14,310 --> 00:00:17,793
So the idea of Unit Tests first integration tests.

9
00:00:18,630 --> 00:00:20,430
At the start of this application,

10
00:00:20,430 --> 00:00:22,680
we were first writing out a ton of unit tests

11
00:00:22,680 --> 00:00:24,540
inside of our code base.

12
00:00:24,540 --> 00:00:26,730
Now, there's nothing wrong with doing Unit Tests,

13
00:00:26,730 --> 00:00:30,360
It's definitely a completely valid way of testing a product.

14
00:00:30,360 --> 00:00:32,100
However, I'm gonna make the claim,

15
00:00:32,100 --> 00:00:34,230
based on my personal experience of working

16
00:00:34,230 --> 00:00:36,000
on many different applications,

17
00:00:36,000 --> 00:00:38,880
that we tend to get a little bit more value

18
00:00:38,880 --> 00:00:43,170
out of testing when we make use of integration tests.

19
00:00:43,170 --> 00:00:45,060
So even though I showed you how to say,

20
00:00:45,060 --> 00:00:47,430
test an action creator and test a reducer,

21
00:00:47,430 --> 00:00:49,200
I'm not entirely sure, personally,

22
00:00:49,200 --> 00:00:51,240
that that's really the best use of your time

23
00:00:51,240 --> 00:00:53,040
when you go to put together tests.

24
00:00:53,040 --> 00:00:55,590
Now to put together a very complete course

25
00:00:55,590 --> 00:00:56,790
on React and Redux testing,

26
00:00:56,790 --> 00:00:58,569
of course, I showed you how to do that stuff

27
00:00:58,569 --> 00:01:01,350
so that if you want to, you absolutely can.

28
00:01:01,350 --> 00:01:04,290
There are very serious enterprise products out there

29
00:01:04,290 --> 00:01:07,050
where they want to put in as many Unit Tests as possible.

30
00:01:07,050 --> 00:01:09,540
And so in having knowledge of testing reducers

31
00:01:09,540 --> 00:01:11,880
and action creators one at a time is valuable,

32
00:01:11,880 --> 00:01:14,168
but if you are introducing testing

33
00:01:14,168 --> 00:01:18,780
to a personal project or a small professional project,

34
00:01:18,780 --> 00:01:21,240
I really recommend you try tending towards

35
00:01:21,240 --> 00:01:24,420
the integration test side of the spectrum a little bit more.

36
00:01:24,420 --> 00:01:26,820
You simply get more bang for your buck.

37
00:01:26,820 --> 00:01:27,720
Or in other words,

38
00:01:27,720 --> 00:01:30,240
you are testing or securing more lines

39
00:01:30,240 --> 00:01:32,520
of code with fewer tests

40
00:01:32,520 --> 00:01:34,050
and you'll get some better signals

41
00:01:34,050 --> 00:01:36,570
when something inside your application breaks

42
00:01:36,570 --> 00:01:39,330
because these integration tests really address

43
00:01:39,330 --> 00:01:41,220
how all the different components,

44
00:01:41,220 --> 00:01:44,013
reducers, and action creators fit together.

45
00:01:44,880 --> 00:01:47,460
Okay, so just wanna throw that little note in there.

46
00:01:47,460 --> 00:01:51,690
Again, I'd say try to focus towards this end

47
00:01:51,690 --> 00:01:54,330
of the spectrum as you're getting started with testing.

48
00:01:54,330 --> 00:01:56,550
So I think we've learned a lot with this first application

49
00:01:56,550 --> 00:01:58,380
but we still have a lot more to cover.

50
00:01:58,380 --> 00:01:59,700
So let's take a quick break

51
00:01:59,700 --> 00:02:01,443
and continue in the next section.