As of f89eb89, coverage output looks like this:

--------------------|----------|----------|----------|----------|----------------|
File                |  % Stmts | % Branch |  % Funcs |  % Lines |Uncovered Lines |
--------------------|----------|----------|----------|----------|----------------|
 contracts/         |    97.36 |    66.87 |    98.18 |    97.04 |                |
  PLCRVoting.sol    |     96.2 |    55.17 |    95.45 |    95.24 |102,103,105,370 |
  Parameterizer.sol |    98.82 |    68.18 |      100 |    98.85 |            223 |
  Registry.sol      |    97.03 |    76.56 |      100 |    96.97 |    136,137,139 |
--------------------|----------|----------|----------|----------|----------------|
All files           |    97.36 |    66.87 |    98.18 |    97.04 |                |
--------------------|----------|----------|----------|----------|----------------|

% Stmts should be at least 95% and % Branch should be at least 85%. These targets currently exclude tests for where token transfers fail. They also exclude PLCRVoting.sol, since that will be consumed from EPM in the future, and the tests really belong in the PLCRVoting repository.

Non-covered test cases to be added:

Parameterizer

proposeRarameterization

• should revert if the proposal is a NOOP

challengeReparameterization

• should revert if the proposal does not exist
• should revert if the proposal already has a challenge against it

processProposal

• should revert in the else case
• (these may not be possible to test)
  • should revert if the set dispensationPct is greater than 100
  • should revert if the set pDispensationPct is greater than 100

claimReward

• should revert if the sender has already claimed their tokens

resolveChallenge

• cover case where the challenge failed and the processBy date has passed
  • it should not set the value, and it should transfer tokens to the proposal owner

Registry

apply

• should revert if the deposit amount is less than the minDeposit

withdraw

• should revert if the message sender is not the owner of the listing
• should be able to withdraw tokens and decrease the unstaked deposit

exit

• should revert if the listing is in the application stage

challenge

• should revert if the application is not in the apply stage and is not on the whitelist
• should revert if the application currently has an open challenge against it

determineReward

• should revert if the challenge has already been resolved
• should revert if the poll has not ended yet