Skip to main content

Mutation Testing


What is Mutation Testing?

Mutation Testing is an approach that evaluates the quality of existing software tests. The whole idea is to modify a small part in your code (mutated version code- faulty seed) covered by tests and check whether the existing test suite will find the errors and reject this mutated code. If it doesn’t, it means the tests are less strong and does not match your code’s complexity and thus leave many aspects untested.

The changes introduced or injected in the program code are generally referred to as ‘mutants’.

Let's take an example now- say we have a function where we take the monthly Total income of a family as an input and then decide whether they are eligible for a subsidy of Gas or not. If it is equal or less than ₹10,000, give them a subsidy.  It will be something like:
-  Input the monthly Total income
-  If monthly Total income=<₹10,000
-  Gas Subsidy= Yes
-  End if (Gas Subsidy= No)

For testing, our test data inputs will be like 9999, 10000, 10001, 0, some negative value,  some decimal value, some fractional value, etc. These should be apt. to catch if there is an issue with the code.

But as part of the mutant test, we do more like, we'll seed fault in the code by adding these mutants:
- Removing/Updating the Arithmetic operator, Relational and Logical operator
- Removing the If Statement itself 
- Adding Incorrect syntax
- Absolute value insertion like Subsidy=5000 instead of Boolean Yes/No, etc.

P.S. In any project where we have many devs contributing to the product/project; mutation testing of even a small module can block your CI cycles. Plus, the time and expense involved in it are huge as compared to the perceived value returned.

Parallel Isolated Test (http://pitest.org) is a Java based mutation testing system.



Labels:

Comments

Post a Comment

Popular posts from this blog

How to Unzip files in Selenium (Java)?

1) Using Java (Lengthy way) : Create a utility and use it:>> import java.io.BufferedOutputStream; import org.openqa.selenium.io.Zip; import java.io.File; import java.io.FileInputStream; import java.io.FileOutputStream; import java.io.IOException; import java.util.zip.ZipEntry; import java.util.zip.ZipInputStream;   public class UnzipUtil {     private static final int BUFFER_SIZE = 4096;     public void unzip (String zipFilePath, String destDirectory) throws IOException {         File destDir = new File(destDirectory);         if (!destDir.exists()) {             destDir.mkdir();         }         ZipInputStream zipIn = new ZipInputStream(new FileInputStream(zipFilePath));         ZipEntry entry = zipIn.getNextEntry();         // to iterates over entries in the zip folder         while (entry != null) {             String filePath = destDirectory + File.separator + entry.getName();             if (!entry.isDirectory()) {                 extractFile (zipIn, filePath);            
Post a Comment
Read more

Encode/Decode the variable/response using Postman itself

We get a lot of use cases where we may have to implement Base64 encoding and/or decoding while building our APIs. And, if you are wondering if it is possible to encode/decode the variable/response using Postman itself or how to encode/decode the token or password in postman and save it in a variable? To Base64 encode/decode, the quickest way is to use JavaScript methods btoa, atob: atob - It turns base64-encoded ASCII data back to binary. btoa - It turns binary data to base64-encoded ASCII. Sample code : var responseBody = pm.response.json(); var parsedPwd = JSON.parse(atob(responseBody.password)); // presuming password is in the payload pm.collectionVariables.set("password", parsedPwd);
Post a Comment
Read more

The use of Verbose attribute in testNG or POM.xml (maven-surefire-plugin)

At times, we see some weird behavior in your testNG execution and feel that the information displayed is insufficient and would like to see more details. At other times, the output on the console is too verbose and we may want to only see the errors. This is where a verbose attribute can help you- it is used to define the amount of logging to be performed on the console. The verbosity level is 0 to 10, where 10 is most detailed. Once you set it to 10, you'll see that console output will contain information regarding the tests, methods, and listeners, etc. <suite name="Suite" thread-count="5" verbose="10"> Note* You can specify -1 and this will put TestNG in debug mode. The default level is 0. Alternatively, you can set the verbose level through attribute in "maven-surefire-plugin" in pom.xml, as shown in the image. #testNG #automationTesting #verbose # #testAutomation
Post a Comment
Read more