One way to gain insights into whether all methods and method-keys have been used, is to compute the grammar coverage.
Based on the OpenRPC specification, the number of keys in total (counting different keys per method) can be computed. If the tool works properly, all keys should eventually be used to make sure there are no stones left unturned (that could lead into unique responses from the server).
While running the tool, the keys that are used per method should be marked so that when the time limit is reached, this number can be compared to the total number. This allows us to see whether all keys have actually been used.
A key may not have an effect on the responses sometimes, so therefore this coverage is based on the total run (to see whether every key was at least used once), and not on the individuals in the archive (although this could also be easily computed).
One way to gain insights into whether all methods and method-keys have been used, is to compute the grammar coverage.
Based on the OpenRPC specification, the number of keys in total (counting different keys per method) can be computed. If the tool works properly, all keys should eventually be used to make sure there are no stones left unturned (that could lead into unique responses from the server).
While running the tool, the keys that are used per method should be marked so that when the time limit is reached, this number can be compared to the total number. This allows us to see whether all keys have actually been used.
A key may not have an effect on the responses sometimes, so therefore this coverage is based on the total run (to see whether every key was at least used once), and not on the individuals in the archive (although this could also be easily computed).