about summary refs log tree commit diff
path: root/usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt
diff options
context:
space:
mode:
Diffstat (limited to 'usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt')
-rw-r--r--usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt27
1 files changed, 0 insertions, 27 deletions
diff --git a/usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt b/usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt
deleted file mode 100644
index 7631180..0000000
--- a/usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt
+++ /dev/null
@@ -1,27 +0,0 @@
-1

-00:00:00,120 --> 00:00:04,280

-So let's have a small quiz and see whether you can remember why can testing

-

-2

-00:00:04,280 --> 00:00:06,250

-guarantee that that a refactoring is behavior is

-

-3

-00:00:06,250 --> 00:00:08,590

-preserving. So why testing can only show the

-

-4

-00:00:08,590 --> 00:00:11,080

-absence of defects and not their presence?

-

-5

-00:00:11,080 --> 00:00:12,960

-Is that because testing and refactoring are different

-

-6

-00:00:12,960 --> 00:00:15,980

-activities? Because testing is inherently incomplete? Or, just

-

-7

-00:00:15,980 --> 00:00:19,560

-because testers are often inexperienced? Make your choice.