How do you estimate how long it will take you to test a feature or an application? One rule of thumb I
have seen used often is to copy the development time.
工作中常常会被问到这个问题~~哎，每次都是一拍脑袋就决定，其实还是有方法可寻滴！除了以上，
以下四点也可以作为评估重点
Attribute How to consider this attribute
Historical data At the very least, you can estimate test design based on previous projects.
Complexity Complexity relates directly to testability. Simple applications can be tested more
quickly than complex programs can be.
Business goals Is the application a prototype or demonstration application? Or is it flight control
software for a spaceship? The business goals influence the breadth and depth ofthe testing effort.
Start testing from asking questions
1.Base on FS,Ask how the software is supposed to work. Ask how it handles data. Ask how it
handles errors. and so on.
2.Without FS,base on source code.the best place to get started on test design is by running the application. Ask yourself
questions about how the program should work. You might answer those questions, or they might lead to
more questions. If something is confusing, ask questions. If the source code is available, refer to the
code and, if necessary, ask more questions. Exploratory testing, the act of testing and designing tests at
the same time, can significantly influence test design and is a beneficial part of the overall test design
process.
这个第二点是自己的弱项，讨厌向dev要源码看，一看code就头晕~~嗨~
TDS模板和我们工作中类似：
Example Elements in a Test Design Specification
Following are items that might be found in a typical test design specification:
• 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
Verification tests are necessary to prove that theapplication works as intended。 这句话估计我以后写TDS或者开bug可以用到哦~~