始终显示原文
小黑人

欢迎使用考满分精听听写

截止昨天,已经有 252988 同学完成了 4103155 次的练习

开始练习 查看新手引导

原文已被隐藏,你可用 快捷键 - 或点击 显示原文 按钮来查看原文

第1段

1 .<-NARRATOR:->Listen to part of a lecture in a computer science class. The professor is discussing software engineering.

旁白:听下面一段计算机科学的课程讲解。教授正在讨论软件工程的问题。

第2段

1 .<-MALE PROFESSOR:->We've been talking about the software development cycle, and today I'd like to move on to the next stage of that cycle... testing... and why finding bugs during testing is actually a great thing.

教授:之前我们一直在讲软件开发周期,今天我们进入下一阶段的讨论-软件测试,以及为何在测试过程中找到bug是件好事。

2 .Ah, uh, th-the quality of a software product often relies heavily on how well it's been tested. Liz?

呃,软件产品的质量往往很大程度在取决于它的测试情况。利兹,有什么问题吗?

第3段

1 .<-FEMALE STUDENT:->Um, just a quick thing. "Bugs" is the word for problems in the program code, correct?

学生:就一个小小的问题,bug是指编程码存在的问题是吗?

第4段

1 .<-MALE PROFESSOR:->Yeah, in code or in a computer itself.

教授:是的,编程码或者计算机本身存在的问题都叫 bug。

2 .There's-there's a bit of a story behind that term.

其实这个术语的背后还有一个小故事。

3 .Um, back in the 1940s, when the computer industry was just starting, a group of computer scientists was working late one night, and there was a problem in one of the computer's circuits.

恩,追溯到 20 世纪 40 年代,那还是计算机产业刚刚起步的时候,几个计算机科学家一直工作到很晚,因为计算机的一个回路出现了问题。

4 .When they examined it, they found a five-centimeter-long moth caught in there.

当他们去检查的时候,发现一个五公分的飞蛾卡在了那里。

5 .Once they "debugged" the computer, it worked just fine.

当他们拿走飞蛾以后,计算机就恢复正常工作了。

6 .And ever since then, all kinds of computer problems have been known as "bugs."

从此以后,所有计算机的问题都被称为“bug”了。

第5段

1 .Anyway, you want to find bugs while the software's still in the development and testing phases.

不管怎么说,bugs 最好是在开发或者测试阶段就被发现。

2 .Finding them when the software product has already been put on the market can be quite embarrassing.

如果当软件产品已经投放市场了才发现 bug 的话,局势就会比较尴尬了。

第6段

1 .Generally speaking, every software development project has a group of testers and a group of developers. Jake?

大致来讲,每个软件工程都有一组开发人员和一组测试人员。杰克?

第7段

1 .<-MALE STUDENT:->And they're different people?

学生:他们都是不同的人吗?

第8段

1 .<-MALE PROFESSOR:->They're generally completely different groups of people.

教授:通常他们是由两组完全不同的人组成。

2 .My personal opinion is that they have to be different groups of people because developers often have a bias toward their own work. And it blinds them to certain problems that might be obvious to somebody else.

我个人的观点是开发人员和测试人员一定要是由两组不同的人来组成,因为软件开发人员总会自己的作品有些偏爱,这就导致他们忽视一些其他人看起来很明显的问题。

3 .So it's always good to have a different set of eyes go in there and make sure that everything's tested properly.

所以说有不同的人来参与到项目中来的话,会使测试更完善。

第9段

1 .OK, now here's the key...

好啦,其实是这样,

2 .developers and testers have different mentalities.

开发人员与测试人员的心态是不一样的。

3 .The mentality of the software developer is constructive,creative. They're spending long hours working together to create and build something new.

软件开发人员是有建设性、有创意性,他们往往花大量的时间来共同创建新的产品。

第10段

1 .A software tester, on the other hand, their entire goal is to look at this product and find problems with it, to improve it.

而软件测试人员的主要任务就是观察这些产品并发现问题,然后来提升软件的质量。

