变异测试 系统输入输出_变异测试，系统测试和性能测试| 软件工程

变异测试 系统输入输出

1)变异测试 (1) Mutation Testing)

Whenever a module is tested for the first time, it is most probably encountered with some errors and to resolve them, the developer makes some changes in the program code of the software and again tests it. After making some changes in the software, the program becomes a mutated program and the changes effected in the program are called the mutant, and thus the testing performed after this is called as mutation testing.

每当首次测试模块时，很可能会遇到一些错误，并且要解决这些错误，开发人员会在软件的程序代码中进行一些更改，然后再次对其进行测试。 在软件中进行了一些更改之后，该程序将成为一个突变程序，并且在程序中生效的更改称为“突变体”，因此在此之后执行的测试称为“突变测试”。

In this type of testing strategy, the test cases are designed to kill the mutant. First, the mutant is checked for simple test cases and if the mutant survives them, the test cases are enhanced to kill the mutant.

在这种类型的测试策略中，测试用例旨在杀死突变体。 首先，检查突变体的简单测试用例，如果突变体幸免于难，则增强测试用例以杀死突变体。

However, this process takes a lot of time is too expensive because sometimes the mutant gets killed for very complex test cases which are tested after testing for so many low-level test cases, and after being killed, changes are to be made in the program and again the same process is performed from the very initial stage.

但是，此过程要花费大量时间，这太昂贵了，因为有时突变体会因为非常复杂的测试用例而被杀死，而这些复杂的测试用例在测试了许多低级别的测试用例之后才进行测试，并且在被杀死之后，需要在程序中进行更改并从最开始的阶段开始执行相同的过程。

It is advised not to use this testing strategy when testing the software manually. However, it is a good way to produce an error-free software if automated software testing is being performed.

建议在手动测试软件时不要使用此测试策略。 但是，如果正在执行自动软件测试，则是生产无错误软件的好方法。

2)系统测试 (2) System Testing)

System testing is performed after the whole software is completely developed and is ready to deliver to the customer. Here, the aim of the testing is not to check the software for errors but the main emphasis is to check whether the software is meeting the user’s needs. In the system testing, there are basically three levels of testing,

在完整开发整个软件并准备将其交付给客户之后，将执行系统测试。 在这里，测试的目的不是检查软件是否有错误，而是主要检查软件是否满足用户的需求。 在系统测试中，基本上有三个测试级别，

1. Alpha testing:

   阿尔法测试 ：

   The alpha testing is performed by a selected group f members form the developing organization itself. This means that the software producers itself act as the customers in order to check for its performance.

   alpha测试是由发展中组织本身的选定小组f成员执行的。 这意味着软件生产商本身就是客户，以检查其性能。

2. Beta testing:

   Beta测试 ：

   Here, the system testing is done with a selected group of friendly customers and their feedback is noted for every single user among this group.

   在这里，系统测试是由一组选定的友好客户完成的，并记录了该组中每个用户的反馈。

3. Acceptance testing:

   验收测试 ：

   In this type of testing, the software is made available to the actual customers and they are the one to then decide whether the software is acceptable or not.

   在这种类型的测试中，软件可供实际客户使用，然后由他们决定软件是否可接受。

3)性能测试 (3) Performance Testing)

Performance testing is basically to check the system on some non-functional requirements. The main aim of the performance testing is to test the software for nun-functional requirements mentioned in the SRS document. The performance testing is considered to be a part of the black box testing. There are several types of performance testing that are performed on the software and among them, some are listed below,

性能测试基本上是检查系统是否存在某些非功能性需求。 性能测试的主要目的是测试软件是否符合SRS文档中提到的功能要求。 性能测试被认为是黑盒测试的一部分。 该软件执行了几种类型的性能测试，其中包括以下几种，

• Stress testing

  压力测试

• Configuration testing

  配置测试

• Smoke testing

  烟雾测试

• Security testing

  安全测试

• Volume testing

  量测

• Compatibility testing

  兼容性测试

• Regression testing

  回归测试

• Recovery testing

  恢复测试

• Maintenance testing

  维护测试

• Documentation testing

  文件测试

• Usability testing

  可用性测试

翻译自: https://www.includehelp.com/basics/mutation-testing-system-testing-and-performance-testing-software-engineering.aspx

变异测试 系统输入输出