我希望有很多很多的爱,如果没有很多的爱,我希望有很多很多的钱;没有很多的钱,我希望拥有健康! I am like the road in the night listening to the footfalls of its memories in silence.

软件测试类型知多少?

上一篇 / 下一篇  2007-04-14 13:11:16 / 个人分类:测试转载

软件测试类型知多少?

软件测试的类型多种多样,测试类型与被测软件的测试需求相关。对于初学者,需要了解最常见的测试类型,也有必要了解其他的测试类型,作为进一步提高的目标。 

以下转载了比较齐全的测试类型,请那位朋友帮助把全文翻译一下。

  • 黑盒测试(Black box testing)
    • not based on any knowledge of internal design or code. Tests are based on requirements and functionality.
  • 白盒测试(White box testing)
    • based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, conditions.
  • 单元测试(unit testing)
      
    • the most 'micro' scale of testing; to test particular functions or code modules. Typically done by the programmer and not by testers, as it requires detailed knowledge of the internal program design and code. Not always easily done unless the application has a well-designed architecture with tight code; may require developing test driver modules or test harnesses.
  • 增量集成测试(incremental integration testing)
    • continuous testing of an application as new functionality is added; requires that various aspects of an application's functionality be independent enough to work separately before all parts of the program are completed, or that test drivers be developed as needed; done by programmers or by testers.
  • 集成测试(integration testing)
    • testing of combined parts of an application to determine if they function together correctly. The 'parts' can be code modules, individual applications, client and server applications on a network, etc. This type of testing is especially relevant to client/server and distributed systems.
  • 功能测试(functional testing)
    • black-box type testing geared to functional requirements of an application; this type of testing should be done by testers. This doesn't mean that the programmers shouldn't check that their code works before releasing it (which of course applies to any stage of testing.)
  • 系统测试(system testing)
    • black-box type testing that is based on overall requirements specifications; covers all combined parts of a system.
  • 端到端测试(end-to-end testing)
    • similar to system testing; the 'macro' end of the test scale; involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.
  • 健全测试或冒烟测试(sanity testing or smoke testing)
    • typically an initial testing effort to determine if a new software version is performing well enough to accept it for a major testing effort. For example, if the new software is crashing systems every 5 minutes, bogging down systems to a crawl, or corrupting databases, the software may not be in a 'sane' enough condition to warrant further testing in its current state.
  • 回归测试(regression testing)
    • re-testing after fixes or modifications of the software or its environment. It can be difficult to determine how much re-testing is needed, especially near the end of the development cycle. Automated testing tools can be especially useful for this type of testing.
  • 验收测试(acceptance testing)
    • final testing based on specifications of the end-user or customer, or based on use by end-users/customers over some limited period of time.
  • 负载测试(load testing)
    • testing an application under heavy loads, such as testing of a web site under a range of loads to determine at what point the system's response time degrades or fails.
  • 压力测试(stress testing)
    • term often used interchangeably with 'load' and 'performance' testing. Also used to describe such tests as system functional testing while under unusually heavy loads, heavy repetition of certain actions or inputs, input of large numerical values, large complex queries to a database system, etc.
  • 性能测试(performance testing)
    • term often used interchangeably with 'stress' and 'load' testing. Ideally 'performance' testing (and any other 'type' of testing) is defined in requirements documentation or QA or Test Plans.
  • 易用性测试(usability testing)
    • testing for 'user-friendliness'. Clearly this is subjective, and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions, and other techniques can be used. Programmers and testers are usually not appropriate as usability testers.
  • 安装/卸载测试(install/uninstall testing)
    • testing of full, partial, or upgrade install/uninstall processes.
  • 恢复测试(recovery testing)
    • testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
  • 故障复原测试(failover testing)
    • typically used interchangeably with 'recovery testing'
  • 安全性测试(security testing)
    • testing how well the system protects against unauthorized internal or external access, willful damage, etc; may require sophisticated testing techniques.
  • 兼容性测试(compatability testing)
    • testing how well software performs in a particular hardware/software/operating system/network/etc. environment.
  • 探索性测试(exploratory testing)
    • often taken to mean a creative, informal software test that is not based on formal test plans or test cases; testers may be learning the software as they test it.
  • 随机测试(ad-hoc testing)
    • similar to exploratory testing, but often taken to mean that the testers have significant understanding of the software before testing it.
  • 上下文驱动测试(context-driven testing)
    • testing driven by an understanding of the environment, culture, and intended use of software. For example, the testing approach for life-critical medical equipment software would be completely different than that for a low-cost computer game.
  • 用户验收测试(user acceptance testing)
    • determining if software is satisfactory to an end-user or customer.
  • 对比测试(comparison testing)
    • comparing software weaknesses and strengths to competing products.
  • Alpha 测试(alpha testing)
    • testing of an application when development is nearing completion; minor design changes may still be made as a result of such testing. Typically done by end-users or others, not by programmers or testers.
  • Beta测试(beta testing)
    • testing when development and testing are essentially completed and final bugs and problems need to be found before final release. Typically done by end-users or others, not by programmers or testers.
  • 植入测试(mutation testing)
    • a method for determining if a set of test data or test cases is useful, by deliberately introducing various code changes ('bugs') and retesting with the original test data/cases to determine if the 'bugs' are detected. Proper implementation requires large computational resources.

原始出处:http://www.softwareqatest.com/qatfaq1.html


相关阅读:

TAG: 测试理论 测试转载

左岸风在吹... 引用 删除 yxsaisai   /   2007-11-09 12:18:16
对于刚起步的测试人员来说,感觉理论实在太空...
JOYhh的个人空间 引用 删除 JOYhh   /   2007-06-28 11:00:13
你好啊!你写的很好啊!我是刚刚进入测试行业的希望能给些帮助。
 

评分:0

我来说两句

Open Toolbar