【24h】

Scenario Driven Testing

机译:场景驱动测试

获取原文

摘要

Software testing has traditionally focused on evaluating the functionality of implemented modules against feature specifications. This approach assumes that customer requirements and usage scenarios are accurately translated into specifications and that individual modules implemented using the feature specifications would work seamlessly and coherently to solve business problems meant to be addressed by the software under test. To ensure software built would help customers solve their business problems as intended, test teams have to go beyond traditional feature driven testing approach and test software for quality and completeness with respect to targeted customer scenarios. For this, test teams have to adopt scenario driven test methodology which involves understanding the targeted customer scenarios and use them along with feature specifications for the intended software solution to translate them into test specifications, prioritization of test work items and use them throughout project for shared understanding of tradeoffs and making decisions. In this short paper, we describe scenario driven testing and share how it was applied to test a feature-set developed for a successful product line at Microsoft®.
机译:传统上,软件测试的重点是根据功能规范评估已实现模块的功能。该方法假定将客户需求和使用场景准确地转换为规范,并且使用功能规范实现的各个模块将无缝且一致地工作,以解决要由被测软件解决的业务问题。为了确保构建的软件可以帮助客户按预期解决他们的业务问题,测试团队必须超越传统的功能驱动测试方法,并针对目标客户场景测试软件的质量和完整性。为此,测试团队必须采用场景驱动的测试方法,该方法包括了解目标客户的场景,并将其与预期软件解决方案的功能规范一起使用,以将其转换为测试规范,确定测试工作项目的优先级,并在整个项目中使用它们以实现共享了解权衡并做出决策。在这篇简短的文章中,我们描述了场景驱动的测试,并分享了如何将其应用于测试为Microsoft®成功的产品线开发的功能集。

著录项

相似文献

  • 外文文献
  • 中文文献
  • 专利
获取原文

客服邮箱:kefu@zhangqiaokeyan.com

京公网安备:11010802029741号 ICP备案号:京ICP备15016152号-6 六维联合信息科技 (北京) 有限公司©版权所有
  • 客服微信

  • 服务号