WIP: Contribution contracts tests #159
@ -181,14 +181,32 @@ contract('Contribution app', (accounts) => {
|
||||
|
|
||||
// eslint-disable-next-line no-undef
|
||||
assert.equal(mintTokenPermission, true);
|
||||
});
|
||||
|
||||
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
});
|
||||
|
||||
describe("Add contribution", async () => {
|
||||
let amount = 100;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let contributorId = 1;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let hashDigest = '0x0000000000000000000000000000000000000000000000000000000000000000';
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let hashFunction = 1;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let hashSize = 1;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// contributor detials
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let account, contributorHashDigest, contributorHashFunction, contributorHashSize;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// contribution details
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let amount, contributorId, hashDigest, hashFunction, hashSize;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// eslint-disable-next-line no-undef
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
before(async () => {
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// Add contributor from Contributor app
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
account = root;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
contributorHashDigest = '0x0000000000000000000000000000000000000000000000000000000000000000';
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
contributorHashFunction = 0;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
contributorHashSize = 0;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
await contributor.addContributor(account, contributorHashDigest, contributorHashFunction, contributorHashSize);
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// eslint-disable-next-line no-undef
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
assert.equal(await contributor.addressExists(account), true);
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
amount = 100;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
contributorId = await contributor.getContributorIdByAddress(root);
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
hashDigest = '0x0000000000000000000000000000000000000000000000000000000000000000';
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
hashFunction = 1;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
hashSize = 1;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
});
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
|
||||
it("should revert when add contribution from address that does not have permission", async () => {
|
||||
return assertRevert(async () => {
|
||||
@ -212,7 +230,7 @@ contract('Contribution app', (accounts) => {
|
||||
|
this one revert for some reasons this one revert for some reasons
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
assert.equal(contributionCountAfter.toNumber()-contributionCountBefore.toNumber(), 1, "contributions counter incremented");
|
||||
let contributionObject = await contribution.getContribution(contributionCountAfter.toNumber());
|
||||
// eslint-disable-next-line no-undef
|
||||
assert.equal(contributionObject[1], contributorId, "contribution added belong to contributor id");
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
assert.equal(contributionObject[1].toNumber(), contributorId.toNumber(), "contribution added belong to contributor id");
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let isExist = await contribution.exists(contributionCountAfter.toNumber());
|
||||
// eslint-disable-next-line no-undef
|
||||
assert.equal(isExist, true, "contribution exist");
|
||||
@ -258,15 +276,6 @@ contract('Contribution app', (accounts) => {
|
||||
|
this one revert for some reasons this one revert for some reasons
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
|
||||
// eslint-disable-next-line no-undef
|
||||
before(async () =>{
|
||||
//add contributor
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let account = root;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let contributorHashDigest = '0x0000000000000000000000000000000000000000000000000000000000000000';
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let contributorHashFunction = 0;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let contributorHashSize = 0;
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
await contributor.addContributor(account, contributorHashDigest, contributorHashFunction, contributorHashSize);
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// eslint-disable-next-line no-undef
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
assert.equal(await contributor.addressExists(account), true);
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
//add contribution
|
||||
let amount = 200;
|
||||
let contributorId = await contributor.getContributorIdByAddress(root);
|
||||
@ -294,14 +303,20 @@ contract('Contribution app', (accounts) => {
|
||||
|
this one revert for some reasons this one revert for some reasons
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
});
|
||||
|
||||
it("claim contribution", async () => {
|
||||
let contributionObject = await contribution.getContribution(contributionId.toNumber());
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let confirmationBlock = contributionObject[7];
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let chainBlockNumberBefore = await getBlockNumber();
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
if(contributionId > 10) {
|
||||
await timeTravel(blocksToWait);
|
||||
await mineBlock();
|
||||
let chainBlockNumberAfter = await getBlockNumber();
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// eslint-disable-next-line no-undef
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
assert.equal(chainBlockNumberAfter.toNumber()-chainBlockNumberBefore.toNumber(), confirmationBlock.toNumber());
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
}
|
||||
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
//Claim contribution
|
||||
await contribution.claim(contributionId);
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
let contributionObject = await contribution.getContribution(contributionId.toNumber());
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
await contribution.claim(contributionId, {from: root});
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
contributionObject = await contribution.getContribution(contributionId.toNumber());
|
||||
|
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
// eslint-disable-next-line no-undef
|
||||
assert(contributionObject[3], true);
|
||||
});
|
||||
|
||||
|
this one revert for some reasons this one revert for some reasons
this one revert for some reasons this one revert for some reasons
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
Looks like the expectation wasn't described here ( Looks like the expectation wasn't described here (`it("does x")`). It also looks like there are 3 different expectations in one block here.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
I think you can also add expectation descriptions as the last argument to I think you can also add expectation descriptions as the last argument to `assert()`, in case you really want to assert multiple things in one `it` block.
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
Reverts unexpectedly? And in which context/scenario? Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
in the scenario of claiming an added contribution in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
most of those multiple assert check for the same thing, that the contribution is added.. XD most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
How would that work? You can only claim confirmed contributions. How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added. They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
ahhhh yup okay, missed this ahhhh yup okay, missed this ` require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE'); ` thanks!
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block. In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
this should fix the claim tests, no @skddc @bumi ? this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
Yes, the first 10 are confirmed immediately iirc. Yes, the first 10 are confirmed immediately iirc.
|
||||
this one revert for some reasons
this one revert for some reasons
Looks like the expectation wasn't described here (
it("does x")). It also looks like there are 3 different expectations in one block here.Looks like the expectation wasn't described here (
it("does x")). It also looks like there are 3 different expectations in one block here.I think you can also add expectation descriptions as the last argument to
assert(), in case you really want to assert multiple things in oneitblock.I think you can also add expectation descriptions as the last argument to
assert(), in case you really want to assert multiple things in oneitblock.Reverts unexpectedly? And in which context/scenario?
Reverts unexpectedly? And in which context/scenario?
in the scenario of claiming an added contribution
in the scenario of claiming an added contribution
most of those multiple assert check for the same thing, that the contribution is added.. XD
most of those multiple assert check for the same thing, that the contribution is added.. XD
How would that work? You can only claim confirmed contributions.
How would that work? You can only claim confirmed contributions.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
They very line I commented on asserts that the contributorId is correct, not that the contribution itself was added.
ahhhh yup okay, missed this
require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE');thanks!ahhhh yup okay, missed this
require(block.number >= c.confirmedAtBlock, 'NOT_CLAIMABLE');thanks!yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
yeah true, honestly don't know if that all those asserts are necessary... maybe just for more code coverage
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
In this case it's only important that you describe what you mean to test exactly. Currently, there's no description of what is being tested in this block.
this should fix the claim tests, no @skddc @bumi ?
this should fix the claim tests, no @skddc @bumi ?
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
idk if this test is really necessary as if a contribution is claimed, so theoretically it is impossible to veto because of block number @bumi
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
can't figure out why this one is not working, idk what I'm missing there! @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc
blocks get minted and the veto period end right away... @bumi @skddc
Yes, the first 10 are confirmed immediately iirc.
Yes, the first 10 are confirmed immediately iirc.