1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
|
1
00:00:00,360 --> 00:00:03,320
As you probably realized by now, at job development, it's a
2
00:00:03,320 --> 00:00:06,280
lot about testing. So there is a lot of emphasis on
3
00:00:06,280 --> 00:00:09,420
testing. Testing first, te, testing early. So that's the reason why
4
00:00:09,420 --> 00:00:12,710
I also want to discuss what is the testing strategy in XP.
5
00:00:12,710 --> 00:00:14,820
So first of all what is the basic principle? The basic
6
00:00:14,820 --> 00:00:18,770
principle is that testing is Coded confidence. You write your test
7
00:00:18,770 --> 00:00:22,150
cases and then you can run them anytime you want. And
8
00:00:22,150 --> 00:00:25,540
if they pass, they'll give you confidence that your code is behaving
9
00:00:25,540 --> 00:00:27,920
the way it's expected. If they don't pass on the other
10
00:00:27,920 --> 00:00:30,870
hand, you'll know that there's something to fix. Another important concept is
11
00:00:30,870 --> 00:00:34,600
that test might be isolated and automated. So both the running and
12
00:00:34,600 --> 00:00:37,400
the checking of the tests has to be automated for all of
13
00:00:37,400 --> 00:00:39,830
this to work. And there are two types of tests. The first
14
00:00:39,830 --> 00:00:43,170
type of test is unit tests, that are created by the programmers,
15
00:00:43,170 --> 00:00:45,830
and they're created by looking at the task cards. The task cards
16
00:00:45,830 --> 00:00:48,410
describe what they implemented, functionality should
17
00:00:48,410 --> 00:00:50,740
do, and therefore allows the developers.
18
00:00:50,740 --> 00:00:53,970
The right test that can test this functionality. That can
19
00:00:53,970 --> 00:00:57,000
check that the code's correctly implemented functionality. And as we
20
00:00:57,000 --> 00:01:00,670
said, you should really test every meaninful feature. So, for
21
00:01:00,670 --> 00:01:04,250
example, you should test every meaningful method in your classes.
22
00:01:04,250 --> 00:01:08,490
You should put specific attention to possibly complex implementations, special
23
00:01:08,490 --> 00:01:11,100
cases or specific problems that you might think of. while
24
00:01:11,100 --> 00:01:13,110
reading the task cards. In some cases, when you do
25
00:01:13,110 --> 00:01:15,800
refactoring, you might also want to write test cases specific
26
00:01:15,800 --> 00:01:18,300
to that refactoring. But we'll say more about that. So this
27
00:01:18,300 --> 00:01:20,610
was for the first kind of tests that are involved in
28
00:01:20,610 --> 00:01:23,650
the, in the XP process. The second kind of tests are
29
00:01:23,650 --> 00:01:27,710
the system tests, also called acceptance tests. And those tests involve
30
00:01:27,710 --> 00:01:30,920
the customer. So basically what happens is that the customer provides
31
00:01:30,920 --> 00:01:33,760
the test cases for their stores and then the development team
32
00:01:33,760 --> 00:01:37,630
transforms those into actual automated tests. So these are tests created
33
00:01:37,630 --> 00:01:40,700
by the developers. They run very quickly and they run very frequently.
34
00:01:40,700 --> 00:01:43,120
These are tests developed with the help, with the
35
00:01:43,120 --> 00:01:46,170
involvement of the customer they run longer. And run less
36
00:01:46,170 --> 00:01:48,710
frequently, they run every time the system is integrated.
37
00:01:48,710 --> 00:01:50,890
According to the cycle we saw a few minutes ago.
|
