The notes of How We Test Software At Microsoft(2)
来源:互联网 发布:信融财富网络借贷 编辑:程序博客网 时间:2024/05/01 03:54
Estimating Test Time
正如书中提到,我周围大多team估算项目的时间都是“simply add a few weeks of “buffer” or “stabilization” time at the end of a product cycle”。这是非常不科学的做法。
也提到一种“copy the development time”的做法,让我想到曾经看过的两篇关于开发和测试人员比例的文章,http://blog.csdn.net/Lynn_yan/archive/2009/09/15/4554687.aspx和http://blog.csdn.net/Lynn_yan/archive/2009/09/15/4554687.aspx。
Starting with Testing-Ask Questions
If requirement aren’t available (or if they aren’t good), the best place to start test design is probably by asking questions. Ask how the software is supposed to work. Ask how it handles data. Ask how it handles errors. Asking questions about the software can help testers get a jumpstart on design before any of the code is ever written.
当缺少文档,提出问题并尝试回答问题,一个问题的答案可能又能引出更多的问题,通过问题去熟悉产品,也可以向开发人员,熟悉产品的测试人员以及其他项目相关人员询问你关于产品的疑惑。另外就是做Exploratory testing, exploratory testing强调的是测试设计和测试执行的“同时”性-这个“同时”是相对于传统软件测试过程中严格的“先设计,后执行”来说的,测试人员可以通过测试来不断学习被测试系统,探索性测试的重点就是创造。
Have a Test Strategy
测试策略包括测试类型,过程,测试方法,以及对代测试产品的风险分析,哪里更容易出错,哪里需要做更多的测试。
Thinking About Testability
Testability是定义一个软件是否能被完全有效测试的程度(Testability is the degree to which software can be tested completely and efficiently.) ,简单的说就是测试的难易程度(How easy is it to Test?)。在需求和设计的review会议上,测试人员要提出问题“我们怎么样去测试”,这样能开发团队成员去更多考虑软件的可测试性。
一个增减软件可测试性的模型:SOCK(首字母缩写词):
1. Simple:简单的模块和程序更容易测试
2. Observable:内部结构可见性好
3. Control:如果一个程序设有临界值,设置或重置这些临界值可以让测试更容易
4. Knowledge:需求,help文档能给测试人员提供更多信息
Test Design Specifications
Test Design Specifications一般包含以下项目:
· Overview/goals/purpose
· Strategy
· Functionality testing
· Component testing
· Integration/system testing
· Interoperability testing
· Compliance/conformance testing
· Internationalization and globalization
· Performance testing
· Security testing
· Setup/deployment testing
· Dependencies
· Metrics
Testing the Good and the Bad
Verification tests are necessary to prove that the application works as intended, but the falsification tests are perhaps even more important. Applications need to be robust and handle bad data without error.
The happy path should always pass, 在这个前提下,要尽可能多的考虑一些异常情况
- The notes of How We Test Software At Microsoft(2)
- The notes of How We Test Software At Microsoft(1)
- The notes of How We Test Software At Microsoft(3)
- The notes of How We Test Software At Microsoft(4)
- The notes of How We Test Software At Microsoft(5)
- The notes of How We Test Software At Microsoft(5)
- The notes of How We Test Software At Microsoft(6)
- The notes of How We Test Software At Microsoft(7)
- Xmind of How We Test Software at Microsoft
- How We Test Software at Microsoft 读书笔记 (一)
- 转载:The Growth of Software Test
- microsoft software test
- How google test software
- How should we evaluate the performance of an DBA?
- How can we double the data rate of 802.11a?
- Test Experience Share: We should consider the impact of the hardware improvement to the test code
- Notes of Managing Software Projects
- 读书笔记 - How Google Test Software
- Linux系统下修改MySQL的root密码
- 试用Libmemcached
- C#发PDU格式串长短信源码
- 实习之初来乍到
- oracle 存储过程的基本语法
- The notes of How We Test Software At Microsoft(2)
- 为Backingbean创建基类
- 传说中的无敌吸星大法
- C语言中位操作用法
- OGRE 去掉设置窗口
- 透明as3截获浏览器鼠标滚轮事件的解决
- 每天做个算法题
- Oracle Function
- 在ADF中为Table自动生成行号