LittleDarwin
Mutation tester
A tool for testing software's robustness to faults and failures
Java Mutation Testing Framework Written in Python
18 stars
4 watching
7 forks
Language: Python
last commit: 5 months ago
Linked from 1 awesome list
Related projects:
Repository | Description | Stars |
---|---|---|
| A mutation testing tool for C++ projects to detect programming errors | 173 |
| A mutation testing system for Python that helps identify weaknesses in software code by introducing small changes and running tests to see which ones fail. | 937 |
| An automated testing tool designed to detect faults in software code by introducing random errors and observing the impact on test results | 1,707 |
| A tool for mutation testing in Smalltalk to improve test quality and fault-finding effectiveness. | 22 |
| A tool for testing code changes by introducing random errors and assessing the impact on the code's functionality | 2 |
| A tool for testing the robustness of Python code by introducing random changes | 570 |
| A tool to test changes in Elixir applications by introducing deliberate faults and verifying the code's ability to recover from them | 21 |
| A tool to help developers analyze and visualize the effectiveness of mutation testing in their codebases. | 4 |
| An experimental tool for testing C# code by intentionally changing it to see if tests can detect the changes | 66 |
| Automated unit test generation and mutation testing tool using Large Language Models. | 252 |
| An automated testing tool that assesses the quality and coverage of test suites by introducing controlled changes to code bases. | 255 |
| Automated code review tool with mutation testing to simplify and improve code quality | 1,956 |
| Mutation testing framework to improve the quality of PHP code by introducing intentional errors and analyzing how it handles them. | 2,063 |
| A tool for generating and testing mutant models in Alloy to identify vulnerabilities in software systems. | 8 |
| A framework for detecting bugs in Rust code by intentionally introducing changes and seeing if tests can catch them | 629 |