Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tests are broken #58

Open
code423n4 opened this issue Oct 10, 2021 · 1 comment
Open

Tests are broken #58

code423n4 opened this issue Oct 10, 2021 · 1 comment
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Warden finding sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons

Comments

@code423n4
Copy link
Contributor

Handle

kenzo

Vulnerability details

Tests have not been changed after changes to protocol.
Not much use in tests if not keeping them up to date.

Impact

Can't test protocol working correctly. (And indeed, basic mint functionality is broken, see issue).

Proof of Concept

Run the tests, they are failing.

Tools Used

Recommended Mitigation Steps

Basket's "Should allow changing the publisher after a timelock": now txs won't be reverted when given new publisher which is different then pending publisher but will set it as pending publisher.
https://github.com/code-423n4/2021-10-defiprotocol/blob/main/contracts/test/Basket.test.js#L122
https://github.com/code-423n4/2021-10-defiprotocol/blob/main/contracts/test/Basket.test.js#L125
You will also need to change the amount of mined blocks if you simply comment out the above lines. However you might want to add a test that checks the changing publisher functionality.
https://github.com/code-423n4/2021-10-defiprotocol/blob/main/contracts/test/Basket.test.js#L126

Errors which are not fully dependent on tests but on code also:

@code423n4 code423n4 added 1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Warden finding labels Oct 10, 2021
code423n4 added a commit that referenced this issue Oct 10, 2021
@frank-beard frank-beard added the sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons label Nov 6, 2021
@GalloDaSballo
Copy link
Collaborator

Technically out of scope, but we'll allow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1 (Low Risk) Assets are not at risk. State handling, function incorrect as to spec, issues with comments bug Warden finding sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons
Projects
None yet
Development

No branches or pull requests

3 participants