单元测试、集成测试、确认测试、系统测试、验收测试

在开发过程中,都要经过由小到大、由内至外、循序渐进测试过程,根据不同的测试阶段可以分为:单元测试、集成测试、确认测试、系统测试、验收测试

1,单元测试(Unit Testing)

单元测试又称模块测试,是针对软件设计的最小单位(模块)进行正确性检验的测试,检查每个程序模块是否实现了规定的功能,保证其能正常工作。

测试重点:

(1)系统的模块,子程序的正确性验证等

(2)白盒测试


2,集成测试(Integrated Testing)

集成测试是把已测试过的模块组装起来,对与设计相关的软件体系结构进行测试。

测试重点:

(1)把各个模块连接起来,模块接口的数据是否会丢失

(2)单独一个子模块的功能是否会对另一个模块的功能产生不利的影响

(3)各个子模块功能组合起来,能否达到预期的要求

(4)全局数据结构是否有问题

(5)单个模块的误差积累起来,是否会被放大从而达到不能接受的程度

(6)白盒测试+黑盒测试


3,确认测试(Confirm Testing)

确认测试是检验所开发的软件是否满足SRD(System Requirement Document)中定义的需求、性能要求,以及软件配置是否完全正确。


4,系统测试(System Testing)

系统测试是把通过确认测试的软件作为系统的一个元素,接入系统的实际运行环境中,与系统的其他部分(硬件、系统、数据库、第三方数据等)结合起来进行测试。

测试重点:

(1)整个系统运行的稳定性

(2)整个系统的兼容性

(3)是否符合“需求规格说明书”

(4)黑盒测试


5,验收测试(Acceptance Testing)

验收测试是检验软件产品的最后一关,在这个环节,测试主要从用户的角度着手。是一个确定产品能否满足合同/用户需求的测试。



  • 16
    点赞
  • 69
    收藏
    觉得还不错? 一键收藏
  • 3
    评论
Learn how to create good requirements when designing hardware and software systems. While this book emphasizes writing traditional “shall” statements, it also provides guidance on use case design and creating user stories in support of agile methodologies. The book surveys modeling techniques and various tools that support requirements collection and analysis. You’ll learn to manage requirements, including discussions of document types and digital approaches using spreadsheets, generic databases, and dedicated requirements tools. Good, clear examples are presented, many related to real-world work the author has done during his career.Requirements Writing for System Engineeringantages of different requirements approaches and implement them correctly as your needs evolve. Unlike most requirements books, Requirements Writing for System Engineering teaches writing both hardware and software requirements because many projects include both areas. To exemplify this approach, two example projects are developed throughout the book, one focusing on hardware and the other on software. This book Presents many techniques for capturing requirements. Demonstrates gap analysis to find missing requirements. Shows how to address both software and hardware, as most projects involve both. Provides extensive examples of “shall” statements, user stories, and use cases. Explains how to supplement or replace traditional requirement statements with user stories and use cases that work well in agile development environments What You Will Learn Understand the 14 techniques for capturing all requirements. Address software and hardware needs; because most projects involve both. Ensure all statements meet the 16 attributes of a good requirement. Differentiate the 19 different functional types of requirement, and the 31 non-functional types. Write requirements properly based on extensive examples of good ‘shall’ statements, user stories, and use cases. Employ modeling techniques to mitigate the

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论 3
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值