Mutation Testing is one of the fault base testing techniques - Maintaining the System

Discussion

• Nirja Shah   -Posted on 21 Oct 15
  Mutation testing
  - It is a structural testing technique, that uses the structure of the code to guide the testing process.
  
  - On higher level, it is the process of rewriting the source code in small ways so that the redundancies are removed from the source code.
  
  - These ambiguities may cause failures in the software and if not fixed they can easily pass through testing phase undetected.
  
  Unit testing
  - The smallest testable part of an application like functions, classes, procedures, interfaces is a unit.
  
  - This testing is a method by which individual units of source code are tested to determine if they are fit for use.
  
  - These tests are basically written and executed by software developers to make sure that code meets its design and requirements and behaves as expected.
  
  - The goal of this testing is to segregate each part of the program and test so that the individual parts are working correctly.
  
  - This means that for any function or procedure when a set of inputs are given then it should return the proper values.
  
  - The failures should be handled properly during the course of execution when any invalid input is given.
  
  Beta testing
  - This testing is also known as field testing.
  
  - They take place at customer’s site.
  
  - They send the system to users who install it and use it under real-world working conditions.
  
  - It is the second phase of software testing in which a sampling of the intended audience tries the product out.
  
  - Originally, the term alpha test meant the first phase of testing in a software development process.
  
  - First phase includes the unit testing, component testing, and system testing.
  
  - This testing can also be considered “pre-release testing.
  
  Stress testing
  - It is a software testing activity that determines the robustness of software by testing beyond the limits of normal operation.
  
  - It is particularly important for "mission critical" software, but is used for all types of software.
  
  - They commonly put a greater emphasis on robustness, availability, and error handling under a heavy load, than on what would be considered correct behavior under normal circumstances.

➨ Post your comment / Share knowledge