2 .Now this difference between the testers and the developers can lead to an environment where there's a bit of friction.

那么软件开发人员和测试人员之间的这种不同就会引起一点小摩擦。

3 .And that friction sometimes makes it difficult for the two teams to work together.

这种摩擦有时就会使开发人员和测试人员很难在一起协调的工作。

第11段

1 .Um, there were two projects that I worked on a couple of years ago.

两三年前我参与了两个项目。

2 .One, which I'll call Project Split... where the testing and development teams did not work well together.

我称其中的一个为分离项目组,这组的开发人员和测试人员就很难在一起共事。

3 .And the other I'll call Project Unity... during which both teams worked very well together.

另一组我称之为团结项目组,这组人员就合作起来很愉快。

第12段

1 .Now during Project Split, we had defect meetings where the developers and the testers met together, um, uh, to discuss various problems and how they should be fixed.

第一组人员在进行缺陷讨论会议时,也就是开发人员和测试人员在一起讨论各种各样的问题并找出解决方案

2 .And you could sense the conflict just by walking into the room.

你在一进入会议室的时候将就能感到那种冲突的气氛。

3 .Literally-the testers and the developers sat on opposite sides of the table.

准确来讲是,测试人员和开发人员完全对立来坐。

4 .Um, an-and the developers were very defensive about the feedback.

呃,而且开发人员对收到的反馈总是持有怀疑的态度。

第13段

1 .<-MALE STUDENT:->Well, if bugs are being pointed out they wouldn't be too happy, since it's their work.

学生:恩,当 bugs 被指出的时候他们肯定不会开心,毕竟那是他们做的产品嘛。

第14段

1 .<-MALE PROFESSOR:->Exactly. Now 'cause the two teams weren't working well together, the fixes were coming very, very slowly.

教授:的确如此。正因为这两组人员不能协调的工作,所以修正工作总是进行的很缓慢。

2 .And you know, a lot of times when you fix bugs you introduce new bugs... or you discover bugs in other areas that only come to light because something's been changed.

而且正如你们所知道的,有些时候当你在修正 bugs 的时候又会引发一些新的 bugs,或者在进行了一些调整之后,新的 bugs 才显现出来

3 .So fixing all those new additional bugs was also being delayed.

所以说这些新加的 bugs 总是未能及时修复。

4 .Um, the test process went on much longer than expected and we ended up having to put the product on the market with known bugs in it, which was obviously not ideal.

呃,测试的过程比预期的要长得多,我们最终就不得不将存有 bugs 的产品投放市场,当然这并不是明智之举。

第15段

1 .<-FEMALE STUDENT:->OK, and what about Project Unity? How was it different?

学生:好的,那么团结项目组呢?有何不同吗?

第16段

1 .<-MALE PROFESSOR:->Um, this was different because the two teams worked closely together.

教授:恩,这组的不同之处体现于两个团队紧密合作。

2 .During the defect meetings, instead of putting up walls, um, we didn't even talk about, you know, who should fix this, who was at fault.

在缺陷讨论会中,开发人员和测试人员并没有产生对立的局势,而是很好的进行协作,呃,我们甚至无需指明谁来进行修复,这又是谁的错。

3 .We all acknowledged what needed to be fixed.

我们也都知道到底哪些地方需要修复。

4 .So, if we had ten bugs, we said, "Hey, you know what, let's do this one first because this will expose another whole bunch of defects that we haven't even seen yet."

所以,假如说我们有十个 bugs,我们就会说“嘿,不如这样吧,我们先来修复这个吧”,因为这样就可以显露出一系列我们还没有发现的缺陷问题。

5 .So we were being proactive and effective.

所以我们是很有前瞩性和效率性。

第17段

1 .And because we were so much more effective with our time, we were actually able to do more than just fix bugs... we even put in some improvements that we hadn't planned.

正因为我们做事很有效率,我们不仅仅是修复了bug,还能注入一些之前没有计划过的升级元素。