[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$flN9MxcGRdjtCLcCKhT-sSyuSMrgWUE1djKgQ2ej3Oio":3},{"answer":4,"createTime":5,"id":6,"options":7,"origin":12,"question":19,"related":20,"source":30,"type":31},[],"2024-11-26 08:45:04",167490507,[8,9,10,11],"系统测试、单元测试、集成测试、验收测试","单元测试、集成测试、验收测试、系统测试","单元测试、集成测试、系统测试、验收测试","验收测试、单元测试、集成测试、系统测试",{"count":13,"courseId":14,"courseImg":15,"courseName":16,"workId":17,"workName":18},257,"e02ff1a36207e6b0593b6de6560e6720","https:\u002F\u002Ftihai-oss-cloud.itihey.com\u002Fimg\u002Fbce0e1eb188e9245c1f92b3bc86e9284.webp","软件测试技术","exam_138318775","软件测试技术单元测验三","在软件测试阶段,测试步骤按次序可以划分为以下几步( )",[21,32,41,50,59,68,77,80,89,98],{"answer":22,"createTime":5,"id":23,"options":24,"question":29,"source":30,"type":31},[],167490501,[25,26,27,28],"x=10,x=100","x=10. x=11, x=99, x=100","x=9, x=10, r-50, x=100","x=9, =10, x=11, x=99, x=100,x=101","用边界值测试法,假定x为整数,10≤x≤100,那么x在测试中应该取( )为边界值","v1",0,{"answer":33,"createTime":5,"id":34,"options":35,"question":40,"source":30,"type":31},[],167490502,[36,37,38,39],"边界值测试是黑盒测试特有的技术方法,不适用于白盒测试","失败测试是纯粹为了破坏软件而设计和执行测试案例的","黑盒测试无法发现规格说明中的错误,不能进行充分的测试","黑盒测试着重测试软件的功能需求,是在程序接口上进行测试","关于黑盒测试技术,下面说法错误的是( )",{"answer":42,"createTime":5,"id":43,"options":44,"question":49,"source":30,"type":31},[],167490503,[45,46,47,48],"因果图法","等价类划分法","边界值法","决策表法","在一些数据处理问题中,某些操作的实施依赖于多个逻辑条件的组合,即针对不同逻辑条件的组合值,分别执行不同的操作,( )很适合处理这类问题",{"answer":51,"createTime":5,"id":52,"options":53,"question":58,"source":30,"type":31},[],167490504,[54,55,56,57],"②③","②④","①⑤","③④","下面关于软件测试模型的描述中,不正确的是( ).①V模型的软件测试策略既包括低层测试,又包括高层测试,高层测试是为了确保源代码的正确性,低层测试是为了使整个系统满足用户的需求.②V模型存在一定的局限性,它仅仅将测试过程作为在需求分析、概要设计、详细设计及编码之后的一个阶段.③W模型可以说是V模型自然而然的发展,它强调:测试伴随着整个软件开发周期,而且测试的对象不仅仅是程序,需求、功能和设计同样要测试.④H模型中,软件测试是一个独立的流程,贯穿产品的整个生命周期,与其他流程并发地进行.⑤H模型中,测试准备和测试实施紧密结合,有利于资源调配",{"answer":60,"createTime":5,"id":61,"options":62,"question":67,"source":30,"type":31},[],167490505,[63,64,65,66],"语句覆盖","条件覆盖","条件组合覆盖","判定\u002F条件覆盖","在下面所列举的逻辑测试覆盖中,测试覆盖强度最强的是( )",{"answer":69,"createTime":5,"id":70,"options":71,"question":76,"source":30,"type":31},[],167490506,[72,73,74,75],"①、②、③","②、③","①、④","①、③","导致软件缺陷的原因有很多,①—④是可能的原因,其中最主要的原因包括( ).①软件需求说明书编写的不全面,不完整,不准确,而且经常更改②软件设计说明书③软件操作人员的水平④开发人员不能很好地理解需求说明书和沟通不足",{"answer":78,"createTime":5,"id":6,"options":79,"question":19,"source":30,"type":31},[],[8,9,10,11],{"answer":81,"createTime":5,"id":82,"options":83,"question":88,"source":30,"type":31},[],167490508,[84,85,86,87],"测试计划","测试用例","测试工具","测试文档","JMeter是根据( )中描述的测试步骤来执行测试的",{"answer":90,"createTime":5,"id":91,"options":92,"question":97,"source":30,"type":31},[],167490509,[93,94,95,96],"验收测试","系统测试","集成测试","有效性测试","对软件是否能达到用户所期望的要求的测试称为( )",{"answer":99,"createTime":5,"id":100,"options":101,"question":106,"source":30,"type":31},[],167490510,[102,103,104,105],"判定表","输出状态表","约束条件表","输入状态表","由因果图转换出来的( )是确定测试用例的基础"]