软件测试工程师阶段_软件工程测试阶段

软件测试工程师阶段

Testing can be defined as checking the software for its correctness. In other words, we can define it as a process of observing a program for its behavior on providing some set of inputs (known as test cases) to check whether it is producing the expected results or not. If the behavior of the software on every input is as per the expected results, then the software qualifies the test and is approved for the next phase in its development cycle. If the tests are not cleared, then the behavior of the software for the failed test cases is noted and the software is again sent to the developers for debugging and correction purposes.

测试可以定义为检查软件的正确性。 换句话说,我们可以将其定义为观察程序在提供某些输入(称为测试用例)以检查程序是否产生预期结果时的行为的过程。 如果软件在每个输入上的行为均符合预期结果,则该软件将使测试合格,并可以批准其进入开发周期的下一阶段。 如果未清除测试,则会记录失败的测试用例的软件行为,并再次将软件发送给开发人员以进行调试和更正。

In most of the software life cycle models, the testing phase is usually mentioned after the coding and development phase. However, it is not the only time when the testing is required in the software. It is believed by software experts and is also a very common practice in most of the leading software development countries that the testing of the software is performed in every stage of its development: starting from its ideation phase till its retirement. It is believed that a good quality software must include the testing of the software after every phase because this practice makes sure that the errors and faults in the code are detected in the early stages itself, and the sooner the error and faults in the software are detected, the easier and convenient it is to correct them. And it also helps the software to remain within the budget because fixing the error takes extra work, extra working hours and hence extra cost as well.

在大多数软件生命周期模型中,通常在编码和开发阶段之后提到测试阶段。 但是,这不是唯一需要在软件中进行测试的时间。 软件专家相信,并且在大多数领先的软件开发国家中,这也是一种非常普遍的做法,即在软件开发的每个阶段都进行软件测试 :从构思阶段到退役。 人们认为,高质量的软件必须在每个阶段之后都包括对软件的测试,因为这种做法可确保在早期阶段就检测到代码中的错误和错误,并尽快识别出软件中的错误和错误。检测到后,更容易更方便地更正它们。 而且它还可以帮助软件保持在预算之内,因为修复错误会花费更多的工作,额外的工作时间,并因此而产生额外的成本。

When we talk about software testing, there are certain terms that you will frequently come across. Like: failures, test cases, test suites. Let us explain what all these terms mean:

当我们谈论软件测试时 ,您会经常遇到某些术语。 如:故障,测试用例,测试套件。 让我们解释一下所有这些术语的含义:

失败 (Failure)

Failure simply means a non-functioning software. Software failure is a result of error present in the program. However, it should be noted that not every error will lead to software failures.

故障仅表示软件无法运行。 软件故障是程序中存在错误的结果。 但是,应注意,并非每个错误都会导致软件故障。

Some of the famous examples of software failures are the Y2K problem, a Software glitch in F-35 fighter planes, etc.

软件故障的一些著名示例是Y2K问题,F-35战斗机中的软件故障等。

测试用例 (Test case)

The test case is a set of inputs that are provided to the software to check its behavior for the given problem that it is expected to solve. This is the triplet: I S O, where,

测试用例是提供给软件的一组输入,以检查软件的行为以解决预期的给定问题。 这是三元组:ISO,

  • "I" stands for the input that you provide to the software.

    “ I”代表您提供给软件的输入

  • "S" stands for the system to which the input is provided.

    “ S”代表提供输入的系统

  • "O" is the expected output that the system should produce.

    “ O”是系统应产生的预期输出

测试套件 (Test Suite)

It can be called as the superset of the test cases. A test suite is a set of all the test cases which are used for testing the software product.

它可以称为测试用例的超集。 测试套件是用于测试软件产品的所有测试用例的集合。

翻译自: https://www.includehelp.com/basics/testing-phase-in-software-engineering.aspx

软件测试工程师阶段

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值