https://github.com/rogervinas/testing-playground

🤹 Testing Playground
https://github.com/rogervinas/testing-playground

mutation-testing property-based-testing snapshot-testing

Last synced: 3 months ago
JSON representation

🤹 Testing Playground

• Host: GitHub
• URL: https://github.com/rogervinas/testing-playground
• Owner: rogervinas
• Created: 2022-09-07T14:55:39.000Z (over 3 years ago)
• Default Branch: main
• Last Pushed: 2022-09-15T13:58:47.000Z (over 3 years ago)
• Last Synced: 2024-12-27T11:24:28.417Z (about 1 year ago)
• Topics: mutation-testing, property-based-testing, snapshot-testing
• Language: Kotlin
• Homepage:
• Size: 68.4 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

          
[![CI](https://github.com/rogervinas/testing-playground/actions/workflows/gradle.yml/badge.svg)](https://github.com/rogervinas/testing-playground/actions/workflows/gradle.yml)

# Testing Playground

## Mutation Testing

[Mutation Testing](mutation-testing/src/test/kotlin/org/testingplayground/MyImplTest.kt) using [pitest](https://pitest.org/)

> Mutation testing is conceptually quite simple.

> Faults (or mutations) are automatically seeded into your code, then your tests are run. If your tests fail then the mutation is killed, if your tests pass then the mutation lived.

> The quality of your tests can be gauged from the percentage of mutations killed.

## Property-based Testing

[Property-based Testing](property-based-testing/src/test/kotlin/PropertyBasedTesting.kt) using [Kotest](https://kotest.io/docs/proptest/property-based-testing.html)

> Instead of writing example-based tests, with property testing,

> hundreds or thousands of values are fed into the same test,

> and the values are (usually) randomly generated by your property test framework

## Snapshot Testing

[Snapshot Testing](snapshot-testing/src/test/kotlin/SnapshotTesting.kt) using [origin-energy/java-snapshot-testing](https://github.com/origin-energy/java-snapshot-testing)

> **Advantages of Snapshot Testing**

> * Great for testing JSON interfaces ensuring you don't break clients

> * Fast and easy to test

> * Will implicitly test areas of your code you did not think about

> * Great of testing dynamic objects

>

> **Disadvantages of Snapshot Testing**

> * You need to ensure your test is deterministic for all fields

> * Does not give great insight to why the snapshot failed

> * Can be difficult to troll though large snapshot changes where you might only be interested in a small set of fields