You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Considering that we intend to update the inter-protocol pkg source code to extend the data being published to the storage node for increased visibility of the vaults liquidation, auction and post auction distribution.
We plan to increase the test coverage in this regard to assure that our updates are behaving accordingly.
A more detailed description of the assignment and solution proposed can be found here
Open Questions:
Should we extend an existing test file, (e.g. inter-protocol/test/vaultFactory/test-vaultLiquidation.js), or create a new one?
In case of creating a new file, would it be beneficial for us to either build a file to export some support functions or extend an existing one, (e.g. vaultFactoryUtils.js), to avoid duplicating code.
For example:
setupBasics
setupServices
setClockAndAdvanceNTimes
startAuctionClock
bid
...
Current approach (WiP)
As an experiment to explore the liquidation visibility, without risking creating a conflict with a future merge, we create a new directory called liquidationVisibility that contain some of the tests created.
The text was updated successfully, but these errors were encountered:
Unit tests
Context:
Considering that we intend to update the inter-protocol pkg source code to extend the data being published to the storage node for increased visibility of the vaults liquidation, auction and post auction distribution.
We plan to increase the test coverage in this regard to assure that our updates are behaving accordingly.
A more detailed description of the assignment and solution proposed can be found here
Open Questions:
inter-protocol/test/vaultFactory/test-vaultLiquidation.js
), or create a new one?vaultFactoryUtils.js
), to avoid duplicating code.For example:
Current approach (WiP)
As an experiment to explore the liquidation visibility, without risking creating a conflict with a future merge, we create a new directory called liquidationVisibility that contain some of the tests created.
The text was updated successfully, but these errors were encountered: