軟件測試工程師階段

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

軟件測試工程師階段

總結

以上是生活随笔為你收集整理的软件测试工程师阶段_软件工程测试阶段的全部內容，希望文章能夠幫你解決所遇到的問題。

如果覺得生活随笔網站內容還不錯，歡迎將生活随笔推薦給好友。