# Overview of Test Coverage Criteria for Test Case Generation from Finite State Machines Modelled as Directed Graphs

arXiv: https://arxiv.org/abs/2203.09604 · HTML: https://mlsanity.com/paper/2203.09604/

## Key facts

- No citing papers in the map yet (data through 14 Oct 2026).
- Builds on 3 of its 39 references that are in the map.
- First posted on arXiv 17 Mar 2022.

## Builds on (most cited first, 3 of 3)

- [Employment of Multiple Algorithms for Optimal Path-based Test Selection Strategy](https://mlsanity.com/paper/1802.08005/) (2018)
- [Prioritized Process Test: An Alternative to Current Process Testing Strategies](https://mlsanity.com/paper/1903.08531/) (2019)
- [Basis Path Coverage Criteria for Smart Contract Application Testing](https://mlsanity.com/paper/1911.10471/) (2019)

## Abstract (arXiv)

Test Coverage criteria are an essential concept for test engineers when generating the test cases from a System Under Test model. They are routinely used in test case generation for user interfaces, middleware, and back-end system parts for software, electronics, or Internet of Things (IoT) systems. Test Coverage criteria define the number of actions or combinations by which a system is tested, informally determining a potential "strength" of a test set. As no previous study summarized all commonly used test coverage criteria for Finite State Machines and comprehensively discussed them regarding their subsumption, equivalence, or non-comparability, this paper provides this overview. In this study, 14 most common test coverage criteria and seven of their synonyms for Finite State Machines defined via a directed graph are summarized and compared. The results give researchers and industry testing engineers a helpful overview when setting a software-based or IoT system test strategy.