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
Sort the tests SetUp() functions on what they need per file, and create a single function in the test folder that generates those requirements, and call that function from the SetUp() functions, instead of cluttering each test with a large SetUp() function (and its accompanying imports).
NEXT UP: Apply loading the _dim from the InitialiseDim.sol contract like in ReceiveAcceptedOffer.t.sol.
Move the unit tests into functional tests and unit tests. Per test, determine if it is functional or unit and when you move it, create a docstring that describes what it tests, and copy the setup.
If you put the first test in a functional file test, create a documentation list of all the functionalities that that file will test.
If a functional test should not be in a method functional test file, put it in the file whose functionality is tested (most), and give the test filename one that describes the functionality that is being tested.
The text was updated successfully, but these errors were encountered:
SetUp()
functions on what they need per file, and create a single function in the test folder that generates those requirements, and call that function from theSetUp()
functions, instead of cluttering each test with a largeSetUp()
function (and its accompanying imports).InitialiseDim.sol
contract like inReceiveAcceptedOffer.t.sol
.The text was updated successfully, but these errors were encountered: