一些典型测试错误
The role of testing
测试的作用
· Thinking the testing team is responsible for assuring quality.
· 认为测试小组应当负责质量保证。
· Thinking that the purpose of testing is to find bugs.
· 认为测试的目的是发现 bug。
· Not finding the important bugs.
· 找不到重要的 bug。
· Not reporting usability problems.
· 不报告可用性问题。
· No focus on an estimate of quality (and on the quality of that estimate).
· 不能集中于质量评估(以及这种评估的质量)
· Reporting bug data without putting it into context.
· 没有放到具体环境中报告 bug 数据。
· Starting testing too late (bug detection, not bug reduction)
· 测试开始得太晚(发现了 bug，但不能减少 bug)
Planning the complete testing effort
计划完整地测试工作
· A testing effort biased toward functional testing.
· 测试工作偏重于功能测试。
· Underemphasizing configuration testing.
· 低估了配置测试的重要性。
· Putting stress and load testing off to the last minute.
· Not testing the documentation
· 不测试文档。
· Not testing installation procedures.
· 不测试安装过程。
· An overreliance on beta testing.
· 过分依赖β测试。
· Finishing one testing task before moving on to the next.
· 完成一个任务之后才进行下一个。
· Failing to correctly identify risky areas.
· 不能正确识别危险领域。
· Sticking stubbornly to the test plan.
· 固执地坚持测试计划。
Personnel issues
人员问题
· Using testing as a transitional job for new programmers.
· 将测试做为新程序员的过渡工作。
· Recruiting testers from the ranks of failed programmers.
· 从不合格的程序员中招募测试员。
· Testers are not domain experts.
· 测试员不是领域专家
· Not seeking candidates from the customer service staff or technical writing staff.
· 不从客户服务人员或技术文档写作人员中寻求申请人。
· Insisting that testers be able to program.
· 坚持认为测试员应当会编程，
· A testing team that lacks diversity.
· 测试小组缺乏多样性。
· A physical separation between developers and testers.
· 开发人员和测试员在物理位置上的隔离。
· Believing that programmers can't test their own code.
· 认为程序员不能测试他们自己的代码。
· Programmers are neither trained nor motivated to test.
· 程序员既没有接受过培训，对测试也没有热情。
The tester at work
工作中的测试员
· Paying more attention to running tests than to designing them.
· 将更多的注意力集中于运行测试而不是设计它们
· Unreviewed test designs.
· 未经审核的测试设计。
· Being too specific about test inputs and procedures.
· 过于注重测试输入和过程的细节。
· Not noticing and exploring "irrelevant" oddities.
· 不能注意和探索“不相关的”奇怪现象
· 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.
· 检查产品完成预期操作，但不检查它是否没有完成不应该完成的操作
· Test suites that are understandable only by their owners.
· 测试套件只有它们的作者才能理解。
· Testing only through the user-visible interface.
· 只测试用户可见的界面。
· Poor bug reporting.
· 低劣的 bug 报告。
· Adding only regression tests when bugs are found.
· 在发现 bug 时仅添加回归测试
· Failing to take notes for the next testing effort.
· 不能为下次测试工作做好记录
Test automation
测试自动化
· Attempting to automate all tests.
· 试图自动化所有的测试
· Expecting to rerun manual tests.
· 期望重新运行所有的手工测试。
· Using GUI capture/replay tools to reduce test creation cost.
· 使用GUI捕获/回放工具减少创建测试的成本。
· Expecting regression tests to find a high proportion of new bugs.
· 期望回归测试发现高比例的新 bug。
Code coverage
代码覆盖率
· Embracing code coverage with the devotion that only simple numbers can inspire.
· 热心采用代码覆盖率，认为只有那些简单的数字可以鼓舞士气。
· Removing tests from a regression test suite just because they don't add coverage.
· 因为有些测试不能增加覆盖率而将它们从回归测试套件中去掉。
· Using coverage as a performance goal for testers.
· 使用覆盖率作为测试员的绩效目标。
· Abandoning coverage entirely.
· 完全放弃了覆盖率。
文章来源于领测软件测试网 https://www.ltesting.net/
