about summary refs log tree commit diff
path: root/usth/ICT2.7/P4L1 General Concepts Subtitles/1 - Lesson Overview - lang_en_vs5.srt
blob: df7cdbe8ac8ffdc6b60c5e5f66a817f355d1f7cf (plain) (blame)
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
1
00:00:00,700 --> 00:00:03,682
Hello, and welcome back. In the previous

2
00:00:03,682 --> 00:00:07,160
mini course we covered software design, discussed the

3
00:00:07,160 --> 00:00:10,020
UML and the unified software process, and worked

4
00:00:10,020 --> 00:00:12,160
on a complex project in which we developed

5
00:00:12,160 --> 00:00:16,020
a distributed software system. In this mini course,

6
00:00:16,020 --> 00:00:17,900
which is the last one for this class,

7
00:00:17,900 --> 00:00:21,080
we will cover my very favorite topic, software

8
00:00:21,080 --> 00:00:24,850
testing or more generally, software verification and validation.

9
00:00:25,860 --> 00:00:28,850
So why do I love software testing? Well,

10
00:00:28,850 --> 00:00:32,430
I love it because it is extremely important. It

11
00:00:32,430 --> 00:00:38,330
is very challenging and it is fun but only if you do it in the right way.

12
00:00:38,330 --> 00:00:40,900
In the upcoming lessons we will discuss why

13
00:00:40,900 --> 00:00:44,710
software verification is important, why software testing, which is

14
00:00:44,710 --> 00:00:47,730
a specific type of verification, is important, and

15
00:00:47,730 --> 00:00:50,730
what are the main techniques for performing software testing.

16
00:00:51,910 --> 00:00:54,866
We will also discuss test-driven development and agile methods,

17
00:00:54,866 --> 00:00:57,780
in which we'll lose some of the rigidity of

18
00:00:57,780 --> 00:01:01,340
the earlier processes and turn things around by writing

19
00:01:01,340 --> 00:01:04,260
tests before we write the code and then writing

20
00:01:04,260 --> 00:01:08,280
code that makes the test pass. Finally, we will

21
00:01:08,280 --> 00:01:10,750
perform a project, in which you get to apply

22
00:01:10,750 --> 00:01:14,010
most of the principles and practices of agile development

23
00:01:14,010 --> 00:01:17,430
in a realistic scenario. So let's jump right in.