[ Last edited by mouse1x on 2004-12-23 at 12:26 ]作者: jojoo 时间: 2004-12-23 17:11
好,谢谢!作者: christine1230 时间: 2004-12-29 20:51
怎么没人介绍哈网游测试呢5555555555555作者: baitest 时间: 2005-1-19 17:15 标题: 我试试! 1。软件测试的生命周期和开发的生命周期相同;
2。流程图:测试计划---审查---通过---实施---审查---通过---bug管理等---审查确认----修改完善----回归测试----确认---发布等,其中包括检查点的走查等;
3。针对缺陷应当采取对缺陷的确认、审查、修改和再确认、审查、修改,直到缺陷排除。
4。测试评估是软件质量管理的范畴,包括测试计划的制定、审查,缺陷得审查、确认。主要是对软件测试各个阶段的有效的管理和文档的审查,已确定软件测试是否按照测试的计划、流程进行,并满足软件设计的要求和计划。
5。黑盒 侧外不测内,即使黑盒测试完美,但也不能保证软件在设计阶段的代码符合设计的要求和规范,因为测试有静态和动态测试。往往在软件运行一段时间后,问题才暴露出来,这时再去做白盒测试,恐怕代价会无限大的。
6。测试结束的标准应当是测试计划、软件设计要求和用户的最终验收通过为准。
7。除了基本的测试外,应还有生命周期测试。作者: YNGXLI 时间: 2005-5-4 08:37 标题: 测试结束的标准是什么? This can be difficult to determine when to stop testing. Many modern software application are so complex, and run such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:
1. Deadlines (release deadlines, testing deadlines, etc.)
2. Test cases completed with certain percentage passed
3. Test budget depleted
4. Coverage of code/functionality/requirements reaches a specified point
5. Bug rate fails below a certain level
6. Beta or alpha testing period ends作者: YNGXLI 时间: 2005-5-4 08:57 标题: 针对缺陷采取怎样管理措施? I have a similar question: What should be done after a bug is found?
An reference answer:
The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested, and determinations made regarding requirments for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. The following are items to consider in the tracking process:
1. Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary.
2. Bug identifier (number, ID, etc.)
3. Current bug status (e.g. 'Released for Retest', 'New', etc.)
4. The application name or identifier and version
5. The function, module, feature, object, screen, etc. where the bug occurred
6. Environment specifics, system, platform, relevant hardware specifics
7. Test case name/number/identifier
8. One-line bug description
9. Full bug description
10. Description of steps needed to reproduce the bug if not covered by a test case or if the developer doesn't have easy access to the test case/test script/test tool
11. Names and/or descriptions of file/data/messages/etc. used in test
12. File excerpts/error messages/log file excerpts/screen shots/test tool logs that would be helpful in finding the cause of the problem
13. Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common)
14. Was the bug reproducible?
15. Tester name
16. Test date
17. Bug reporting date
18. Name of developer/group/organizaiton the problem is assigned to
19. Description of problem cause
20. Description of fix
21. Code section/file/module/class/method that was fixed
22. Date of fix
23. Application version that contains the fix
24. Tester responsible for retest
25. Retest date
26. Retest results
27. Regression testing requirements
28. Tester responsible for regression tests
29. Regression testing results
A reporting or tracking process should enable notification of appropriate personnel at various stages. For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers.作者: YNGXLI 时间: 2005-5-4 09:03 标题: 如果能够执行完美的黑盒测试,还需要进行白盒测试吗?为什么? - Logic errors and incorrect assumptions most likely to be made when coding for 'special cases'. Need to ensure these execution paths are tested.
- May find assumptions about execution paths incorrect, and so make design errors. White box testing can find these errors.
- Typographical errors are random. Just as likely to be on an obscure logical path as on a mainstream path.作者: jschenjuan 时间: 2005-5-8 17:20 标题: 我也想知道答案啊???? 我也想知道答案啊????作者: yikuang2004 时间: 2005-5-19 15:19
谢谢元老的回答.学到了很多!作者: 爱情鸟 时间: 2005-5-19 15:51
我现在就是为这个测试结束的标准而感到烦,不知道我这二个项目到底有没有测完。作者: zys3497 时间: 2005-5-25 13:36
有点意思
理论的系统化还是很必要的作者: walker_lai 时间: 2006-9-1 18:01 标题: 回复 #1 bobli 的帖子 学习下先啊