Contract Test case Definition

[mehdi-torabiv]

Test cases

Below are the test cases for the engagement contract.

variables

uint private _counter; // increment on issue function
mapping(uint id, uint) private _tokenCount; // nb of accounts that have minted a token

deployment

Success

• Should have deployer as admin #8
• Should have a PROVIDER_ROLE #9
• Should have counter equal 0 #16

issue(string memory tokenCid)

Creates a new token and adds a cid to it's metadata.

Success

• Should increment counter by 1 #11
• Should have an account balance of 1 #13
• Should emit Issue event #14

mint(uint id, string memory account)

Mint a token balance to 1.

Success

• Should have an account balance of 1 #17
• Should emit Mint event #18

Revert

• Should revert with MintLimit (token balance > 1) #20
• Should revert with NotFound (token doesn't exist) #19

burn(uint id, string memory account)

Burn the token balance to 0.

Success

• Should have an account balance of 0 #21
• Should emit Burn event #22

Revert

• Should revert with NotAllowed (msg.sender != account) #23
• Should revert with NotFound (token doesn't exist) #25

getScore(uint date, uint id, string memory account)

Return a formatted uri: ipfs://hash/id/account.json

Success

• Should return formatted uri #32

Revert

• Should revert with NotFound (token doesn't exist) #30

updateScores(uint date, string memory cid)

Update the cid for a given date.

Success

• Should update scores mapping #36
• Should emit UpdateCid event #39

Revert

• Should revert with AccessControlUnauthorizedAccount (msg.sender doesn't have PROVIDER_ROLE) #34

uri(uint id)

Return a formatted uri: ipfs://hash.json

Success

• Should return formatted uri #15

Revert

• Should revert with NotFound (token doesn't exist) #42

[cyri113]

@mehdi-torabiv

I think we need 2 new mappings: mintedAt and burnedAt.

• What new test cases does this add? and where?
• How does this impact the getScore revert test case?

Missing test cases for issue(string memory cid).