|
来源:http://www.sqaforums.com/showfla ... p;page=0#Post242968
发贴人:Jeanj
翻译:AlexanderIII
"Let me address the template question first.
In my opinion, templates sometimes cause more stumbling blocks than they they are worth. Every project is different, and not one will fit exactly into the template. I prefer to create a list of my own on what I plan to test. I'll read the requirements, and use a highlighter on the features so that when I create my test documents, I remember to test those features. Maybe a check list will help you.
Now the testing life cycle is actually very simply described. Remember when you were about 12 and were taught how to write a composition, that it contains 3 parts. Introduction, Body & Conclusion. That's the same with the testing life cycle.
- What you are planning to test (Test Plan)
- What you are testing (Test cases and steps)
- What you tested (Test Report)
Don't forget that you will be in continuous improvement afterwards, so you will be refining your tests for the next iteration of software."
这是我在QAforums.com上看到的一个版主回一个新人的贴子,翻译过来应该对测试文件模版与测试生命周期有个最浅显的理解.
"让我先讲讲模版的问题.依我看来,有时候由模版所引起的阻滞代价会比模版本身的价值要高.每一个项目都是不一样的,没有一个项目是可以确切的和模版相符.我更喜欢根据我要计划测试的东西来创建一个列表.然后我会读需求并用萤光笔划一下相关的特性,避免在我创建测试文档的时候,对这些特性有所遗漏.也许一个检查表(checklist)会对你有所帮助. 如今,测试生命周期是可以被描述得非常简单的.还记得你小时候,老师教你怎么写作文的吗?它分为三部分,事情的起因,经过,与结尾(译者按,引用了一下中国的小学经验,也许大家对这种译法会比较喜欢,呵呵.)测试生命周期与它是一样的.
-你要计划测试什么?(测试计划)
-你要测试什么?(测试用例和步骤)
-你测试得出什么?(测试报告)
不要忘记之后你还要持续不断的改进提高它,这样,你就可以在测试下一个软件版本的时候,更加精确的来进行测试了." |
|