1
00:00:00,000 --> 00:00:02,170
[No Audio]

2
00:00:02,170 --> 00:00:03,524
So now we've marked up a test as

3
00:00:03,524 --> 00:00:05,374
being testable with it @Test annotation.

4
00:00:05,374 --> 00:00:06,716
In this video, we're going to see how we

5
00:00:06,716 --> 00:00:08,599
can run it in the IDE so we can see what

6
00:00:08,599 --> 00:00:11,247
test success actually looks like. So let's jump in

7
00:00:11,247 --> 00:00:13,800
now and pick up where we left off. So click that.

8
00:00:13,800 --> 00:00:17,610
[No Audio]

9
00:00:17,610 --> 00:00:18,859
And you can see here,

10
00:00:18,859 --> 00:00:20,816
[No Audio]

11
00:00:20,816 --> 00:00:22,260
that this is the test class.

12
00:00:22,260 --> 00:00:23,904
These are the test methods which

13
00:00:23,904 --> 00:00:25,520
were found in that class.

14
00:00:25,520 --> 00:00:27,564
And because we have these ticks here, it

15
00:00:27,564 --> 00:00:29,856
means that all of the test methods which

16
00:00:29,856 --> 00:00:31,898
were included in the test class have passed.

17
00:00:31,898 --> 00:00:33,368
In other words, it didn't fail.

18
00:00:33,368 --> 00:00:35,474
And if all of those test methods, if you imagine

19
00:00:35,474 --> 00:00:37,296
if we had a lot of different test methods here,

20
00:00:37,296 --> 00:00:39,684
if all of those test methods pass, and in turn,

21
00:00:39,684 --> 00:00:42,692
the test class itself is deemed to have passed.

22
00:00:42,692 --> 00:00:43,896
And you can also see this here

23
00:00:43,896 --> 00:00:45,695
as well, it says test passed.

24
00:00:45,695 --> 00:00:48,024
1 test passed, out of a total of

25
00:00:48,024 --> 00:00:51,498
1 test, and it took one millisecond. So

26
00:00:51,498 --> 00:00:54,458
that's the @Test annotation, which JUnit provides,

27
00:00:54,458 --> 00:00:57,072
which marks methods in the test class as being

28
00:00:57,072 --> 00:01:00,084
actual test methods, which will appear in this test

29
00:01:00,084 --> 00:01:01,850
runner output because they've been marked for

30
00:01:01,850 --> 00:01:04,818
inclusion as test methods within the test class.

31
00:01:04,818 --> 00:01:06,552
So with unit tests, whenever you see something

32
00:01:06,552 --> 00:01:08,568
that's green, that's generally a good thing.

33
00:01:08,568 --> 00:01:09,708
It means green is good.

34
00:01:09,708 --> 00:01:11,808
Good for go, green for go. All good.

35
00:01:11,808 --> 00:01:12,890
The tests have passed.

36
00:01:12,890 --> 00:01:14,268
So that's always a good thing.

37
00:01:14,268 --> 00:01:16,236
That's what test success looks like.

38
00:01:16,236 --> 00:01:17,376
And we've seen that in this video.

39
00:01:17,376 --> 00:01:18,864
So next video, we're going to explore what

40
00:01:18,864 --> 00:01:21,100
test failure looks like, coming up next.