匿名网友
● （ English ）翻译下面的内容
An important special case of overlooking bugs is checking that the product does what it’s supposed to do, but not that it doesn’t do what it isn’t supposed to do. As an example, suppose you have a program that updates a health care service’s database of family records. A test adds a second child to Dawn Marick’s record. Almost all testers would check that, after the update, Dawn now has two children. Some testers – those who are clever, experienced, or subject matter experts – would check that Dawn Marick’s spouse, Brian Marick, also now has two children. Relatively few testers would check that no one else in the database has had a child added. They would miss a bug where the programmer over-generalized and assumed that all “family information” updates should be applied both to a patient and to all members of her family, giving Paul Marick (aged 2) a child.
Ideally, every test should check that all data that should be modified has been modified and that all other data has been unchanged. With forethought, that can be built into automated tests. Complete checking may be impractical for manual tests, but occasional quick scans for data that might be corrupted can be valuable.
● （ English ）根据下面的中文内容写一个缺陷报告
我们正在给国外的一家软件公司的“ klsoft ”软件做测试，你发现了一个 bug ，在“ Mkbox ”对话框中输入八位的数字点“ save ”按钮，再次查询后该数字就会变成另外一个数字，而且任何什么规则，如果输入小于八位或者大于八位的数字就不会出现此问题。这个问题在 Win2000 professional 系统存在，其他系统不存在。现在该软件已经投入使用了，所以你感觉到问题的严重性，现在要求你写一封英文的 email 给美国公司的 Simen ，希望他可以帮助转达给相关的负责人员，引起注意，记住 Simen 并不是这部分的负责人，而且他工作很忙，所以要注意措辞。
