# Blog post: Testing in Seqes

**URL:** https://discuss.ocaml.org/t/blog-post-testing-in-seqes/11115
**Category:** Community
**Tags:** blog, gadt, qcheck
**Created:** [January 5, 2023, 8:02am UTC](https://discuss.ocaml.org/t/blog-post-testing-in-seqes/11115 "2023-01-05T08:02:22Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![raphael-proust](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/raphael-proust/32/415_2.png) [@raphael-proust](https://discuss.ocaml.org/u/raphael-proust)
#### Post date: [January 5, 2023, 8:02am UTC](https://discuss.ocaml.org/t/blog-post-testing-in-seqes/11115/1 "2023-01-05T08:02:23Z")

</div>

I have written a blog post about the test suite which covers this library.

TL;DR:

- I use GADTs to describe the library API and generate QCheck tests.
- I manually used `mutaml` for mutation-testing on the test suite.

[https://raphael-proust.gitlab.io/code/testing-seqes.html](https://raphael-proust.gitlab.io/code/testing-seqes.html)

The big takeaway for me is how useful mutation testing is. It gives some confidence in the test coverage not just in terms of what paths are visited but also that modifications are indeed caught by the tests. If you haven’t used `mutaml` I’d recommend giving it a go. If you have I’d be interested in ideas for integrating it better with some common build tools (`dune` mostly).

(Also, version 0.2 of `Seqes` is now available.)