From b2d80610db6beda38573890ed169815e495bc663 Mon Sep 17 00:00:00 2001 From: Nguyễn Gia Phong Date: Sun, 24 May 2020 16:34:31 +0700 Subject: [usth/ICT2.7] Engineer software --- .../3 - Introduction - lang_en_vs4.srt | 27 ++++++++++++++++++++++ 1 file changed, 27 insertions(+) create mode 100644 usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt (limited to 'usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt') 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 new file mode 100644 index 0000000..7631180 --- /dev/null +++ b/usth/ICT2.7/P4L5 Software Refactoring Subtitles/3 - Introduction - lang_en_vs4.srt @@ -0,0 +1,27 @@ +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. -- cgit 1.4.1